公开(公告)号：US11176115B2

公开(公告)日：2021-11-16

申请号：US16428892

申请日：2019-05-31

Applicant: Oracle International Corporation

Inventor： Chi Kim Hoang ,  Chih-Ping Wang ,  Nagender Bandi ,  John Miller

IPC: G06F16/00 ,  G06F16/23 ,  G06F16/27 ,  G06F16/21

Abstract: Techniques are described for performing dependency locking to enable parallel execution of database server processes modifying the same object. In an embodiment, a DBMS receives a request to execute an operation on its managed database. The request may include an object identifier and a version identifier for a version of a database object, which is required for the successful execution of the operation on the database. The required version of the database object may not exist and may be generated only after the execution of another, second, operation on the database. The first database server process initiates execution of the earlier received operation on the database. The first database server process queries the first database for the version of the particular database object and determines that the version of the database object does not exist yet, in one embodiment. Based on such a determination, a dependency lock is generated for the version of the object, and the first database server process is suspended, preventing the completion of execution of the earlier received operation on the database. Another, second database server process executes another operation on the database and causes the generation of the version of the object on the database. The dependency lock is thereby released for the version of the object, and the first database server process completes the execution of the first operation on the first database.

公开(公告)号：US20130198249A1

公开(公告)日：2013-08-01

申请号：US13799572

申请日：2013-03-13

Applicant: Oracle International Corporation

Inventor： Chi-Kim Hoang ,  Tirthankar Lahiri ,  Marie-Anne Neimat ,  Chih-Ping Wang ,  John E. Miller ,  Dilys Thomas ,  Nagender Bandi ,  Susan Cheng

IPC: G06F17/30

CPC classification number: G06F17/30312 ,  G06F12/084

Abstract: A plurality of mid-tier databases form a single, consistent cache grid for data in one or more backend data sources, such as a database system. The mid-tier databases may be standard relational databases. Cache agents at each mid-tier database swap in data from the backend database as needed. Ownership locks maintain consistency in the cache grid. Cache agents prevent database operations that will modify cached data in a mid-tier database unless and until ownership of the cached data can be acquired for the mid-tier database. Cache groups define what backend data may be cached, as well as a general structure in which the backend data is to be cached. Metadata for cache groups is shared to ensure that data is cached in the same form throughout the entire grid. Ownership of cached data can then be tracked through a mapping of cached instances of data to particular mid-tier databases.

Abstract translation: 多个中间层数据库形成用于一个或多个后端数据源（例如数据库系统）中的数据的单一，一致的高速缓存网格。 中间层数据库可以是标准关系数据库。 每个中间层数据库的缓存代理根据需要从后端数据库交换数据。 所有权锁在高速缓存网格中保持一致性。 高速缓存代理阻止数据库操作，将修改中间层数据库中的缓存数据，除非可以为中间层数据库获取缓存数据的所有权。 缓存组定义可以缓存哪些后端数据，以及要缓存后端数据的一般结构。 共享缓存组的元数据，以确保数据在整个网格中以相同的格式缓存。 然后可以通过将缓存的数据实例映射到特定中间层数据库来跟踪缓存数据的所有权。

公开(公告)号：US09569475B2

公开(公告)日：2017-02-14

申请号：US13799572

申请日：2013-03-13

Applicant: Oracle International Corporation

Inventor： Chi-Kim Hoang ,  Tirthankar Lahiri ,  Marie-Anne Neimat ,  Chih-Ping Wang ,  John E. Miller ,  Dilys Thomas ,  Nagender Bandi ,  Susan Cheng

IPC: G06F17/30 ,  G06F12/08

CPC classification number: G06F17/30312 ,  G06F12/084

Abstract: A plurality of mid-tier databases form a single, consistent cache grid for data in one or more backend data sources, such as a database system. The mid-tier databases may be standard relational databases. Cache agents at each mid-tier database swap in data from the backend database as needed. Ownership locks maintain consistency in the cache grid. Cache agents prevent database operations that will modify cached data in a mid-tier database unless and until ownership of the cached data can be acquired for the mid-tier database. Cache groups define what backend data may be cached, as well as a general structure in which the backend data is to be cached. Metadata for cache groups is shared to ensure that data is cached in the same form throughout the entire grid. Ownership of cached data can then be tracked through a mapping of cached instances of data to particular mid-tier databases.

Abstract translation: 多个中间层数据库形成用于一个或多个后端数据源（例如数据库系统）中的数据的单一，一致的高速缓存网格。 中间层数据库可以是标准关系数据库。 每个中间层数据库的缓存代理根据需要从后端数据库交换数据。 所有权锁在高速缓存网格中保持一致性。 高速缓存代理阻止数据库操作，将修改中间层数据库中的缓存数据，除非可以为中间层数据库获取缓存数据的所有权。 缓存组定义可以缓存哪些后端数据，以及要缓存后端数据的一般结构。 共享缓存组的元数据，以确保数据在整个网格中以相同的格式缓存。 然后可以通过将缓存的数据实例映射到特定中间层数据库来跟踪缓存数据的所有权。

公开(公告)号：US20160335310A1

公开(公告)日：2016-11-17

申请号：US14709018

申请日：2015-05-11

Applicant: Oracle International Corporation

