中科微点-全球专利检索

  1. Login
  2. Sign Up

Search Results

39 records (took 0.03 seconds)

    Multi-version concurrency control on in-memory snapshot store of oracle in-memory database
    27.
    发明授权
    Multi-version concurrency control on in-memory snapshot store of oracle in-memory database 有权
    oracle内存数据库的内存中快照存储的多版本并发控制

    公开(公告)号：US09128972B2

    公开(公告)日：2015-09-08

    申请号：US14337183

    申请日：2014-07-21

    Applicant: Oracle International Corporation

    Inventor： Vivekanandhan Raja ,  Sanket Hase ,  Amit Ganesh ,  Vineet Marwah ,  Shuang Su ,  Atrayee Mullick ,  Sukhada Pendse

    IPC: G06F17/30

    CPC classification number: G06F17/30371 ,  G06F17/30324 ,  G06F17/30356 ,  G06F17/30507 ,  G06F17/30578 ,  G06F17/30581

    Abstract: Techniques are provided for maintaining data persistently in one format, but making that data available to a database server in more than one format. For example, one of the formats in which the data is made available for query processing is based on the on-disk format, while another of the formats in which the data is made available for query processing is independent of the on-disk format. Data that is in the format that is independent of the disk format may be maintained exclusively in volatile memory to reduce the overhead associated with keeping the data in sync with the on-disk format copies of the data.

    Abstract translation: 提供的技术用于以一种格式持续保持数据，但使数据库可以以多种格式提供给数据库服务器。 例如，数据可用于查询处理的格式之一是基于磁盘格式，而数据可用于查询处理的其他格式与磁盘格式无关。 独立于磁盘格式的格式的数据可以专门保存在易失性存储器中，以减少与保持数据与数据的磁盘格式副本同步的开销。

    IN PLACE POINT-IN-TIME RECOVERY OF PLUGGABLE DATABASES
    28.
    发明申请
    IN PLACE POINT-IN-TIME RECOVERY OF PLUGGABLE DATABASES 有权
    在可插拔数据库中的时间点恢复

    公开(公告)号：US20140095452A1

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

    申请号：US13830349

    申请日：2013-03-14

    Applicant: ORACLE INTERNATIONAL CORPORATION

    Inventor： J. William LEE ,  Vipin Gokhale ,  Muthu Olagappan ,  Sanket Hase ,  Vivekanandhan Raja ,  Michael John Skarpelos ,  Michael Stewart

    IPC: G06F11/14

    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: In an approach, a database server maintains a container database which comprises: one or more pluggable databases, a root database that stores an undo log for rolling back transactions on the consolidated database, and a redo log for replaying modifications to the container database. The database server restores a particular pluggable with a backup version that corresponds to a first point in time. The database server generates a clone database loaded with a backup version of the root database that corresponds to the first point in time. The database server applies the redo log to recover the particular pluggable database and the clone database to a second point in time that is later than the first point in time. The database server identifies, based on the clone database, one or more active transactions on the particular pluggable database. The database server rolls back the one or more active transactions.

    Abstract translation: 在一种方法中，数据库服务器维护容器数据库，其中包括：一个或多个可插拔数据库，存储用于在统一数据库上回退事务的撤销日志的根数据库，以及用于重播对容器数据库的修改的重做日志。 数据库服务器使用与第一个时间点对应的备份版本恢复特定的可插拔。 数据库服务器生成加载有与第一个时间点相对应的根数据库的备份版本的克隆数据库。 数据库服务器应用重做日志将特定的可插拔数据库和克隆数据库恢复到晚于第一个时间点的第二个时间点。 数据库服务器根据克隆数据库识别特定可插拔数据库上的一个或多个活动事务。 数据库服务器回滚一个或多个活动事务。

    Efficient determination of committed changes
    30.
    发明授权
    Efficient determination of committed changes 有权

    公开(公告)号：US10303788B2

    公开(公告)日：2019-05-28

    申请号：US15253630

    申请日：2016-08-31

    Applicant: Oracle International Corporation

    Inventor： Kartik Kulkarni ,  Juan R. Loaiza ,  Vivekanandhan Raja ,  Kothanda Umamageswaran ,  Sanket Hase ,  Vasudha Krishnaswamy ,  Tirthankar Lahiri

    IPC: G06F17/30

    Abstract: A minimum value (MV) is computed for start timestamps that each correspond to an uncommitted transaction. In an embodiment, the MV is computed for a pluggable database that is open on at least first and second instances of a database. The MV is computed for the first instance as of a first current timestamp (CT). The MV and the first CT are communicated to a second instance that has a second CT. If the first and second CTs are equal, the second instance store the MV. If the first CT is bigger, the second CT also becomes equal to the first CT. If the first CT is smaller, the MV is discarded, and the first CT becomes equal to the second CT. In an embodiment, if the MV remains unchanged for a predetermined time period, a start timestamp corresponding to the MV is advanced to a current or future timestamp.

Patent Agency Ranking