Abstract:
Techniques are provided for block-level fail atomicity on byte-level non-volatile media. In one technique, an offset table and application data that stores content of a file are stored for a file. The offset table includes multiple entries, each entry being associated with a different offset value and storing a logical block address (LBA) that references a location in the application data. In response to receiving a request, that includes an input buffer and an offset value, to update the file: (a) an entry, in the offset table, that corresponds to the offset value and comprises a first LBA is identified; (b) a second LBA that is considered free is identified; (c) the second LBA is replaced with the first LBA; (d) the input buffer is written to a location, in the application data, that the second LBA references; and (e) the second LBA is added in the entry.
Abstract:
Consistent External Table Access maintains transactional consistency for queries that access external tables stored in a DBFS. This ability is achieved by bypassing the OS. One or more database processes executing a query that access an external table stored in a DBFS access the database-file table like other database tables in the DBMS that can be accessed to execute a query. Based on metadata stored in the DBMS regarding how an external table is stored in a DBFS, a DBMS is able to marshal database processes that access database-file tables directly to execute a query.
Abstract:
A system and method can provide a scalable data storage in a middleware environment. The system can include a cluster of replicated store daemon processes in a plurality of processing nodes, wherein each machine node can host a replicated store daemon process of the cluster of replicated store daemon processes. Additionally, the system can include one or more replicated stores associated with an application server the processing node. The replicated store daemon cluster can persist data from a replicated store to another node, the other node also being associated with the replicated store daemon cluster. The system and method can additionally support a messaging service in a middleware environment. The messaging service can use the replicated store to store a copy of a message in the local processing node and on another processing node associated with the same replicated store daemon cluster.
Abstract:
Techniques are provided for block-level fail atomicity on byte-level non-volatile media. In one technique, an offset table and application data that stores content of a file are stored for a file. The offset table includes multiple entries, each entry being associated with a different offset value and storing a logical block address (LBA) that references a location in the application data. In response to receiving a request, that includes an input buffer and an offset value, to update the file: (a) an entry, in the offset table, that corresponds to the offset value and comprises a first LBA is identified; (b) a second LBA that is considered free is identified; (c) the second LBA is replaced with the first LBA; (d) the input buffer is written to a location, in the application data, that the second LBA references; and (e) the second LBA is added in the entry.
Abstract:
A system and method can provide a scalable data storage in a middleware environment. The system can include a cluster of replicated store daemon processes in a plurality of processing nodes, wherein each machine node can host a replicated store daemon process of the cluster of replicated store daemon processes. Additionally, the system can include one or more replicated stores associated with an application server the processing node. The replicated store daemon cluster can persist data from a replicated store to another node, the other node also being associated with the replicated store daemon cluster. The system and method can additionally support a messaging service in a middleware environment. The messaging service can use the replicated store to store a copy of a message in the local processing node and on another processing node associated with the same replicated store daemon cluster.
Abstract:
Techniques for moving data files without interrupting access are described. A first process moves a database file from a first location to a second location while the database file is accessible to one or more other processes for read or write operations. According to one technique, the first process communicates a move status and a copy range into the database file to one or more database server instances executing the one or more other processes. The one or more other processes then perform input/output (IO) operations on the database file based at least in part on the move status and the copy range communicated by the first process.