Oracle International Corporation

Prasad V Bagal

Harish Nandyala

Samarjeet Singh Tomar

Rajiv Wickremesinghe

Richard L Long

Sameer Arun Joshi

Hanlin Daniel Chien

David Friedman

Santhosh Selvaraj

Shie-rei Huang

William Havinden Bridge, Jr

Rich Long

Mahanteshwar Chimangala Maheshwar

Saurabh Manchanda

Ricardo Rey Diez

Amit Roy

David Cavazos Woo

Ana L Solis

Emily Ronshien Su

Sha Chang

Lavina Jain

Darshan Nagarajappa

Radek Vingralek

James Aubrey Williams

Ankur Kemkar

Sanuj Basu

Tao Mao

Yanfei Fan

Dungara Ram Choudhary

Gilberto Arnaiz

John Leys

Willliam H Bridge, Jr

Hemanth Pikkili

Sahaj Agarwal

Somya Gupta

Mounica Prodduturu

Kanchan Ramesh Matkar

Wanding Li

Samarjeet Tomar

Techniques are describe herein for associating storage management properties with a group of files of a database referred to herein as a 'file group'. In this system, storage management properties are defined at the database-level. Thus, multiple databases can be stored across a single disk group, gaining the benefits of having multiple block access devices working in parallel, but each respective database may be associated with a respective file group in a one-to-one relationship, so that each database can have different storage management properties.

Database-level automatic storage management

Techniques for universal cache management are described. In an example embodiment, a plurality of caches are allocated, in volatile memory of a computing device, to a plurality of data-processing instances, where each one of the plurality of caches is exclusively allocated to a separate one of the plurality of data-processing instances. A common cache is allocated in the volatile memory of the computing device, where the common cache is shared by the plurality of data-processing instances. Each instance of the plurality of data-processing instances is configured to: identify a data block in the particular cache allocated to that instance, where the data block has not been changed since the data block was last persistently written to one or more storage devices; cause the data block to be stored in the common cache; and remove the data block from the particular cache. Data blocks in the common cache are maintained without being persistently written to the one or more storage devices.

Universal cache management system

Disclosed is an approach to implement an architecture and methodology that allows rapid access to provisioned software without requiring the entirety of the software distribution to be transferred to the target system in an upfront manner. Instead, a multi-tier architecture is used that allows the software to be provisioned and accessed with efficient access and reads of distribution materials from one or more remote storage locations.

Rapid software provisioning and patching

Techniques are provided for transitioning from a hierarchical file system to an object store. A request is received to change file metadata of a hierarchical file system. In response to the request: in-cache file metadata of the hierarchical file system is modified. The in-cache file metadata includes a directory structure of the hierarchical file system and file metadata of the hierarchical file system. Additionally, an in-store metadata journal entry is generated. The in-store metadata journal entry indicates an update to in-store file metadata. The in-store file metadata includes the directory structure of the hierarchical file system and file metadata of the hierarchical file system and is stored in an object store. The in-store metadata journal entry is stored in the object store. Furthermore, in-store file metadata and in-store metadata journal entry may be used to reconstruct the in-cache file metadata on another node.

System for transition from a hierarchical file system to an object store

Described is an approach for computing a quorum for a two-node non-shared storage converged architecture via a distributed state machine without the need for a quorum device.

Method and system for computing a quorum for two node non-shared storage converged architecture

Duplicate bug report detection using machine learning algorithms and automated feedback incorporation is disclosed. For each set of bug reports, a user-classification of the set of bug reports as including duplicate bug reports or non-duplicate bug reports is identified. Also for each set of bug reports, correlation values corresponding to a respective feature, of a plurality of features, between bug reports in the set of bug reports is identified. Based on the user-classifications and the correlation values, a model is generated to identify any set of bug reports as including duplicate bug reports or non-duplicate bug reports. The model is applied to classify a particular bug report and a candidate bug report as duplicate bug reports or non-duplicate bug reports.

