公开(公告)号：US11068437B2

公开(公告)日：2021-07-20

申请号：US15266340

申请日：2016-09-15

Applicant: Oracle International Corporation

Inventor： Margaret Susairaj ,  Giridhar Ravipati ,  Kumar Rajamani ,  Yunrui Li ,  Jaebock Lee ,  Sanket Jain

IPC: G06F7/00 ,  G06F16/11 ,  G06F11/14

Abstract: Techniques are provided for using a sparse file to create a hot archive of a pluggable database of a container database. In an embodiment and while a source pluggable database is in service, a source database server creates a clone of the source pluggable database. Also while the source pluggable database is in service, the source database server creates an archive of the source pluggable database that is based on the clone. Eventually, a need arises to consume the archive. A target database server (which may also be the source database server) creates a target pluggable database based on the archive.

公开(公告)号：US20200026774A9

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

申请号：US15266340

申请日：2016-09-15

Applicant: Oracle International Corporation

Inventor： Margaret Susairaj ,  Giridhar Ravipati ,  Kumar Rajamani ,  Yunrui Li ,  Jaebock Lee ,  Sanket Jain

IPC: G06F17/30 ,  G06F11/14

Abstract: Techniques are provided for using a sparse file to create a hot archive of a pluggable database of a container database. In an embodiment and while a source pluggable database is in service, a source database server creates a clone of the source pluggable database. Also while the source pluggable database is in service, the source database server creates an archive of the source pluggable database that is based on the clone. Eventually, a need arises to consume the archive. A target database server (which may also be the source database server) creates a target pluggable database based on the archive.

公开(公告)号：US20170116213A1

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

申请号：US15093506

申请日：2016-04-07

Applicant: Oracle International Corporation

Inventor： Sanket Jain ,  Kumar Rajamani ,  Jaebock Lee ,  Nicolas Michael ,  Yixiao Shen ,  Giridhar Ravipati

IPC: G06F17/30

CPC classification number: G06F16/24566 ,  G06F16/172 ,  G06F16/214 ,  G06F16/258

Abstract: Embodiments provide a migration instruction that effectuates the migration of a pluggable database from a source database server instance to a destination database server instance. Upon receiving the migration instruction, the migrating pluggable database is opened at the destination instance. Connections are terminated at the source instance at a rate that is determined based on statistics maintained for one or more of: the migrating pluggable database, the source instance, the destination instance, a container database, etc. Furthermore, once the migration instruction is received, a certain amount of time is provided before the source instance flushes the dirty buffers for the migrating pluggable database from the buffer cache of the source instance. The delay in flushing dirty buffers from buffer cache allows the source instance to provide data blocks, of the migrating pluggable database, directly to the destination database server instance from the cache.

公开(公告)号：US20140095546A1

公开(公告)日：2014-04-03

申请号：US13841272

申请日：2013-03-15

Applicant: ORACLE INTERNATIONAL CORPORATION

Inventor： Andre KRUGLIKOV ,  Kumar Rajamani ,  Jaebock Lee ,  Sanket Jain ,  Giridhar Ravipati

IPC: G06F21/62

CPC classification number: G06F3/0619 ,  G06F3/065 ,  G06F3/067 ,  G06F11/1448 ,  G06F11/1469 ,  G06F11/1471 ,  G06F12/084 ,  G06F13/1663 ,  G06F17/30289 ,  G06F17/30292 ,  G06F17/3048 ,  G06F17/30557 ,  G06F17/30566 ,  G06F17/30595 ,  G06F17/30867 ,  G06F21/6218 ,  G06F2201/80 ,  G06F2201/835 ,  G06F2212/60 ,  G06F2212/62

