Oracle International Corporation

Ashish Motivala

Tirthankar Lahiri

Andrey Gusev

Juan Tellez

Rohan Aranha

Sourav Ghosh

Ben Fulton

Charles Hoch

Garret Frederick Swart

Nikunj R Mehta

Colm Divilly

A cluster manager manages copies of a mid-tier database as a mid-tier database cluster. The cluster manager may concurrently manage a backend database system. The cluster manager is configured to monitor for and react to failures of mid-tier database nodes. The cluster manager may react to a mid-tier database failure by, for example, assigning a new active node, creating a new standby node, creating new copies of the mid-tier databases, implementing new replication or backup schemes, reassigning the node's virtual address to another node, or relocating applications that were directly linked to the mid-tier database to another host. Each node or an associated agent may configure the cluster manager during initialization, based on common cluster configuration information. Each copy of the mid-tier database may be, for example, a memory resident database. Thus, a node must reload the entire database into memory to recover a copy of the database.

Automated integrated high availability of the in-memory database cache and the backend enterprise database

Techniques for facilitating communication between an application and a server are provided. An intermediary sits between an application and a server. The intermediary intercepts and responds to communications on behalf of the intended recipient of the communication. In one technique, the intermediary relays a request to the server and receives a response from the server. The intermediary updates a local store with data that is implied by the protocol to which the request conforms and determined based on the request. In another technique, the intermediary intercepts a request to access data on the server. The intermediary determines, based on characteristics of a computing device, that the request should be responded to using data that is available in a local store. The intermediary responds to the request using that data.

Adaptive write-back and write-through caching for off-line data

A cluster manager is configured to manage a plurality of copies of a mid-tier database as a mid-tier database cluster. The cluster manager may concurrently manage a backend database system. The cluster manager is configured to monitor for and react to failures of mid-tier database nodes. The cluster manager may react to a mid-tier database failure by, for example, assigning a new active node, creating a new standby node, creating new copies of the mid-tier databases, implementing new replication or backup schemes, reassigning the node's virtual address to another node, or relocating applications that were directly linked to the mid-tier database to another host. Each node or an associated agent may configure the cluster manager to behave in this fashion during initialization, based on common cluster configuration information. Each copy of the mid-tier database may be, for example, a memory resident database. Thus, a node must reload the entire database into memory to recover a copy of the database.

Growing community of inventors

San Francisco, CA, United States of America

Ashish Motivala