公开(公告)号：US10732836B2

公开(公告)日：2020-08-04

申请号：US15720949

申请日：2017-09-29

Applicant: Oracle International Corporation

Inventor： Jia Shi ,  Yiliang Jin ,  Zheren R. Zhang ,  Zuoyu Tao ,  Vijay Sridharan ,  Kothanda Umamageswaran ,  Graham Ivey ,  Yunrui Li

IPC: G06F7/00 ,  G06F17/30 ,  G06F3/06 ,  G06F13/28 ,  G06F16/23 ,  G06F9/455 ,  G06F12/02 ,  G06F12/0871 ,  H04L29/08

Abstract: A shared storage architecture persistently stores database files in non-volatile random access memories (NVRAMs) of computing nodes of a multi-node DBMS. The computing nodes of the multi-node DBMS not only collectively store database data on NVRAMs of the computing nodes, but also host database server instances that process queries in parallel, host database sessions and database processes, and together manage access to a database stored on the NVRAMs of the computing nodes. To perform a data block read operation from persistent storage, a data block may be transferred directly over a network between NVRAM of a computing node that persistently stores the data block to a database buffer in non-volatile RAM of another computing node that requests the data block. The transfer is accomplished using remote direct memory access (“RDMA). In addition to techniques for performing a data block read operation to NVRAM, computing nodes perform a data block write operation to data blocks stored in NVRAM of the NVRAM shared storage architecture. The data block write operation is referred to herein as a one-sided write because only one database process needs to participate in the writing of a data block to NVRAM in order to successfully commit the write.

公开(公告)号：US10698771B2

公开(公告)日：2020-06-30

申请号：US15266375

申请日：2016-09-15

Applicant: Oracle International Corporation

Inventor： Hongjie Yang ,  Yunrui Li ,  Mahesh Baburao Girkar

IPC: G06F7/00 ,  G06F17/00 ,  G06F11/14 ,  G06F16/27 ,  G06F11/20

Abstract: Herein are techniques of zero data loss with asynchronously replicated redo logs. In an embodiment, a first server instance (FSI) of a plurality of server instances (PSI) of a primary database (PDB) sends, to a standby database (SDB) during an shutdown of FSI, a first recovery count (RC) and a remainder of an instance redo log (IRL). In response to recovering FSI, a second server instance of PSI increments a recovery counter to a second RC (SRC), publishes SRC to PSI, and sends SRC to SDB. After restarting FSI, FSI makes a change to contents of PDB, and stores, into IRL, a redo entry that defines the change. During failover, a database management system (DBMS) detects whether RCs associated with FSRL and SSRL are unanimous. If unanimous, DBMS fully rolls forward SDB by replaying FSRL and SSRL. Otherwise, DBMS limits replay and indicates that FSRL and SSRL might be inconsistent.

公开(公告)号：US20200026609A9

公开(公告)日：2020-01-23

申请号：US15254884

申请日：2016-09-01

Applicant: Oracle International Corporation

Inventor： Kumar Rajamani ,  Muthu Olagappan ,  Yunrui Li ,  Giridhar Ravipati ,  Jing Zheng

IPC: G06F11/14 ,  G06F17/30

Abstract: Techniques are provided for creating a backup of a source pluggable database (SPD) of a source container database and porting the backup for recovery into a different target container database. In an embodiment, a source database server retrieves metadata that describes backups of the SPD. The source database server inserts, into a unplugged pluggable database of the SPD, the metadata that describes each of the backups. For example, unplugging the SPD may automatically create the unplugged pluggable database. Eventually, the unplugged pluggable database may be plugged into the target container database. A target database server transfers the metadata that describes each of the backups from the unplugged pluggable database and into the target container database. Based on at least one backup and the metadata that describes backups of the SPD, the target database server restores a target pluggable database within the target container database.

公开(公告)号：US20190102087A1

公开(公告)日：2019-04-04

申请号：US15720949

申请日：2017-09-29

Applicant: Oracle International Corporation

Inventor： Jia Shi ,  Yiliang Jin ,  Zheren R. Zhang ,  Zuoyu Tao ,  Vijay Sridharan ,  Kothanda Umamageswaran ,  Graham Ivey ,  Yunrui Li

IPC: G06F3/06 ,  G06F9/455 ,  G06F12/02 ,  G06F12/0871 ,  H04L29/08

