Benedicto E Garin

7996363, Aug 9, 2011

Aug 27, 2004

10/927927

Mahesh Girkar - Cupertino CA, US
Benedicto Garin - Hudson NH, US
Joydip Kundu - Derry NH, US

Oracle International Corporation - Redwood Shores CA

G06F 17/00

707638, 707640

A method and apparatus for applying changes to a standby database in real-time. According to one aspect, a change is applied to data contained in a standby database. The standby database functions as a replica of a primary database. The primary database has a current online redo log file to which a particular redo block was written. According to one aspect, prior to the archiving of the current online redo log file, the particular redo block is received at a process associated with the standby database. A change indicated by the particular redo block is applied to the data contained in the standby database.

20070083574, Apr 12, 2007

Oct 28, 2005

11/261221

Benedicto Garin - Hudson NH, US
Robert McGuirk - Nashua NH, US
Mahesh Girkar - Cupertino CA, US

ORACLE INTERNATIONAL CORPORATION - REDWOOD SHORES CA

G06F 17/30

707204000

Systems, methods, and other embodiments associated with remote database maintenance using parallel file transfers are described. One exemplary system includes a processor configured to run a database management system (DBMS) that is in turn configured to manage a database (DB). The DBMS may maintain a database log file that stores information about changes to the database. The system may also include a connection logic for establishing data transfer connections between the computing system and a remote computing system storing the database replica. The system may also include a partition logic that separates the database log file into multiple portions and a distribution logic that provides the multiple file portions in parallel to the remote computing system through the multiple data transfer connections.

20080091737, Apr 17, 2008

Oct 31, 2007

11/930834

Steven Lee - Hollis NH, US
Sadhana Kyathappala - Westford MA, US
Benedicto Garin - Hudson NH, US

G06F 17/00

707200000, 707E17010

Techniques used in an automatic failover configuration having a primary database system, a standby database system, and an observer. In the automatic failover configuration, the primary database system remains available even in the absence of both the standby and the observer as long as the standby and the observer become absent sequentially. The failover configuration may use asynchronous transfer modes to transfer redo to the standby and permits automatic failover only when the observer is present and the failover will not result in data loss due to the asynchronous transfer mode beyond a specified maximum. The database systems and the observer have copies of failover configuration state and the techniques include techniques for propagating the most recent version of the state among the databases and the observer and techniques for using carefully-ordered writes to ensure that state changes are propagated in a fashion which prevents divergence.

20080126845, May 29, 2008

Nov 24, 2006

11/604063

Jiangbin Luo - Nashua NH, US
George H. Claborn - Amherst NH, US
Stephen John Vivian - Londonderry NH, US
Steve Tiahung Lee - Hollis NH, US
Raymond Guzman - Amherst NH, US
Douglas Andrew Voss - Nashua NH, US
Benedicto Elmo Garin - Hudson NH, US

G06F 11/30

714 6, 714E11007

Techniques used in an automatic failover configuration having a primary database system, a standby database system, and an observer for preventing divergence among the primary and standby database systems while increasing the availability of the primary database system. In the automatic failover configuration, the primary database system remains available even in the absence of both the standby and the observer as long as the standby and the observer become absent sequentially. The failover configuration further permits automatic failover only when the observer is present and the standby and the primary are synchronized and inhibits state changes during failover. The database systems and the observer have copies of failover configuration state and the techniques include techniques for propagating the most recent version of the state among the databases and the observer and techniques for using carefully-ordered writes to ensure that state changes are propagated in a fashion which prevents divergence.

20080126846, May 29, 2008

Nov 24, 2006

11/604064

Stephen John Vivian - Londonderry NH, US
Raymond Guzman - Amherst NH, US
Douglas Andrew Voss - Nashua NH, US
Benedicto Elmo Garin - Hudson NH, US

G06F 11/30

714 6, 714E11007

Techniques used in an automatic failover configuration having a primary database system, a standby database system, and an observer for preventing divergence among the primary and standby database systems while increasing the availability of the primary database system. In the automatic failover configuration, the primary database system remains available even in the absence of both the standby and the observer as long as the standby and the observer become absent sequentially. The failover configuration further permits automatic failover only when the observer is present and the standby and the primary are synchronized and inhibits state changes during failover. The database systems and the observer have copies of failover configuration state and the techniques include techniques for propagating the most recent version of the state among the databases and the observer and techniques for using carefully-ordered writes to ensure that state changes are propagated in a fashion which prevents divergence.

20130282666, Oct 24, 2013

Apr 24, 2012

13/454799

Steven McGee - Bedford NH, US
Jiangbin Luo - Bedford NH, US
Benedicto Garin - Hollis NH, US
Mahesh Girkar - Cupertino CA, US
Michael Harvey - Hollis NH, US
Nitin Karkhanis - Nashua NH, US
Steve Lee - Hollis NH, US
Juan Loaiza - Woodside CA, US
Robert McGuirk - Nashua NH, US
Hongjie Yang - Foster City CA, US

Oracle International Corporation - Redwood Shores CA

G06F 17/30

707683, 707E17005

Disclosed are methods and apparatuses to provide a redo repeater that allows for no data loss protection without the performance impact to the primary database even when a significant geographical distance separates the primary and standby databases. The Repeater is a lightweight entity that receives redo from the primary database with the purpose of redistributing that redo throughout the primary/standby system configuration. The Repeater able to extend no data loss protection and switchover functionality to terminal standby databases even though the primary database does not need to have a direct connection with those destinations.

6963957, Nov 8, 2005

Jan 7, 2003

10/337309

Joydip Kundu - Nashua NH, US
Qinqin Wang - Nashua NH, US
Benedicto Garin - Nashua NH, US

Oracle International Corporation - Redwood Shores CA

G06F012/12

711160

The present invention is a paging scheme that provides improved performance for various applications. In one embodiment of the present invention, a method of paging data comprises the steps of storing a plurality of pages of data in a main memory, determining that paging must occur, and paging out a page of data from the main memory based on the memory pressure of the page of data. The paging out step may comprise the steps of determining an amount of time a page is or will be in memory for each of the plurality of pages of data in the main memory and determining a memory pressure for each of the plurality of pages of data in the main memory.

20190026353, Jan 24, 2019

Sep 27, 2018

16/144126

- Redwood Shores CA, US
Jiangbin Luo - Bedford NH, US
Benedicto GARIN - Hollis NH, US
Mahesh Girkar - Cupertino CA, US
Michael Harvey - Hollis NH, US
Nitin Karkhanis - Nashua NH, US
Steve Lee - Hollis NH, US
Juan Loaiza - Woodside CA, US
Robert McGuirk - Nashua NH, US
Hongjie Yang - Foster City CA, US

Oracle International Corporation - Redwood Shores CA

G06F 17/30

Disclosed are methods and apparatuses to provide a redo repeater that allows for no data loss protection without the performance impact to the primary database even when a significant geographical distance separates the primary and standby databases. The Repeater is a lightweight entity that receives redo from the primary database with the purpose of redistributing that redo throughout the primary/standby system configuration. The Repeater able to extend no data loss protection and switchover functionality to terminal standby databases even though the primary database does not need to have a direct connection with those destinations.