公开(公告)号：US20150363610A1

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

申请号：US14835507

申请日：2015-08-25

Applicant: ORACLE INTERNATIONAL CORPORATION

Inventor： Andre KRUGLIKOV ,  Kumar RAJAMANI ,  Jaebock LEE ,  Sanket JAIN ,  Giridhar RAVIPATI

IPC: G06F21/62 ,  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: 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允许通常或本地授予权限和角色。 通常授予特权或角色时，特权将应用于容器数据库的每个数据库。 当本地授予特权或角色时，权限仅适用于权限或角色的授予人建立连接的数据库。

公开(公告)号：US20220179753A1

公开(公告)日：2022-06-09

申请号：US17113091

申请日：2020-12-06

Applicant: Oracle International Corporation

Inventor： Giridhar RAVIPATI ,  Yunrui LI ,  Kumar RAJAMANI ,  Muthu OLAGAPPAN

IPC: G06F11/14

Abstract: A computer program product, system, and computer implemented method for management of a consolidated database and implementing pluggable database recovery with efficient redo filtering in a consolidated database according to some embodiments. Generally, the process includes ongoing activities that maintain activity logs and summarize the activity for respective activity logs (e.g., in an activity vector maintained in a consolidated database catalog). In some embodiments, event-based activities corresponding to recovery processes are triggered by an administrator or an automated process, completed and then do not occur again until another triggering event. The event-based activities can leverage the summary information to quickly determine which online activity logs are relevant to the type of recovery operation for a particular pluggable database. In this way the approach provided herein enables recovery without requiring that all log activity be analyzed to determine whether it is relevant to a particular pluggable database.