Near-zero downtime relocation of a pluggable database across container databases

    公开(公告)号:US10860605B2

    公开(公告)日:2020-12-08

    申请号:US15215446

    申请日:2016-07-20

    Abstract: Embodiments minimize downtime involved in moving a PDB between CDBs by allowing read-write access to the PDB through most of the moving operation, and by transparently forwarding connection requests, for the PDB, from the source CDB to the destination CDB. The files of a source PDB are copied from a source CDB to a destination CDB, during which the source PDB may be in read-write mode. The source PDB is then closed to write operations so that changes to the source PDB cease. Another round of recovery is performed on the PDB clone, which applies all changes that have been performed on the source PDB during the copy operation and the PDB clone is opened for read and write operations. Forwarding information is registered with the source location, which information is used to automatically forward connection requests, received at the source location for the moved PDB, to the destination location.

    AUTOMATIC RECONFIGURATION OF RELOCATED PLUGGABLE DATABASES

    公开(公告)号:US20170116235A1

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

    申请号:US15266030

    申请日:2016-09-15

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

    Abstract: A database server instance automatically detects configuration issues when a pluggable database (PDB) is plugged into a new destination container database (CDB). The database server instance identifies one or more update templates, within the destination CDB, that, when run over the relocated PDB, will update the configuration of the PDB to conform to the configuration of the destination CDB. Instead of requiring an administrator to initiate update scripts from a DBMS kernel to reconfigure a PDB, the DBMS creates the update templates by recording commands run within PDBs in connection with system updates. These recorded update templates may then be run over relocated PDBs, to configure the PDBs according to the configuration of the destination CDB. Further, the update templates may be pre-recorded update templates, which record commands to perform configuration updates, to PDBs, that have never before been performed within the CDB.

    Instantaneous Unplug of Pluggable Database From One Container Database and Plug Into Another Container Database
    15.
    发明申请
    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中。

    NEAR-ZERO DOWNTIME RELOCATION OF A PLUGGABLE DATABASE ACROSS CONTAINER DATABASES

    公开(公告)号:US20210056123A1

    公开(公告)日:2021-02-25

    申请号:US17090732

    申请日:2020-11-05

    Abstract: Embodiments minimize downtime involved in moving a PDB between CDBs by allowing read-write access to the PDB through most of the moving operation, and by transparently forwarding connection requests, for the PDB, from the source CDB to the destination CDB. The files of a source PDB are copied from a source CDB to a destination CDB, during which the source PDB may be in read-write mode. The source PDB is then closed to write operations so that changes to the source PDB cease. Another round of recovery is performed on the PDB clone, which applies all changes that have been performed on the source PDB during the copy operation and the PDB clone is opened for read and write operations. Forwarding information is registered with the source location, which information is used to automatically forward connection requests, received at the source location for the moved PDB, to the destination location.

Patent Agency Ranking