Abstract: A shared storage architecture persistently stores database files in non-volatile random access memories (NVRAMs) of computing nodes of a multi-node DBMS. The computing nodes of the multi-node DBMS not only collectively store database data on NVRAMs of the computing nodes, but also host database server instances that process queries in parallel, host database sessions and database processes, and together manage access to a database stored on the NVRAMs of the computing nodes. To perform a data block read operation from persistent storage, a data block may be transferred directly over a network between NVRAM of a computing node that persistently stores the data block to a database buffer in non-volatile RAM of another computing node that requests the data block. The transfer is accomplished using remote direct memory access (“RDMA). In addition to techniques for performing a data block read operation to NVRAM, computing nodes perform a data block write operation to data blocks stored in NVRAM of the NVRAM shared storage architecture. The data block write operation is referred to herein as a one-sided write because only one database process needs to participate in the writing of a data block to NVRAM in order to successfully commit the write.

公开(公告)号：US20190012244A1

公开(公告)日：2019-01-10

申请号：US15643294

申请日：2017-07-06

Applicant: Oracle International Corporation

Inventor： Anjan Kumar Amirishetty ,  Yunrui Li ,  Tolga Yurek ,  Wilson Wai Shun Chan

IPC: G06F11/20 ,  G06F17/30

CPC classification number: G06F11/2023 ,  G06F9/52 ,  G06F11/1471 ,  G06F11/1474 ,  G06F16/2336 ,  G06F16/273 ,  G06F17/30578 ,  G06F2201/80 ,  G06F2201/825 ,  H04L67/1097

Abstract: Techniques are described herein for quick identification of a set of units of data for which recovery operations are to be performed to redo or undo changes made by the failed node. When a lock is requested by an instance, lock information for the lock request is replicated by another instance. If the instance fails, the other instance may use the replicated lock information to determine a set of data blocks for recovery operations. The set of data blocks is available in memory of a recovery instance when a given node fails, and does not have to be completely generated by scanning a redo log.

公开(公告)号：US20180121511A1

公开(公告)日：2018-05-03

申请号：US15339525

申请日：2016-10-31

Applicant: Oracle International Corporation

Inventor： Yunrui Li ,  Kumar Rajamani

IPC: G06F17/30

CPC classification number: G06F16/24549 ,  G06F16/2282 ,  G06F16/2358 ,  G06F16/2365 ,  G06F16/2379 ,  G06F16/2477 ,  G06F16/256 ,  G06F16/27 ,  G06F16/951

Abstract: A refreshable PDB clone is associated with a PDB-specific logical timestamp (LT) service that continuously reflects the LT of the most recent changes that have fully committed within the PDB clone during a refresh operation. Such an LT service is used to perform queries over the changing data in the PDB clone while the PDB clone is undergoing a refresh operation. Furthermore, a PDB-specific LT service can facilitate write operations in a standby CDB, where the standby CDB is a physical standby of a source CDB. Specifically, a standby CDB is configured with a private read-write PDB that does not replicate data from the source CDB. This private PDB may accommodate a write operation required by a query over data in the standby CDB. A PDB-specific LT service provides LTs for such a private PDB where the PDB-specific LT service provides LTs to order changes made within the private PDB.

公开(公告)号：US20180060181A1

公开(公告)日：2018-03-01

申请号：US15254884

申请日：2016-09-01

Applicant: Oracle International Corporation

Inventor： Kumar Rajamani ,  Muthu Olagappan ,  Yunrui Li ,  Giridhar Ravipati ,  Jing Zheng

IPC: G06F11/14 ,  G06F17/30

Abstract: Techniques are provided for creating a backup of a source pluggable database (SPD) of a source container database and porting the backup for recovery into a different target container database. In an embodiment, a source database server retrieves metadata that describes backups of the SPD. The source database server inserts, into a unplugged pluggable database of the SPD, the metadata that describes each of the backups. For example, unplugging the SPD may automatically create the unplugged pluggable database. Eventually, the unplugged pluggable database may be plugged into the target container database. A target database server transfers the metadata that describes each of the backups from the unplugged pluggable database and into the target container database. Based on at least one backup and the metadata that describes backups of the SPD, the target database server restores a target pluggable database within the target container database.

公开(公告)号：US20170116298A1

公开(公告)日：2017-04-27

申请号：US15215443

申请日：2016-07-20