Duplicate bug report detection using machine learning algorithms and automated feedback incorporation

Disclosed is an improved system, method, and computer program product for generating backups in a database system. This is accomplished by using a disaster recovery infrastructure of a database system to generate the database backup, where the backup activities are performed on a standby database system, thereby freeing up the primary database system. To avoid authorization/authentication requirements between the primary and standby that may require human intervention to type passwords when backups are performed on the standby, a backup solution is provided that does not require human intervention to enter passwords when automating the backup process.

Database backup from standby DB

A shared storage architecture persistently stores database files in non-volatile memories (NVMs) of a plurality of computing nodes of a multi-node DBMS. The computing nodes of the multi-node DBMS store data blocks in NVM and each computing node of the DBMS stores copies of each data block stored on the plurality of computing nodes. A computing node that disconnects and subsequently rejoins the DBMS employs an on-demand approach to resilvering stale data blocks that have been updated in other computing nodes in the DBMS while the computing node was offline. A data block may be resilvered on-demand based on an I/O request for a specific data block from a workload running on the reconnected computing node. Stale data blocks on the reconnected computing node are not resilvered unless they are accessed by the workload.

Stale block resynchronization in NVM based systems

Embodiments enable a database management system (DBMS) to manage two levels of disk failure groups. These two levels of redundancy are achieved by grouping the disks of the disk group for the DBMS into two levels of failure groups (i.e., 'data sites' each containing two or more 'failure groups' of disks). This system of disk grouping allows a DBMS to potentially tolerate the loss of both an entire first site and part of a second site. Such a DBMS uses a multi-level voting system, based on both failure group-level votes and site-level votes, to identify the current version of administrative data structures (ADS) that store key administrative data. In addition to data sites that store database data, the DBMS includes a quorum site with a single quorum failure group that stores a copy of the ADS. The quorum site contributes a site-level vote during a multi-level voting event.

Hierarchical fault tolerance in system storage

Techniques are described herein for re-syncing a snapshot database with a base database. Data units of each database are associated with version numbers. When a data unit is modified, the data unit is associated with the current version number. When a snapshot database is re-synced with a base database, particular data units are copied from the base database to the snapshot database, based on the version number associated with the particular data units.

Efficient mirror data re-sync

Systems, methods, and other embodiments associated with separating executables and working data of an application between separate images are described. In one embodiment, a method includes mounting an application image together with a working image to create an application directory for an application. The application image is read-only and includes at least an executable of the application and the working image includes working data modified by the application. The application directory provides files and paths of the files for the application together within a single unified directory while separating the executable in the application image from the working data in the working image. The method includes in response to receiving a write request to the application directory, arbitrating access to the application directory by controlling the processor to write data for the write request to the working image to maintain the working data separate from the executable of the application.

Computerized system and method for patching an application by separating executables and working data using different images

A multi-node cluster is configured for credential management. A method commences by retrieving a super-user credential from a credential record stored in a location accessible to the cluster, then propagating the super-user credential to a set of nodes in the multi-node cluster. A credential creating processes is invoked on at least some of the set of nodes. Application-level credential access can be implemented in a multi-cluster environment by carrying-out an exchange that passes credentials between a first cluster and a second cluster over a secure channel. A protocol is observed whereby one or more applications running on the first cluster receive new credentials for accessing the second cluster from the credential serving process after the credential creating process creates the new credential.

Automatic creation and management of credentials in a distributed environment

A method and apparatus for booting a clustered management system is provided where the configuration information required to boot the system is stored within the system itself. The techniques cope with several issues including finding the configuration data on the physical disk before the logical disk system is established, coping with replicated copies of configuration data, network partitions and disk drive failures that may prevent a booting node to have perfect knowledge of the state of the entire system, and active nodes modifying or moving configuration data while the booting node is searching for a consistent, correct copy of configuration data.

Bootstrapping server using configuration file stored in server-managed storage

Growing community of inventors

Saratoga, CA, United States of America

Prasad V Bagal