Inventor： Tirthankar Lahiri ,  Derek Taylor ,  Nagender Bandi ,  John Miller ,  Chi-Kim Hoang ,  Ryder Rishel ,  Varadarajan Aravamudhan ,  Chih-Ping Wang ,  Susan Cheung ,  Samuel Drake ,  Paul Tuck ,  David Aspinwall

IPC: G06F17/30

CPC classification number: G06F16/2379 ,  G06F16/27

Abstract: A database is stored as a plurality of database shards in a distributed database grid comprising a plurality of grid elements, each including a mid-tier database system. A first grid element receives, from an application executing in the same memory as a mid-tier database system of the first grid element, a first database transaction including at least one database operation on specific data stored in a first database shard that belongs to the first grid element. The first grid element performs and commits the first database transaction without participation of another grid element of the plurality of grid elements. The first grid element receives a second database transaction that requires access to another database shard that does not belong to the first grid element. Multiple grid elements of the plurality of grid elements perform the second database transaction and commit the second database transaction using a two-phase commit protocol.

Abstract translation: 数据库作为多个数据库分片存储在包括多个网格元素的分布式数据库网格中，每个网格元素包括中间层数据库系统。 第一网格元件从与第一网格元素的中间层数据库系统在同一存储器中执行的应用接收第一数据库事务，该第一数据库事务包括存储在第一数据库分片中的特定数据的至少一个数据库操作，该数据库操作属于 第一个网格元素 第一网格元素执行并提交第一数据库事务而不参与多个网格元素中的另一网格元素。 第一个网格元素接收需要访问不属于第一个网格元素的另一个数据库分片的第二个数据库事务。 多个网格元素的多个网格元素执行第二数据库事务并使用两阶段提交协议提交第二数据库事务。

公开(公告)号：US11829349B2

公开(公告)日：2023-11-28

申请号：US14709018

申请日：2015-05-11

Applicant: Oracle International Corporation

Inventor： Tirthankar Lahiri ,  Derek Taylor ,  Nagender Bandi ,  John Miller ,  Chi-Kim Hoang ,  Ryder Rishel ,  Varadarajan Aravamudhan ,  Chih-Ping Wang ,  Susan Cheung ,  Samuel Drake ,  Paul Tuck ,  David Aspinwall

IPC: G06F16/23 ,  G06F16/27

CPC classification number: G06F16/2379 ,  G06F16/27

Abstract: A database is stored as a plurality of database shards in a distributed database grid comprising a plurality of grid elements, each including a mid-tier database system. A first grid element receives, from an application executing in the same memory as a mid-tier database system of the first grid element, a first database transaction including at least one database operation on specific data stored in a first database shard that belongs to the first grid element. The first grid element performs and commits the first database transaction without participation of another grid element of the plurality of grid elements. The first grid element receives a second database transaction that requires access to another database shard that does not belong to the first grid element. Multiple grid elements of the plurality of grid elements perform the second database transaction and commit the second database transaction using a two-phase commit protocol.

公开(公告)号：US11334445B2

公开(公告)日：2022-05-17

申请号：US16232860

申请日：2018-12-26

Applicant: Oracle International Corporation

Inventor： Tirthankar Lahiri ,  Martin Reames ,  Kao Makino ,  Ananth Raghavan ,  Chih-Ping Wang ,  Mutsumi Kogawa ,  Jorge Luis Issa Garcia

IPC: G06F16/23 ,  G06F11/14

Abstract: In an in-memory database management system, non-volatile random access memories (NVRAMs) are used to store database data and control data. Because this data is stored in NVRAM, the data survives system failures. Recovery from a system failure may be accomplished more quickly by, at least in part, modifying the surviving data in NVRAM, rather than loading an entire checkpoint image and applying uncheckpointed transactions needed to synchronize the database. Because in this form of recovery the database state that serves as the starting point for applying change records is the database as stored in the NVRAM, this form of recovery is referred to herein as in-memory-based recovery. Recovery, where the database state that serves as the starting point for applying change records is a checkpoint image, is referred to herein as checkpointed-based recovery. In-memory-based recovery eliminates or reduces the need to perform certain operations that are performed for checkpointed-based recovery.

公开(公告)号：US09639562B2

公开(公告)日：2017-05-02

申请号：US13842843

申请日：2013-03-15

Applicant: Oracle International Corporation

Inventor： John Raitto ,  Tirthankar Lahiri ,  Marie-Anne Neimat ,  Chih-Ping Wang

IPC: G06F17/30

CPC classification number: G06F17/30292 ,  G06F17/30442 ,  G06F17/30463 ,  G06F17/30575

Abstract: A method, apparatus, and system for automatically determining an optimal database subsection is provided. A database subsection is selected to optimize certain benefits when the database subsection is translated, transferred, and cached on an alternative database system, which may utilize a different technology or database engine that provides certain performance benefits compared to the original database system. Algorithms such as multi-path greedy selection and/or dynamic programming may provide optimal or near-optimal results. A host for the alternative database server may be shared with or otherwise located in close physical proximity to improve latency for a database application or client layer. Once the database subsection analysis is completed, a report may be generated and presented to the user, and an implementation script may also be created to automatically configure a client host to function as a cache or replacement system according various cache size configurations described in the report.