Oracle International Corporation

Bharat C V Baddepudi

Kiran Badrinarain Goyal

Juan R Loaiza

Kothanda Umamageswaran

Alexander Tsukerman

Selcuk Aya

Boris Erlikhman

Poojan Kumar

Tirthankar Lahiri

Wei-Ming Hu

Neil J S MacNaughton

Roger J Hansen

Adam Y Lee

Vipin Gokhale

Eugene Reddy Ho

Umesh Panchaksharaiah

Nilesh Choudhury

Sue-Kyoung Lee

Adrian Ng

Timothy L Shetler

Susy Fan

Benoit Dageville

Balasubramanian Narasimhan

Brian Hirano

Siddhartha Roychowdhury

Techniques are provided for using an intermediate cache to provide some of the items involved in a scan operation, while other items involved in the scan operation are provided from primary storage. Techniques are also provided for determining whether to service an I/O request for an item with a copy of the item that resides in the intermediate cache based on factors such as a) an identity of the user for whom the I/O request was submitted, b) an identity of a service that submitted the I/O request, c) an indication of a consumer group to which the I/O request maps, d) whether the I/O request is associated with an offloaded filter provided by the database server to the storage system, or e) whether the intermediate cache is overloaded. Techniques are also provided for determining whether to store items in an intermediate cache in response to the items being retrieved, based on logical characteristics associated with the requests that retrieve the items.

Selectively reading data from cache and primary storage based on whether cache is overloaded

Techniques are provided for using an intermediate cache between the shared cache of an application and the non-volatile storage of a storage system. The application may be any type of application that uses a storage system to persistently store data. The intermediate cache may be local to the machine upon which the application is executing, or may be implemented within the storage system. In one embodiment where the application is a database server, the database system includes both a DB server-side intermediate cache, and a storage-side intermediate cache. The caching policies used to populate the intermediate cache are intelligent, taking into account factors that may include which object an item belongs to, the item type of the item, a characteristic of the item, or the type of operation in which the item is involved.

Caching data between a database server and a storage system

Techniques are provided for using an intermediate cache to provide some of the items involved in a scan operation, while other items involved in the scan operation are provided from primary storage. Techniques are also provided for determining whether to service an I/O request for an item with a copy of the item that resides in the intermediate cache based on factors such as a) an identity of the user for whom the I/O request was submitted, b) an identity of a service that submitted the I/O request, c) an indication of a consumer group to which the I/O request maps, or d) whether the intermediate cache is overloaded. Techniques are also provided for determining whether to store items in an intermediate cache in response to the items being retrieved, based on logical characteristics associated with the requests that retrieve the items.

Selectively reading data from cache and primary storage

Techniques are provided for using an intermediate cache between the shared cache of a database server and the non-volatile storage of a storage system. The intermediate cache may be local to the machine upon which the database server is executing, or may be implemented within the storage system. In one embodiment, the database system includes both a DB server-side intermediate cache, and a storage-side intermediate cache. The caching policies used to populate the intermediate cache are intelligent, taking into account factors that may include which database object an item belongs to, the item type of the item, a characteristic of the item; or the database operation in which the item is involved.

A method and apparatus for auto-tuning memory is provided. Memory on a computer system comprises at least one shared memory area and at least one private memory area. Addresses in the shared memory area are accessible to multiple processes. Addresses in the private memory area are dedicated to individual processes. Initially, a division in the amount of memory is established between the shared and private memory areas. Subsequently, a new division is determined. Consequently, memory from one memory area is 'given' to the other memory area. In one approach, such sharing is achieved by causing the shared and private memory areas to be physically separate from each other both before and after a change in the division. The division of the amount of memory may be changed to a new division by deallocating memory from one of the memory areas and allocating that memory to the other of the memory areas.

Managing memory in a system that includes a shared memory area and a private memory area

A method for starting up a database system, comprising allocating memory spaces for three buffers; initializing two of the buffers; partially initializing the third buffer where the third buffer is larger than the other two; instructing the memory manager to initialize the remainder of the third buffer in the background process; performing recovery operations; and opening the database system for use. The database is operated in an open phase while the remainder of the third buffer is initialized in the background and ran in parallel to the recovery operation that may extend beyond the completion of opening the database. Thus opening the database prior to completion of full initialization and initializing the third buffer in the background improves the startup time of the database which becomes significant when the size of the third buffer is very large (e.g., 500 GB+).

Method and system for faster instance startup for large resource configurations

Growing community of inventors

San Jose, CA, United States of America

Bharat C V Baddepudi