Abstract: Techniques for common users and roles, and commonly-granted privileges and roles are described. In one approach, the DBMS of a container database allows for the creation of common roles and common users that are shared across the container database. Thus, when a common role or a common user is established, the common role or common user is propagated to each database of the container database. In another approach, the DBMS of a container database allows privileges and roles to be granted commonly or locally. When a privilege or role is granted commonly, the privilege applies in each of the databases of a container database. When a privilege or role is granted locally, the privilege applies only in the database to which the grantor of the privilege or role established a connection.

Abstract translation: 描述了普通用户和角色的技术以及常用权限和角色。 在一种方法中，容器数据库的DBMS允许创建跨容器数据库共享的常见角色和通用用户。 因此，当建立常见角色或公共用户时，常见角色或普通用户将被传播到容器数据库的每个数据库。 在另一种方法中，容器数据库的DBMS允许通常或本地授予权限和角色。 通常授予特权或角色时，特权将应用于容器数据库的每个数据库。 当本地授予特权或角色时，权限仅适用于权限或角色的授予人建立连接的数据库。

公开(公告)号：US11386058B2

公开(公告)日：2022-07-12

申请号：US16135769

申请日：2018-09-19

Applicant: Oracle International Corporation

Inventor： Hochak Hung ,  Kumar Rajamani ,  Jaebock Lee ,  Sanket Jain ,  Giridhar Ravipati ,  John McHugh ,  Churn Don Lee ,  Alexander Chen ,  Jen-Cheng Huang

IPC: G06F16/21 ,  G06F16/25 ,  G06F16/27 ,  G06N5/02 ,  H04L12/24 ,  G06N20/00 ,  H04L29/08 ,  H04L41/085 ,  H04L41/5003 ,  H04L67/562 ,  H04L67/55 ,  H04L41/0853

Abstract: Provided herein are data cloud administration techniques that achieve autonomy by using a rules engine that reacts to a database system event by autonomously submitting an asynchronous job to reconfigure a database. In an embodiment, a rules engine receives an event from a DBMS. Based on the event, the rules engine executes a rule to generate a request that indicates configuration details for a database. The rules engine sends the request to a request broker. The request broker dispatches an asynchronous job based on the request. The asynchronous job configures the database based on the configuration details. Thus, databases in a cloud, data grid, or data center may be administered autonomously (without human intervention) base on dynamic conditions that are foreseen and unforeseen.

公开(公告)号：US11327932B2

公开(公告)日：2022-05-10

申请号：US16055468

申请日：2018-08-06

Applicant: Oracle International Corporation

Inventor： Hochak Hung ,  Kumar Rajamani ,  Sanket Jain ,  Giridhar Ravipati ,  Jaebock Lee ,  Alexander Chen ,  Jen-Cheng Huang

IPC: G06F16/21 ,  G06F9/50 ,  G06F16/27 ,  G06F9/455 ,  G06F9/48

Abstract: Provided herein are workload management techniques that asynchronously configure pluggable databases within a compute cloud. In an embodiment, the compute cloud receives an administrative request that indicates configuration details for a pluggable database. The compute cloud generates a configuration descriptor that specifies an asynchronous job based on the configuration details of the request. The compute cloud accesses hosting metadata to detect at least one of: a) a current container database that already hosts the pluggable database, b) a target container database that will host the pluggable database, or c) a particular computer that hosts at least one of: the current container database, or the target container database. The compute cloud executes the asynchronous job to configure the pluggable database based on at least one of: the hosting metadata, or the configuration descriptor. Thread pools, lanes, and queues may facilitate load balancing to avoid priority inversion, starvation, and denial of service.

公开(公告)号：US10922331B2

公开(公告)日：2021-02-16

申请号：US15215435

申请日：2016-07-20

Applicant: Oracle International Corporation

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

IPC: G06F16/00 ,  G06F16/27 ,  G06F16/13 ,  G06F16/11 ,  G06F16/178 ,  G06F16/23