Applicant: Oracle International Corporation

Inventor： Giridhar Ravipati ,  Kumar Rajamani ,  Yunrui Li ,  Muthu Olagappan ,  Jaebock Lee ,  Sanket Jain

IPC: G06F17/30 ,  G06F11/14

CPC classification number: G06F16/27 ,  G06F11/14 ,  G06F11/1469 ,  G06F16/119 ,  G06F16/13 ,  G06F16/178 ,  G06F16/214 ,  G06F16/2358 ,  G06F16/2365 ,  G06F16/273 ,  G06F2201/84

Abstract: Embodiments incrementally refresh a clone of a source PDB while the source PDB accepts write operations. Specifically, refreshing the PDB clone incorporates changes made to the source PDB since a refresh reference time stamp, which marks the time at which the PDB clone was created or, if the PDB clone has been previously refreshed, the time at which the PDB clone was last refreshed. A PDB clone is incrementally refreshed by incorporating, into the PDB clone data, those source data blocks that have changed since the refresh reference time stamp. Recovery is performed on the PDB clone, once the blocks are copied, to apply any changes made to the source PDB while the blocks were being copied, which recovery makes the PDB clone files consistent. This recovery is based on redo entries recorded for the source PDB during the time it took to copy the blocks to the PDB clone.

公开(公告)号：US09514160B2

公开(公告)日：2016-12-06

申请号：US13794112

申请日：2013-03-11

Applicant: Oracle International Corporation

Inventor： Shanshan Song ,  Yunrui Li ,  Tolga Yurek ,  Mahesh Girkar ,  Neil MacNaughton

IPC: G06F17/30

CPC classification number: G06F17/30289 ,  G06F17/30575 ,  G06F17/30581

Abstract: A method, system, and computer program product. The method for non-intrusive redeployment of a standby database facility comprises configuring a database system having a shared lock manager process to synchronize two or more concurrent access instances, then granting lock requests for access to a cache of database blocks. At some moment in time, the shared lock manager process may fail, and a monitor process detects the failure or other stoppage of the shared lock manager process. A new shared lock manager process and other processes are started, at least one of which serves for identifying the database blocks in the cache that have not yet been written to the database. The identified blocks are formed into a recovery set of redo operations. During this time, incoming requests for access to the cache of database blocks are briefly blocked, at least until the recovery set of redo operations has been formed.

Abstract translation: 一种方法，系统和计算机程序产品。 用于非侵入式重新部署备用数据库设施的方法包括配置具有共享锁管理器进程的数据库系统以同步两个或多个并发访问实例，然后授予对数据库块的高速缓存的锁定请求。 在某个时刻，共享锁管理器进程可能会失败，并且监视进程检测到共享锁管理器进程的故障或其他停止。 启动新的共享锁管理器进程和其他进程，其中至少一个用于识别高速缓存中尚未写入数据库的数据库块。 所识别的块被形成恢复一组重做操作。 在此期间，暂时阻止访问数据库块的缓存的传入请求，至少在恢复组重做操作已经形成之前。

公开(公告)号：US09189502B2

公开(公告)日：2015-11-17

申请号：US13630582

申请日：2012-09-28

Applicant: Oracle International Corporation

Inventor： Vsevolod Panteleenko ,  Yunrui Li ,  Jonghyun Lee ,  Margaret M. Susairaj ,  William H. Bridge, Jr. ,  Vinay Srihari

IPC: G06F17/30

CPC classification number: G06F17/303

Abstract: Techniques for moving data files without interrupting access are described. A first process moves a database file from a first location to a second location while the database file is accessible to one or more other processes for read or write operations. According to one technique, the first process communicates a move status and a copy range into the database file to one or more database server instances executing the one or more other processes. The one or more other processes then perform input/output (IO) operations on the database file based at least in part on the move status and the copy range communicated by the first process.

Abstract translation: 描述了在不中断访问的情况下移动数据文件的技术。 第一个进程将数据库文件从第一个位置移动到第二个位置，而数据库文件可被一个或多个其他进程访问以进行读取或写入操作。 根据一种技术，第一过程将移动状态和复制范围传达到数据库文件中，以执行一个或多个其他进程的一个或多个数据库服务器实例。 所述一个或多个其他进程至少部分地基于由第一进程传送的移动状态和复制范围对数据库文件执行输入/输出（IO）操作。