Oracle International Corporation

Delphix Corporation

Michael James Stewart

Wei-Ming Hu

Mark Dilman

Hubert Ken Sun

Vinay H Srihari

Juan R Loaiza

Balasubrahmanyam Kuchibhotla

William Havinden Bridge, Jr

Matthew Allan Ahrens

J William Lee

Kevin S Neel

Adam H Leventhal

Kant C Patel

Feroz Alam Khan

Leonid Novak

Bhaskar Mathur

Subhadeep Sinha

Lakshminaray Chidambaran

Saravanakumar Ramasubramanian

Margaret Susairaj

Alok Pareek

Muthu Olagappan

Lawrence HinLuen To, Jr

Margaret Susairai

A computer is programmed to identify failures and perform recovery of data. Specifically, in several embodiments, the computer is programmed to automatically check integrity of data in a storage structure to identify a set of failures related to the storage structure. The computer is further programmed in some embodiments to identify, based on one failure in the set of failures, a group of repairs to fix that one failure. Each repair in the group of repairs is alternative to another repair in the group. The computer is also programmed in some embodiments to execute at least one repair in the group of repairs, so as to generate corrected data to fix the one failure. In certain embodiments, the corrected data is stored in non-volatile storage media of the computer.

Data recovery advisor

Virtual databases are provisioned using point-in-time copies of a source database. Transaction logs received from the source database are applied to a point-in-time copy of the source database to create recovery milestones comprising database blocks that can be used to provision virtual databases. The recovery milestones are created in advance of receiving a request to provision a virtual database. Each recovery milestone is validated to determine that a consistent database snapshot can be created using the recovery milestone. If a problem is identified that prevents creation of a consistent database snapshot, the problem is fixed before creating the next recovery milestone. In response to receiving a request to provision a virtual database corresponding to a point in time, a recovery milestone is identified and transaction logs applied to the recovery milestone to create a database snapshot corresponding to the requested point in time.

Creating validated database snapshots for provisioning virtual databases

A database storage system allows users to modify the state of a virtual database. The database storage system provides a respective virtual database (VDB) at a respective destination, the respective VDB having a first timeflow stored in a respective container. A user can send a request to rewind a VDB. The request identifies timeflow of the VDB and a state of the VDB associated with a timeflow. The database storage system modifies the virtual database to refer to database blocks associated with a snapshot of the VDB associated with the identified timeflow. The database storage system maintains a new timeflow for the modified VDB. The database storage system also allows the virtual database to be refreshed to a state of a source database. The source database can be a database stored in an external system or a virtual database stored within the database storage system.

Virtual database rewind

Techniques are provided to allow users to define a global service that is offered across multiple replicated databases. Database clients connect to and use a global service just as they do with regular services on a single database today. Upon receiving a connection request, a collection of components, referred to collectively as the Global Data Service framework (GDS framework), automatically chooses the best database server instances to which to connect a client. Once those connections have been established, the clients determine which database server instance, of those database server instances to which they are connected, to send requests to based, at least in part, on advisory messages sent to the clients by the GDS framework.

Providing services across systems that manage distributed replicas

A computer is programmed to execute a diagnostic procedure either on a pre-set schedule or asynchronously in response to an event, such as an error message, or a user command. When executed, the diagnostic procedure automatically checks for integrity of one or more portions of data in the computer, to identify any failure(s). In some embodiments, the failure(s) may be displayed to a human, after revalidation to exclude any failure that no longer exists.

Data corruption diagnostic engine

A computer is programmed to automatically generate repairs to fix failure(s) while taking into account dependencies between repairs relative to one another, by grouping failures. In some embodiments, the computer uses a map that associates each failure type with repair types that are alternatives to one another, and uses another map that associates each repair type with a template that creates the repair when instantiated. In certain embodiments, repairs within a repair plan are consolidated, to avoid duplicates and redundancies.

Repair planning engine for data corruptions

Techniques are described herein for returning a repository to a prior state. The repository may be, for example a database, and the prior state may be, for example the consistent state that the database had at a particular point in time in the past. When a operator-caused error has been introduced to the database by changes made by an already-committed transaction, the techniques described herein may be used to recover from the error by returning the database to a point in time prior to the commit time of the transaction that introduced the error. The techniques involve the generation of 'physical undo' information, and the use of the physical undo information in conjunction with physiological undo and physiological redo to efficiently return a repository to the prior state.

Flashback database

Growing community of inventors

Belmont, CA, United States of America

Michael James Stewart