TIME-BASED CHECKPOINT TARGET FOR DATABASE MEDIA RECOVERY
    41.
    发明申请
    TIME-BASED CHECKPOINT TARGET FOR DATABASE MEDIA RECOVERY 审中-公开
    基于时间的检查点目标数据库媒体恢复

    公开(公告)号:US20150317212A1

    公开(公告)日:2015-11-05

    申请号:US14270117

    申请日:2014-05-05

    Abstract: A method, apparatus, and system for a time-based checkpoint target is provided for standby databases. Change records received from a primary database are applied for a standby database, creating dirty buffer queues. As the change records are applied, a mapping is maintained, which maps timestamps to logical times of change records that were most recently applied at the timestamp for the standby database. On a periodic dirty buffer queue processing interval, the mapping is used to determine a target logical time that is mapped to a target timestamp that is prior to a present timestamp by at least a checkpoint delay. The dirty buffer queues are then processed up to the target logical time, creating an incremental checkpoint. On a periodic header update interval, file headers reflecting a consistent logical time for the checkpoint are also updated. The intervals and the checkpoint delay are adjustable by user or application.

    Abstract translation: 为备用数据库提供了基于时间的检查点目标的方法,装置和系统。 将从主数据库接收的更改记录应用于备用数据库,从而创建脏缓冲区队列。 随着应用更改记录,维护映射,将时间戳映射到最近在备用数据库的时间戳处应用的更改记录的逻辑时间。 在周期性的脏缓冲器队列处理间隔上,该映射用于确定映射到当前时间戳之前至少一个检查点延迟的目标时间戳的目标逻辑时间。 然后将脏缓冲区队列处理到目标逻辑时间,创建一个增量检查点。 在周期性头文件更新间隔中,还会更新反映检查点一致逻辑时间的文件头。 间隔和检查点延迟可由用户或应用程序调整。

    TECHNIQUES TO TAKE CLEAN DATABASE FILE SNAPSHOT IN AN ONLINE DATABASE
    42.
    发明申请
    TECHNIQUES TO TAKE CLEAN DATABASE FILE SNAPSHOT IN AN ONLINE DATABASE 有权
    在线数据库中使用清洁数据库文件快照的技术

    公开(公告)号:US20150286649A1

    公开(公告)日:2015-10-08

    申请号:US14243792

    申请日:2014-04-02

    CPC classification number: G06F17/30088 G06F17/30377

    Abstract: Techniques are described herein for making a clean file snapshot of a target file. The techniques may be applied to a single target file, to a set of target files, or to an entire database The techniques involve transitioning the target file through a series of states. During each state, particular actions are performed and/or prevented. In the final state of each approach, a clean file snapshot of the target file exists. Transitioning through the states, only one of which does not allow new changes to be made to the target file, allows the database to remain online and available to a greater extent than is possible with an approach that prevents database changes for the duration of the clean file snapshot creation operation.

    Abstract translation: 这里描述了用于制作目标文件的干净文件快照的技术。 这些技术可以应用于单个目标文件,一组目标文件或整个数据库。这些技术涉及通过一系列状态转换目标文件。 在每个状态期间,执行和/或防止特定动作。 在每种方法的最终状态下,存在目标文件的干净的文件快照。 通过状态转换,只有其中一个不允许对目标文件进行新的更改,允许数据库在更大程度上保持在线,并且可用于在清理期间阻止数据库更改的方法。 文件快照创建操作。

    Instantaneous Unplug of Pluggable Database From One Container Database and Plug Into Another Container Database
    43.
    发明申请
    Instantaneous Unplug of Pluggable Database From One Container Database and Plug Into Another Container Database 有权
    从一个容器数据库中即时拔下可插拔数据库,并插入另一个容器数据库

    公开(公告)号:US20150254240A1

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

    申请号:US14202091

    申请日:2014-03-10

    CPC classification number: G06F17/303 G06F17/30371 G06F17/30575

    Abstract: A pluggable database is transported between a source DBMS and a destination DBMS, in a way that minimizes downtime of the pluggable database. While a copy of the pluggable database is being made at the destination DBMS, transactions continue to execute against the pluggable database at the source DBMS and change the pluggable database. Eventually, the transactions terminate or cease executing. Redo records generated for the transactions are applied to the copy of the pluggable database at the source DBMS. Undo records generated for at least some of the transactions may be stored in a separate undo log and transported to the destination DBMS. The transported pluggable database is synchronized at a destination DBMS in a “pluggable-ready state”, where it may be plugged into the destination container DBMS.

    Abstract translation: 可插拔数据库在源DBMS和目标DBMS之间传输,从而最大限度地减少可插拔数据库的停机时间。 虽然目标DBMS正在进行可插拔数据库的副本,但是事务将继续针对源DBMS上的可插拔数据库执行,并更改可插拔数据库。 最终,交易终止或停止执行。 为事务生成的重做记录应用于源DBMS的可插拔数据库的副本。 至少为某些事务生成的撤销记录可以存储在单独的撤销日志中,并传送到目标DBMS。 传输的可插拔数据库在目标DBMS上以“可插拔就绪状态”进行同步,可以插入到目标容器DBMS中。

    MULTI-INSTANCE REDO APPLY
    44.
    发明申请
    MULTI-INSTANCE REDO APPLY 有权
    多媒体重播

    公开(公告)号:US20150120659A1

    公开(公告)日:2015-04-30

    申请号: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, remerged 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.

    Abstract translation: 为备用数据库提供了一种用于多实例重做应用的方法,装置和系统。 多实例主数据库生成多个重做记录,这些记录由运行多实例备用数据库的物理备用程序接收和应用。 每个备用实例运行一组使用非阻塞单任务线程进行高并行化的进程。 在多实例重做的每个备用实例上,多个重做记录以逻辑时间顺序被合并到来自一个或多个重做链的流中,根据使用智能工作负载分布函数确定的应用从属进程分发到备用实例 在从远程实例接收到更新后,并通过应用从属进程以逻辑时间顺序应用。 重做应用进度在本地和全局的每个实例被跟踪,允许一致的查询逻辑时间被维护和发布,以与重做应用程序同时服务于数据库读取查询请求。

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

    公开(公告)号:US12164801B2

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

    申请号:US17880438

    申请日: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

    公开(公告)号:US20240045857A1

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

    申请号:US17880433

    申请日:2022-08-03

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

    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