Patents by Inventor Rohan Aranha
Rohan Aranha has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Patent number: 9886490Abstract: Approaches for a persistent data store that may be used to service data queries originating from data warehousing applications, operational reporting applications, or data archiving and data feed applications. At periodic intervals, data may be extracted from one or more disparate data sources. The extracted data may be stored in the persistent data store in a tabular format. A backward delta data set is generated. The backward delta data set identifies what additions, deletions, and modifications need to be made to the data stored in the persistent data store to return the data to a most recent version. Backward delta data sets are stored and maintained in accordance with a policy that instructs two or more backward delta data sets, associated with a continuous interval of time, be combined into a single backward delta data set after the expiration of a specified amount of time.Type: GrantFiled: March 17, 2014Date of Patent: February 6, 2018Assignee: Numerify, Inc.Inventors: Rahul Kapoor, Gaurav Rewari, Rohan Aranha, Sadanand Sahasrabudhe
-
Patent number: 9870412Abstract: 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.Type: GrantFiled: September 26, 2012Date of Patent: January 16, 2018Assignee: Oracle International CorporationInventors: Sourav Ghosh, Ashish Motivala, Charles Hoch, Rohan Aranha, Ben Fulton, Andrey Gusev, Tirthankar Lahiri, Juan Tellez
-
Patent number: 8868504Abstract: A system includes an active node and a standby node and zero or more replica nodes. Each of the nodes includes a database system, such as an in-memory database system. Client updates applied to the active node are written through to the standby node, and the standby node writes the updates through to a primary database and updates the replica nodes. Commit ticket numbers tag entries in transaction logs and are used to facilitate recovery if either of the active node or the standby node fails. Updates applied to the primary database are autorefreshed to the active node and written through by the active node to the standby node which propagates the updates to the replica nodes. Bookmarks are used to track updated records of the primary database and are used to facilitate recovery if either of the active node or the standby node fails.Type: GrantFiled: February 12, 2008Date of Patent: October 21, 2014Assignee: Oracle International CorporationInventors: Rohan Aranha, Paul Tuck, John Ernest Miller, Chih-Ping Wang, Marie-Anne Neimat, Susan Sokeng Cheung
-
Patent number: 8738568Abstract: A replication track is a designated group of transactions that are to be replicated at a destination database in a way that, with respect to any other transaction in the replication track, preserves transactional dependency. Further, transactions in a replication track can be replicated at the destination database without regard to transactional dependency of other transactions in another track. This facilitates concurrent parallel replication of transactions of different tracks. Replicating data in this manner is referred to herein as track replication. An application may request execution of transactions and designate different tracks for transactions.Type: GrantFiled: May 5, 2011Date of Patent: May 27, 2014Assignee: Oracle International CorporationInventors: Sourav Ghosh, Rohan Aranha, Tirthankar Lahiri, Mark McAuliffe, Chih-Ping Wang, Paul Tuck, Nagender Bandi, John E. Miller, Dina Thomas, Marie-Anne Neimat
-
Publication number: 20120284228Abstract: A replication track is a designated group of transactions that are to be replicated at a destination database in a way that, with respect to any other transaction in the replication track, preserves transactional dependency. Further, transactions in a replication track can be replicated at the destination database without regard to transactional dependency of other transactions in another track. This facilitates concurrent parallel replication of transactions of different tracks. Replicating data in this manner is referred to herein as track replication. An application may request execution of transactions and designate different tracks for transactions.Type: ApplicationFiled: May 5, 2011Publication date: November 8, 2012Inventors: Sourav Ghosh, Rohan Aranha, Tirthankar Lahiri, Mark McAuliffe, Chih-Ping Wang, Paul Tuck, Nagender Bandi, John E. Miller, Dina Thomas, Marie-Anne Neimat
-
Patent number: 8306951Abstract: 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.Type: GrantFiled: March 8, 2010Date of Patent: November 6, 2012Assignee: Oracle International CorporationInventors: Sourav Ghosh, Ashish Motivala, Charles Hoch, Rohan Aranha, Ben Fulton, Andrey Gusev, Tirthankar Lahiri, Juan Tellez
-
Publication number: 20110071981Abstract: 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.Type: ApplicationFiled: March 8, 2010Publication date: March 24, 2011Inventors: Sourav Ghosh, Ashish Motivala, Charles Hoch, Rohan Aranha, Ben Fulton, Andrey Gusev, Tirthankar Lahiri, Juan Tellez
-
Publication number: 20080222159Abstract: A system includes an active node and a standby node and zero or more replica nodes. Each of the nodes includes a database system, such as an in-memory database system. Client updates applied to the active node are written through to the standby node, and the standby node writes the updates through to a primary database and updates the replica nodes. Commit ticket numbers tag entries in transaction logs and are used to facilitate recovery if either of the active node or the standby node fails. Updates applied to the primary database are autorefreshed to the active node and written through by the active node to the standby node which propagates the updates to the replica nodes. Bookmarks are used to track updated records of the primary database and are used to facilitate recovery if either of the active node or the standby node fails.Type: ApplicationFiled: February 12, 2008Publication date: September 11, 2008Applicant: Oracle International CorporationInventors: Rohan Aranha, Paul Tuck, John Ernest Miller, Chih-Ping Wang, Marie-Anne Neimat, Susan Sokeng Cheung