会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Consistent database recovery across constituent segments
    • 跨组成部分的数据库恢复一致
    • US08671085B2
    • 2014-03-11
    • US13315363
    • 2011-12-09
    • Robin Dhananjay DhamankarKapil GuptaMichael PurtellKevin G. Farlee
    • Robin Dhananjay DhamankarKapil GuptaMichael PurtellKevin G. Farlee
    • G06F17/00
    • G06F11/1471G06F17/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,并且一些代码基于收获的结果列表来解决任何无疑的事务。 成果可能驻留在日志或持久化事务表中。 恢复检查点可能包括收获结果。 分段可能驻留在云节点和/或共享无数据库系统中。
    • 6. 发明授权
    • Commit tree optimization based on recovery topology information
    • 基于恢复拓扑信息提交树优化
    • US07533080B2
    • 2009-05-12
    • US11401029
    • 2006-04-10
    • Dana D. GroffJames E. JohnsonJohn D. DotyJonathan M. CargilleKapil GuptaMichael R. Clark
    • Dana D. GroffJames E. JohnsonJohn D. DotyJonathan M. CargilleKapil GuptaMichael R. Clark
    • G06F17/30
    • G06F9/466Y10S707/99932
    • Minimizing transaction managers. A method that may be practiced in a commit tree topology including a plurality of transaction managers to manage transactions. The transactions include a set of operations that are all performed if a transaction is completed or all aborted if a transaction is not completed. The transaction managers store transaction result information to allow recovery of a transaction in case of system failure. The method includes acts for minimizing storage overhead by minimizing the number of transaction managers used to coordinate transactions. The method includes identifying a set of transaction managers. A first transaction manager is selected from among the set of transaction managers. A second transaction manager is identified from among the set of transaction managers that is always available when the first transaction manager is available. Messages are redirected from a subordinate associated with the first transaction manager to the second transaction manager.
    • 最小化交易经理。 可以在包括多个事务管理器的提交树拓扑中实践的方法来管理事务。 事务包括一组操作,如果事务完成或者如果事务未完成则全部中止操作。 事务管理器存储事务结果信息,以便在系统故障的情况下恢复事务。 该方法包括通过最小化用于协调事务的事务管理器的数量来最小化存储开销的动作。 该方法包括识别一组事务管理器。 从一组事务管理器中选择第一个事务管理器。 从第一个事务管理器可用时始终可用的一组事务管理器中识别出第二个事务管理器。 消息从与第一个事务管理器关联的下属重定向到第二个事务管理器。
    • 10. 发明申请
    • Consistent Database Recovery Across Constituent Segments
    • 跨组成部分的数据库恢复一致
    • US20130151494A1
    • 2013-06-13
    • US13315363
    • 2011-12-09
    • Robin Dhananjay DhamankarKapil GuptaMichael PurtellKevin G. Farlee
    • Robin Dhananjay DhamankarKapil GuptaMichael PurtellKevin G. Farlee
    • G06F17/30
    • G06F11/1471G06F17/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,并且一些代码基于收获的结果列表来解决任何无疑的事务。 成果可能驻留在日志或持久化事务表中。 恢复检查点可能包括收获结果。 分段可能驻留在云节点和/或共享无数据库系统中。