会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Transitioning ownership of data items between ownership groups
    • 在所有权组之间转换数据项目的所有权
    • US06341340B1
    • 2002-01-22
    • US09222593
    • 1998-12-28
    • Alex TsukermanGary C. NgaiGianfranco PutzoluJ. William Lee
    • Alex TsukermanGary C. NgaiGianfranco PutzoluJ. William Lee
    • G06F1200
    • G06F17/30575
    • A database or some portion thereof is partitioned into ownership groups. Each ownership group is assigned one or more database servers as owners of the ownership group. The database servers that are assigned as owners of an ownership group are treated as the owners of all data items that belong to the ownership group. That is, they are allowed to directly access the data items within the ownership group, while other database servers are not allowed to directly access those data items. A mechanism is provided for transitioning ownership of a data item. Ownership is transferred by disabling access to the data item, waiting for all transactions that have made changes to the data item to either commit or abort, changing data that indicates ownership of the data item from a first owner to a second owner, and enabling access to the data item.
    • 数据库或其一部分被划分为所有权组。 每个所有权组被分配一个或多个数据库服务器作为所有权组的所有者。 分配为所有者组的所有者的数据库服务器将被视为属于所有权组的所有数据项的所有者。 也就是说,它们被允许直接访问所有权组内的数据项,而其他数据库服务器不允许直接访问这些数据项。 提供了一种转换数据项所有权的机制。 通过禁用对数据项的访问,等待对数据项进行更改的所有事务进行提交或中止,将数据项的所有权从第一个所有者更改为第二个所有者,并启用访问权限 到数据项。
    • 9. 发明授权
    • Lost write detection and repair
    • 丢失写检测和修复
    • US07627614B2
    • 2009-12-01
    • US11072111
    • 2005-03-03
    • Wei Ming HuMark DilmanJ. William LeeJuan R. LoaizaVinay Srihari
    • Wei Ming HuMark DilmanJ. William LeeJuan R. LoaizaVinay Srihari
    • G06F17/30
    • G06F11/1471G06F11/2094G06F2201/80G06F2211/1007Y10S707/99954
    • Techniques are provided for detecting lost writes so that data corruption can be avoided. According to one technique, lost writes are detected by comparing version numbers that are indicated in redo log entries with version numbers that are indicated in corresponding blocks in a standby database. According to one technique, which may be used in conjunction with the above technique, lost writes are detected by logging read operations that occur relative to a primary database, and comparing version numbers that are indicated in read log entries with version numbers that are indicated in corresponding blocks in a standby database. According to one technique, lost writes are detected by comparing, in response to read operations, (a) version numbers that are stored in a persistent in-memory cache with (b) version numbers that are indicated in corresponding blocks that are read from a primary database.
    • 提供了用于检测丢失写入的技术,从而可以避免数据损坏。 根据一种技术,通过将重做日志条目中指示的版本号与在备用数据库中的相应块中指示的版本号进行比较来检测丢失的写入。 根据可以与上述技术结合使用的一种技术,通过记录相对于主数据库发生的读取操作来检测丢失的写入,并且将读取日志条目中指示的版本号与在 备用数据库中的相应块。 根据一种技术,通过比较读取操作来检测丢失的写入,(a)存储在持久性内存高速缓存中的版本号,(b)版本号,其在从 主数据库。
    • 10. 发明授权
    • Multi-node fault-tolerant timestamp generation
    • 多节点容错时间戳生成
    • US6078930A
    • 2000-06-20
    • US961798
    • 1997-10-31
    • J. William LeeWilliam H. Bridge, Jr.
    • J. William LeeWilliam H. Bridge, Jr.
    • G06F11/14G06F17/00G06F11/00
    • G06F11/1415G06F2201/835Y10S707/99952Y10S707/99953
    • Techniques for determining a safe recovery time value after a failure of a first node in a computer system are described. According to the techniques, every node in a multi-node parallel database system maintains a logical clock for generating timestamps. The logical clocks are synchronized by attaching a current timestamp to every message that is sent by a node. When a node receives an incoming timestamp that is greater than the value indicated by the associated logical clock, it sets the associated logical clock forward to at least the value of the timestamp. When a node fails, a recovery node calculates a "safe" logical clock value to use in recovering the crashed node. In calculating the "safe" logical clock value, the recovery node searches specific areas of the database to locate and recover a most recent timestamp value associated with the crashed node. The recovery node then compares its current logical clock time value with the most recent crash node timestamp value to determine which timestamp is most recent. If the most recent crash node timestamp value is more recent than the recovery node's current logical clock time value, the recovery node's logical clock is updated to be at least as recent as the most recent crash node timestamp value. The recovery node then recovers the crashed node as its logical clock is guaranteed to be at least as recent as any timestamp value that was previously written to the database by the crashed node prior to failure.
    • 描述用于在计算机系统中的第一节点故障之后确定安全恢复时间值的技术。 根据这些技术,多节点并行数据库系统中的每个节点维护用于生成时间戳的逻辑时钟。 通过将当前时间戳附加到由节点发送的每个消息来同步逻辑时钟。 当节点接收到大于由相关逻辑时钟指示的值的输入时间戳时,它将关联的逻辑时钟向前设置为至少时间戳的值。 当节点出现故障时,恢复节点将计算一个“安全”的逻辑时钟值,用于恢复崩溃的节点。 在计算“安全”逻辑时钟值时,恢复节点搜索数据库的特定区域以查找和恢复与崩溃的节点相关联的最新时间戳值。 然后,恢复节点将其当前逻辑时钟时间值与最近的崩溃节点时间戳值进行比较,以确定哪个时间戳是最近的。 如果最近的崩溃节点时间戳值比恢复节点当前的逻辑时钟时间值更新,则恢复节点的逻辑时钟被更新为至少与最近的崩溃节点时间戳值一样近。 然后,恢复节点恢复崩溃的节点,因为其逻辑时钟保证至少与故障之前由崩溃的节点写入数据库的任何时间戳值一样最近。