Abstract: Embodiments create a clone of a PDB while the PDB accepts write operations. While the PDB remains in read-write mode, the DBMS copies the data of the PDB and sends the data to a destination location. The DBMS performs data recovery on the PDB clone based on redo entries that record changes made to the source PDB while the DBMS copied the source PDB files. This data recovery makes all changes, to the PDB clone, that occurred to the source PDB during the copy operation. The redo information, on which the data recovery is based, is foreign to the PDB clone since the redo entries were recorded for a different PDB. In order to apply foreign redo information to perform recovery on the PDB clone, a DBMS managing the PDB clone maintains mapping information that maps PDB source reference information to corresponding information for the PDB clone.

公开(公告)号：US20190102384A1

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

申请号：US16055468

申请日：2018-08-06

Applicant: Oracle International Corporation

Inventor： Hochak Hung ,  Kumar Rajamani ,  Sanket Jain ,  Giridhar Ravipati ,  Jaebock Lee ,  Alexander Chen ,  Jen-Cheng Huang

IPC: G06F17/30 ,  G06F9/50 ,  G06F9/455

Abstract: Provided herein are workload management techniques that asynchronously configure pluggable databases within a compute cloud. In an embodiment, the compute cloud receives an administrative request that indicates configuration details for a pluggable database. The compute cloud generates a configuration descriptor that specifies an asynchronous job based on the configuration details of the request. The compute cloud accesses hosting metadata to detect at least one of: a) a current container database that already hosts the pluggable database, b) a target container database that will host the pluggable database, or c) a particular computer that hosts at least one of: the current container database, or the target container database. The compute cloud executes the asynchronous job to configure the pluggable database based on at least one of: the hosting metadata, or the configuration descriptor. Thread pools, lanes, and queues may facilitate load balancing to avoid priority inversion, starvation, and denial of service.

公开(公告)号：US20140164331A1

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

申请号：US14135202

申请日：2013-12-19

Applicant: Oracle International Corporation

Inventor： Yunrui Li ,  Chi Cao Minh ,  Kumar Rajamani ,  Jaebock Lee ,  Sanket Jain ,  Giridhar Ravipati ,  Jonghyun Lee

IPC: G06F11/14 ,  G06F17/30

CPC classification number: G06F3/0619 ,  G06F3/065 ,  G06F3/067 ,  G06F11/1448 ,  G06F11/1469 ,  G06F11/1471 ,  G06F12/084 ,  G06F13/1663 ,  G06F17/30289 ,  G06F17/30292 ,  G06F17/3048 ,  G06F17/30557 ,  G06F17/30566 ,  G06F17/30595 ,  G06F17/30867 ,  G06F21/6218 ,  G06F2201/80 ,  G06F2201/835 ,  G06F2212/60 ,  G06F2212/62

Abstract: A container database stores redo records and logical timestamps for multiple pluggable databases. When it is detected that a first read-write instance of the pluggable database is opened and no other read-write instances of the pluggable database are open, offline range data associated with the pluggable database is updated. When it is detected that a second read-write instance of the pluggable database is closed, and the second read-write instance is the last open read-write instance, the offline range data associated with the pluggable database is updated. The pluggable database is restored to a logical timestamp associated with a restore request based on the offline range data.

Abstract translation: 容器数据库存储多个可插拔数据库的重做记录和逻辑时间戳。 当检测到可插拔数据库的第一个读写实例被打开，并且没有可插拔数据库的其他读写实例被打开时，与可插拔数据库关联的脱机范围数据被更新。 当检测到可插拔数据库的第二读写实例被关闭，并且第二读写实例是最后打开的读写实例时，更新与可插拔数据库相关联的脱机范围数据。 基于离线范围数据，可插拔数据库恢复到与恢复请求相关联的逻辑时间戳。

公开(公告)号：US10915549B2

公开(公告)日：2021-02-09

申请号：US15215443

申请日：2016-07-20

Applicant: Oracle International Corporation

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

IPC: G06F16/00 ,  G06F16/27 ,  G06F16/13 ,  G06F16/11 ,  G06F16/178 ,  G06F16/23

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.