Multi-instance redo apply
    61.
    发明授权

    公开(公告)号:US09619541B2

    公开(公告)日:2017-04-11

    申请号:US14067129

    申请日:2013-10-30

    Abstract: A method, apparatus, and system for multi-instance redo apply is provided for standby databases. A multi-instance primary database generates a plurality of redo records, which are received and applied by a physical standby running a multi-instance standby database. Each standby instance runs a set of processes that utilize non-blocking, single-task threads for high parallelism. At each standby instance for the multi-instance redo, the plurality of redo records are merged into a stream from one or more redo strands in logical time order, distributed to standby instances according to determined apply slave processes using an intelligent workload distribution function, reemerged after receiving updates from remote instances, and applied in logical time order by the apply slave processes. Redo apply progress is tracked at each instance locally and also globally, allowing a consistent query logical time to be maintained and published to service database read query requests concurrently with the redo apply.

    Data transfers between cluster instances with delayed log file flush
    62.
    发明授权
    Data transfers between cluster instances with delayed log file flush 有权
    在具有延迟日志文件刷新的群集实例之间进行数据传输

    公开(公告)号:US09563521B2

    公开(公告)日:2017-02-07

    申请号:US14337077

    申请日:2014-07-21

    Abstract: Techniques for processing changes in a cluster database system are provided. A first instance in the cluster transfers a data block to a second instance in the cluster before a redo record that stores one or more changes that the first instance made to the data block is durably stored. The first instance also transfers, to the second instance, a block change timestamp that indicates when a redo record for the one or more changes was generated by the first instance. The first instance also separately sends, to the second instance, a last store timestamp that indicates when the last redo record that was durably stored was generated by the first instance. The block change timestamp and the last store timestamp are used by the second instance when creating redo records for changes (made by the second instance) that depend on the redo record generated by the first instance.

    Abstract translation: 提供了一种用于处理群集数据库系统中的更改的技术。 集群中的第一个实例将数据块传输到集群中的第二个实例,然后将存储一个或多个更改的重做记录保存在数据块中的第一个实例可持续存储。 第一个实例还将一个块更改时间戳传送到第二个实例,该时间戳指示一个或多个更改的重做记录何时由第一个实例生成。 第一个实例还分别向第二个实例发送一个最后一个存储时间戳,它指示何时被第一个实例生成的持久存储的最后一个重做记录。 当创建依赖于第一个实例生成的重做记录的更改(由第二个实例创建)的重做记录时,块更改时间戳和最后一个存储时间戳由第二个实例使用。

    Reduced disk space standby
    65.
    发明授权
    Reduced disk space standby 有权
    减少磁盘空间待机

    公开(公告)号:US09146934B2

    公开(公告)日:2015-09-29

    申请号:US14072739

    申请日:2013-11-05

    Abstract: A method and system for replicating database data is provided. One or more standby database replicas can be used for servicing read-only queries, and the amount of storage required is scalable in the size of the primary database storage. One technique is described for combining physical database replication to multiple physical databases residing within a common storage system that performs de-duplication. Having multiple physical databases allows for many read-only queries to be processed, and the de-duplicating storage system provides scalability in the size of the primary database storage. Another technique uses one or more diskless standby database systems that share a read-only copy of physical standby database files. Notification messages provide consistency between each diskless system's in-memory cache and the state of the shared database files. Use of a transaction sequence number ensures that each database system only accesses versions of data blocks that are consistent with a transaction checkpoint.

    Abstract translation: 提供了一种用于复制数据库数据的方法和系统。 一个或多个备用数据库副本可用于维护只读查询,并且所需的存储量可在主数据库存储的大小上扩展。 描述了一种将物理数据库复制与驻留在执行重复数据删除的公共存储系统中的多个物理数据库进行组合的技术。 拥有多个物理数据库可以处理许多只读查询,并且重复存储系统提供主数据库存储大小的可扩展性。 另一种技术使用一个或多个共享物理备用数据库文件的只读副本的无盘备用数据库系统。 通知消息提供每个无盘系统的内存缓存与共享数据库文件的状态之间的一致性。 使用事务序列号确保每个数据库系统只能访问与事务检查点一致的数据块版本。

    Increasing OLTP throughput by improving the performance of logging using persistent memory storage

    公开(公告)号:US12159032B2

    公开(公告)日:2024-12-03

    申请号:US17880446

    申请日:2022-08-03

    Abstract: In an embodiment, before modifying a persistent ORL (ORL), a database management system (DBMS) persists redo for a transaction and acknowledges that the transaction is committed. Later, the redo is appended onto the ORL. The DBMS stores first redo for a first transaction into a first PRB and second redo for a second transaction into a second PRB. Later, both redo are appended onto an ORL. The DBMS stores redo of first transactions in volatile SRBs (SLBs) respectively of database sessions. That redo is stored in a volatile shared buffer that is shared by the database sessions. Redo of second transactions is stored in the volatile shared buffer, but not in the SLBs. During re-silvering and recovery, the DBMS retrieves redo from fast persistent storage and then appends the redo onto an ORL in slow persistent storage. After re-silvering, during recovery, the redo from the ORL is applied to a persistent database block.

    Increasing OLTP throughput by improving the performance of logging using persistent memory storage

    公开(公告)号:US12086132B2

    公开(公告)日:2024-09-10

    申请号:US17880433

    申请日:2022-08-03

    CPC classification number: G06F16/2379 G06F9/466 G06F16/2358

    Abstract: In an embodiment, before modifying a persistent ORL (ORL), a database management system (DBMS) persists redo for a transaction and acknowledges that the transaction is committed. Later, the redo is appended onto the ORL. The DBMS stores first redo for a first transaction into a first PRB and second redo for a second transaction into a second PRB. Later, both redo are appended onto an ORL. The DBMS stores redo of first transactions in volatile SRBs (SLBs) respectively of database sessions. That redo is stored in a volatile shared buffer that is shared by the database sessions. Redo of second transactions is stored in the volatile shared buffer, but not in the SLBs. During re-silvering and recovery, the DBMS retrieves redo from fast persistent storage and then appends the redo onto an ORL in slow persistent storage. After re-silvering, during recovery, the redo from the ORL is applied to a persistent database block.

    INCREASING OLTP THROUGHPUT BY IMPROVING THE PERFORMANCE OF LOGGING USING PERSISTENT MEMORY STORAGE

    公开(公告)号:US20240045613A1

    公开(公告)日:2024-02-08

    申请号:US17880438

    申请日:2022-08-03

    CPC classification number: G06F3/0656 G06F3/0604 G06F3/0679

    Abstract: In an embodiment, before modifying a persistent ORL (ORL), a database management system (DBMS) persists redo for a transaction and acknowledges that the transaction is committed. Later, the redo is appended onto the ORL. The DBMS stores first redo for a first transaction into a first PRB and second redo for a second transaction into a second PRB. Later, both redo are appended onto an ORL. The DBMS stores redo of first transactions in volatile SRBs (SLBs) respectively of database sessions. That redo is stored in a volatile shared buffer that is shared by the database sessions. Redo of second transactions is stored in the volatile shared buffer, but not in the SLBs. During re-silvering and recovery, the DBMS retrieves redo from fast persistent storage and then appends the redo onto an ORL in slow persistent storage. After re-silvering, during recovery, the redo from the ORL is applied to a persistent database block.

Patent Agency Ranking