会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 21. 发明申请
    • Persistent client-server database sessions
    • 持久的客户端 - 服务器数据库会话
    • US20050021514A1
    • 2005-01-27
    • US10920629
    • 2004-08-18
    • Roger BargaDavid Lomet
    • Roger BargaDavid Lomet
    • G06F7/00G06F17/00G06F17/30
    • G06F11/1438G06F11/1471Y10S707/99942Y10S707/99943
    • A client-server database system enables persistent client-server database sessions, without modification to a client-side application, a database system, or native client-side database drivers. The client is implemented with a driver manager to facilitate communication between the native database drivers and the database application. The driver manager wraps the native drivers, intercepting queries passed from the database application to the database drivers. The driver manager modifies the queries to form modified queries that direct the database server to render result sets produced from processing the queries persistent at the database server. Upon recovery following a server crash, the driver manager directs the drivers to reestablish a connection with the database server. The driver manager then finds the persistent result set table and, using logged data, returns to the same operation on the result set table just prior to the crash. The driver manager then reassociates the application context to the new database session without the database application being aware that a failure occurred. The recovery is thus transparent to the client-side application.
    • 客户端 - 服务器数据库系统启用持久的客户端 - 服务器数据库会话,而不会修改客户端应用程序,数据库系统或本机客户端数据库驱动程序。 客户端由驱动程序管理器实现,以促进本机数据库驱动程序与数据库应用程序之间的通信。 驱动程序管理器将本机驱动程序打包,并将从数据库应用程序传递的查询截取到数据库驱动程序。 驱动程序管理器修改查询以形成修改的查询,指导数据库服务器呈现从处理数据库服务器上持久存储的查询生成的结果集。 在服务器崩溃后恢复,驱动程序管理器指示驱动程序重新建立与数据库服务器的连接。 然后,驱动程序管理器会找到持久性结果集表,并使用记录的数据在崩溃之前在结果集表上返回相同的操作。 然后,驱动程序管理器将应用程序上下文重新关联到新数据库会话,而数据库应用程序不知道发生故障。 恢复对客户端应用来说是透明的。
    • 22. 发明授权
    • Logical recovery with unbundled transaction services
    • 逻辑恢复与非捆绑交易服务
    • US08930321B2
    • 2015-01-06
    • US12827941
    • 2010-06-30
    • David LometKostas Tzoumas
    • David LometKostas Tzoumas
    • G06F7/00G06F11/14
    • G06F11/1471
    • This patent application relates to enhanced logical recovery techniques for redo recovery operations of a system with an unbundled storage engine. These techniques can be implemented by utilizing an enhanced logical recovery approach in which a dirty page table (DPT) is constructed based on information logged during normal execution. The unbundled storage engine can include a transaction component (TC) that is architecturally independent of a data component (DC). These techniques can enhance redo recovery operations by mitigating the resources needed to determine whether previously executed operations sent from the TC to the DC are to be repeated in response to a recovery-initiating event. This can include using the DPT to avoid fetching every data page corresponding to every previously executed operation received by the DC during recovery and/or pre-fetching data pages and/or index pages that correspond to PIDs in the DPT.
    • 该专利申请涉及用于具有非捆绑存储引擎的系统的重做恢复操作的增强的逻辑恢复技术。 这些技术可以通过利用增强的逻辑恢复方法来实现,其中基于在正常执行期间记录的信息来构造脏页表(DPT)。 非捆绑存储引擎可以包括在架构上独立于数据组件(DC)的事务组件(TC)。 这些技术可以通过减轻确定从TC发送到DC的先前执行的操作是否要响应于恢复发起事件被重复而需要的资源来增强重做恢复操作。 这可以包括使用DPT来避免在恢复期间和/或预取与DPT中的PID相对应的数据页和/或索引页期间获取对应于由DC接收的每个先前执行的每个操作的每个数据页。
    • 23. 发明授权
    • Unilateral web services interaction contract
    • 单边Web服务交互合同
    • US07668961B2
    • 2010-02-23
    • US10947707
    • 2004-09-23
    • David Lomet
    • David Lomet
    • G06F15/16G06F11/00
    • G06F11/1474G06F11/1479H04L69/40
    • The present invention leverages a unilaterally-based interaction contract that enables applications to have a persistent state and ensures an exactly-once execution despite failures between and by communicating entities, permitting disparate software applications to be robustly supported in an environment where little is known about the implementation of the interaction contract. In one instance of the present invention, a web services interaction contract provides a communicating application with duplicate commit request elimination, persistent state transitions, and/or unique persistent reply requests. The present invention permits this interaction contract to be supported by, for example, a persistent application, a workflow, a transaction queue, a database, and a file system to facilitate in providing idempotent executions for requests from a communicating application.
    • 本发明利用单方面的交互合同,使得应用能够具有持久状态,并确保即使在通信实体之间发生故障并且通过通信实体发生故障,从而允许不同的软件应用被强有力地支持在一个关于 互动合同的实施。 在本发明的一个实例中,Web服务交互协议为通信应用提供重复的提交请求消除,持久状态转换和/或唯一的持久应答请求。 本发明允许例如持续应用程序,工作流程,事务队列,数据库和文件系统来支持该交互合同,以便于为来自通信应用的请求提供幂等执行。
    • 24. 发明申请
    • Recovery of logless components
    • 恢复无序组件
    • US20070192373A1
    • 2007-08-16
    • US11354374
    • 2006-02-15
    • David Lomet
    • David Lomet
    • G06F17/30
    • G06F11/1471G06F11/1469
    • Recovery processing of logless components is disclosed. Logless components in middle-tier systems can be checkpointed to provide faster recovery. In particular, a client system, executing a persistent component and itself logging, initiates a snapshot method that returns to the client the values of all variables and other state of the logless component during normal execution. The client writes this data to the client log along with information about the initiation call. To recover the logless component, the client invokes a restore method which takes as an argument values returned from the snapshot method and included in the checkpointing portion of the client log relating to the logless component. This information is sufficient for recreating the logless component which is logically identical to the failed logless component and for setting its state to the checkpoint state. This can occur transparently and shorten the recovery time in providing exactly-once execution.
    • 公开了无级元件的恢复处理。 中间层系统中的无逻辑组件可以检查点以提供更快的恢复。 特别地,执行持久组件和自身日志记录的客户端系统启动快照方法,该方法在正常执行期间向客户端返回所有变量的值和无逻辑组件的其他状态。 客户端将该数据连同关于启动呼叫的信息一起写入客户端日志。 要恢复logless组件,客户端将调用恢复方法,该方法将从快照方法返回的参数值作为参数值,并将其包含在与无逻辑组件相关的客户机日志的检查点部分中。 该信息足以重新创建逻辑上与失败的无逻辑组件相同的无逻辑组件,并将其状态设置为检查点状态。 这可以透明地发生,并缩短恢复时间,以提供一次执行。
    • 25. 发明申请
    • Concurrency control for B-trees with node deletion
    • 具有节点删除的B树的并发控制
    • US20050171960A1
    • 2005-08-04
    • US10768527
    • 2004-01-30
    • David Lomet
    • David Lomet
    • G06F17/00
    • G06F17/30327G06F17/30336G06F17/30348Y10S707/99942Y10S707/99943
    • A data structure, added to a modified form of the Blink-tree data structure, tracks delete states for nodes. The index delete state (DX) indicates whether it is safe to directly access an index node without re-traversing the B-tree. The DX state is maintained globally, outside of the tree structure. The data delete state (DD) indicates whether it is safe to post an index term for a new leaf node. A DD state is maintained in each level 1 node for its leaf nodes. Delete states indicate whether a specific node has not been deleted, or whether it may have been deleted. Delete states are used to remove the necessity for atomic node splits and chains of latches for deletes, while not requiring retraversal. This property of not requiring a retraversal is exploited to simplify the tree modification operations.
    • 添加到B 链接树数据结构的修改形式的数据结构跟踪节点的删除状态。 索引删除状态(D X)表示在不重新遍历B树的情况下直接访问索引节点是否安全。 在树结构之外,全局地维护D 状态。 数据删除状态(D D )表示是否可以安全地为新的叶节点发布索引项。 在其叶节点的每个1级节点中保持D D D N状态。 删除状态表示特定节点是否未被删除,或者是否可能被删除。 删除状态用于消除用于删除的原子节点拆分和锁存链的必要性,而不需要重新进行穿越。 利用这种不需要重穿的属性来简化树的修改操作。