Abstract:
A first request may be received to update a first set of values. The first set of values may be stored at a first location within a first data page of a database. The first location may be read-only. In response to the receiving of the first request, a first set of records may be inserted into a second data page. The first set of records may include the update of the first set of values. In response to the inserting, a forward pointer may be stored in the first data page that points to the first set of records on the second data page. One or more committed values may be identified on the second data page. In response to the identifying, the one or more committed values may be merged from the second data page to a third data page.
Abstract:
Techniques for recovering from session failures between clients and database servers are described herein. A first session may be established between a client and a first database server to handle a database query for the client. A request for data associated with the first session may be received by the first database server from the client, and the data retrieved. Prior to responding to the request, the data is spooled to a first session state stored in a repository made accessible by at least one computing device. The computing device(s) controls access to session states in the repository that correspond to sessions between clients and database servers. The computing device(s) enables sessions to be reestablished between the clients and database servers by accessing data of the session states in the repository and transmitting the data in response to messages received from the database servers containing session identifiers.
Abstract:
Provisioning, managing and tracking of services provided by a cloud infrastructure system are described. A subscription order request from a customer for services provided by the cloud infrastructure system is received. A separation of roles performed by different customer entities in a customer's organization when the customer subscribes to services in the cloud infrastructure system is determined. The roles relate to providing information about different portions of the subscription order by the customer entities. Upon completion of the assigned roles by the relevant customer entities, the subscription order is provisioned to the customer.
Abstract:
Embodiments of the invention relate techniques of implementing role-driven notification. The techniques can include determining a location of a role in a role hierarchy and a corresponding location of a first notification template in a notification template hierarchy. The techniques can also include identifying one or more child roles of the role corresponding to the user and one or more child notification templates of the notification template corresponding to the user. The techniques can include generating a second notification template, the second notification template including the one or more rules included in each of the one or more child notification templates and sending a notification for the user based on the second notification template.
Abstract:
Data synchronization includes establishing a plurality of target data tables based on a source data table in which data to be synchronized is stored, determining a current target data table from the plurality of target data tables, synchronizing the source data table and the current target data table, and directing an application server to access the current target data table upon successful completion of synchronization.
Abstract:
Changes to data in a column in an in memory array resulting from operations of a transaction thread can be written to a database object associated with the column. The database object can be marked for materialization upon completion of all of the plurality of operations of the transaction thread such that the column and the changes are materialized from the in-memory array to one or more pages stored on a persistent storage based on the marking.
Abstract:
A technique for applying hardware transaction memory to an arbitrarily large data structure is disclosed. A data updater traverses the data structure to locate an update point using a lockless synchronization technique that synchronizes the data updater with other updaters that may be concurrently updating the data structure. At the update point, the updater performs an update on the data structure using a hardware transactional memory transaction that operates at the update point.
Abstract:
Example embodiments involve a system, computer-readable storage medium storing at least one program, and computer-implemented method for modifying a database object with one or more dependent database objects. The method may include receiving a data definition statement involving a modification to a database object. The received data definition statement includes a clause imposing a restriction on the modification to the database object. The method further includes determining whether the modification results in invalidation of at least one dependent database object in response to the clause being included in the received data definition statement. Based on determining that the modification results in the invalidation of at least one dependent database object, the modification to the database object is prevented. Based on determining that the modification does not result in the invalidation any dependent database objects, the modification to the database object is performed in accordance with the data definition statement.
Abstract:
Generating a digest in a transactional memory environment for performing transactional executions, the transactional memory environment supporting transaction nesting is provided. Included is generating for a transaction, by a computer system, a computed digest based on the execution of at least one of a plurality of instructions of the transaction; based on beginning a nested transaction, executed within the transactional region of the transaction, saving a snapshot of the computed digest as a nesting level snapshot; beginning execution of the nested transaction: updating, by the computer system, the computed digest based on the execution of at least one of a plurality of instructions of the nested transaction; and based on an abort of the nested transaction, restoring the computed digest from the nesting level snapshot and restarting the nested transaction.
Abstract:
A system and method of implementing distributed transactions on a KVS having a simple configuration without unnecessarily causing rollbacks. The method includes providing a management map including a global transaction ID as a key and {a state of global transaction, a waiting global transaction ID list} as a value, starting a management local transaction on one of the plurality of servers, inserting a key-value pair including an ID of the global transaction to be processed as a key and {a state “working”, null} as a value into the management map in the management local transaction, and updating a value having the ID of the global transaction to be processed as a key to {a state “waiting”, a waiting global transaction ID list for the global transaction to be processed} on the management map in the management local transaction and committing the management local transaction.