Consistent database recovery across constituent segments
    1.
    发明授权
    Consistent database recovery across constituent segments 有权
    跨组成部分的数据库恢复一致

    公开(公告)号:US08671085B2

    公开(公告)日:2014-03-11

    申请号:US13315363

    申请日:2011-12-09

    IPC分类号: G06F17/00

    CPC分类号: G06F11/1471 G06F17/30289

    摘要: A distributed database transaction coordination manager's outcome store may be unavailable to resolve in-doubt transactions locally, e.g., after an unclean detach, during an outcomes store restore, or during a logical database restore. To facilitate transactional consistency, AGEs and values based on them are used. Some code avoids reformatting any closed physical portion for reuse based on the segment's most recently received minimum of persisted AGEs. Some code commits any in-doubt transactions that appear on an aggregate list and aborts any not on the aggregate list. Some code writes each segment's transaction commit records to persistent storage until the segment's persisted-AGE is not less than a common-restore-AGE, and some code resolves any in-doubt transactions based on a harvested outcomes list. Outcomes may reside in a log or a persisted transactions table. A restore checkpoint may include harvested outcomes. Segments may reside on cloud nodes and/or in a shared nothing database system.

    摘要翻译: 分布式数据库事务协调管理器的结果存储可能不可用于在结果存储恢复期间或在逻辑数据库恢复期间在本地例如在不清洁的分离之后解决无疑的事务。 为了促进事务一致性,使用AGEs和基于它们的值。 一些代码避免重新格式化任何封闭的物理部分,以便根据片段最近接收的持久AGE的最小值进行重新使用。 一些代码提交出现在聚合列表上的任何无疑的事务,并且中止不在聚合列表上的任何事务。 一些代码将每个段的事务提交记录写入永久存储,直到段的持久AGE不小于common-restore-AGE,并且一些代码基于收获的结果列表来解决任何无疑的事务。 成果可能驻留在日志或持久化事务表中。 恢复检查点可能包括收获结果。 分段可能驻留在云节点和/或共享无数据库系统中。

    Consistent Database Recovery Across Constituent Segments
    2.
    发明申请
    Consistent Database Recovery Across Constituent Segments 有权
    跨组成部分的数据库恢复一致

    公开(公告)号:US20130151494A1

    公开(公告)日:2013-06-13

    申请号:US13315363

    申请日:2011-12-09

    IPC分类号: G06F17/30

    CPC分类号: G06F11/1471 G06F17/30289

    摘要: A distributed database transaction coordination manager's outcome store may be unavailable to resolve in-doubt transactions locally, e.g., after an unclean detach, during an outcomes store restore, or during a logical database restore. To facilitate transactional consistency, AGEs and values based on them are used. Some code avoids reformatting any closed physical portion for reuse based on the segment's most recently received minimum of persisted AGEs. Some code commits any in-doubt transactions that appear on an aggregate list and aborts any not on the aggregate list. Some code writes each segment's transaction commit records to persistent storage until the segment's persisted-AGE is not less than a common-restore-AGE, and some code resolves any in-doubt transactions based on a harvested outcomes list. Outcomes may reside in a log or a persisted transactions table. A restore checkpoint may include harvested outcomes. Segments may reside on cloud nodes and/or in a shared nothing database system.

    摘要翻译: 分布式数据库事务协调管理器的结果存储可能不可用于在结果存储恢复期间或在逻辑数据库恢复期间在本地例如在不清洁的分离之后解决无疑的事务。 为了促进事务一致性,使用AGEs和基于它们的值。 一些代码避免重新格式化任何封闭的物理部分,以便根据片段最近接收的持久AGE的最小值进行重新使用。 一些代码提交出现在聚合列表上的任何无疑的事务,并且中止不在聚合列表上的任何事务。 一些代码将每个段的事务提交记录写入永久存储,直到段的持久AGE不小于common-restore-AGE,并且一些代码基于收获的结果列表来解决任何无疑的事务。 成果可能驻留在日志或持久化事务表中。 恢复检查点可能包括收获结果。 分段可能驻留在云节点和/或共享无数据库系统中。