Abstract: A database recovery and index rebuilding method involves reading data pages for a database to be recovered as recovery bases; retrieving all log records from stored post-backup updates and sorting the retrieved log records; as the data pages to be recovered are read, applying the sorted log records to their respective data pages; as the applying completes for individual data pages, extracting and sorting index keys from the individual data pages for which the applying is complete, until all index keys have been extracted from all individual data pages and sorted; on an individual recovered page basis, writing the recovered individual data pages into the database; and when all index keys have been extracted and sorted from all of the recovered individual data pages, rebuilding indexes of the database using the sorted index keys and writing the rebuilt indexes to the non-transitory storage.

Abstract: A database recovery and index rebuilding method involves reading data pages for a database to be recovered as recovery bases; retrieving all log records from stored post-backup updates and sorting the retrieved log records; as the data pages to be recovered are read, applying the sorted log records to their respective data pages; as the applying completes for individual data pages, extracting and sorting index keys from the individual data pages for which the applying is complete, until all index keys have been extracted from all individual data pages and sorted; on an individual recovered page basis, writing the recovered individual data pages into the database; and when all index keys have been extracted and sorted from all of the recovered individual data pages, rebuilding indexes of the database using the sorted index keys and writing the rebuilt indexes to the non-transitory storage.

Abstract: A database recovery and index rebuilding system involves at least one processor coupled to memory, storage, a database, and sets of image copies and post-backup updates. When database reconstruction is required, the processor will i) access the image copies; ii) access post-backup updates to be re-applied; iii) without regard to “ii)”, read data pages to be recovered into objects; iv) concurrently with “iii)”, retrieve and sort log records from the post-backup updates; v) as the data pages to be recovered are read in “iii)”, apply the sorted log records; vi) as “e)” completes and concurrently with “v)”, extract and sort index keys; vii) concurrently with “vi)” and on an individual recovered page basis, write the recovered data pages into the database; viii) when all index keys have been extracted and sorted, initiate database index rebuilds; and ix) when rebuilt, store the rebuilt indexes without regard to whether “vii)” has completed.

Abstract: A database recovery method involves: a) accessing image copies; b) accessing updates to be re-applied to reconstruct the database; c) reading into objects, from the image copies, data pages to be recovered; d) concurrently with “c)” retrieving and sorting log records from the updates; e) as the data pages are read into the objects in “c)”, applying the sorted log records, in timestamp order; f) as “e)” completes for individual pages, and concurrently with “e)” with respect to pages for which applying is not complete, extracting and sorting index keys, from pages for which the applying is complete, until all index keys have been extracted and sorted; g) concurrently with “f)”, writing recovered pages into the database; h) initiating a rebuild of database indexes using the extracted and sorted index keys; and i) when the database indexes have been rebuilt, writing them to storage without regard to whether “g)” completed.

Abstract: A system, method a computer usable storage medium tangibly embodying a program of instructions executable by the computer to perform a computer-based method for restoration of a database from a failed data recovery. For each failed data recovery the method generates a log error data set having log records of a faulty transaction unapplied to data due to inconsistency. Log error data set is directly useable by a log analysis tool to regenerate and redo the unapplied faulty transaction to recover the data and by a print log tool to diagnose the faulty transaction. Log records mimic format of records of an archive log data set and identify data objects, faulty transactions on the data objects and a range of the unapplied data objects' updates.

Abstract: A method for performing a system level backup of a log-ahead database management system (DBMS) without suspending updates by application programs is described. The DBMS comprises a database mainline system, a backup utility and a restore utility. The data and log records are stored on separate storage volumes. Log records are written to identify objects that require special handling during the point-in-time recovery. The database engine operates normally during a backup except for suspending actions that would alter the file system catalog or write updates across a storage volume boundary; and by freezing the REDO log point in its checkpoint information. The backup utility copies the data volumes first and optionally the log volumes second while updates are allowed. The resulting inconsistencies are resolved either during a DBMS restart or during a point-in-time (PIT) recovery performed by the restore utility.

Abstract: A system, method and a computer usable medium tangibly embodying a program of instructions executable by the computer to perform a computer-based method for restoration of a database from a failed data recovery. For each failed data recovery the method generates a log error data set having log records of a faulty transaction unapplied to data due to inconsistency. Log error data set is directly useable by a log analysis tool to regenerate and redo the unapplied faulty transaction to recover the data and by a print log tool to diagnose the faulty transaction. Log records mimic format of records of an archive log data set and identify data objects, faulty transactions on the data objects and a range of the unapplied data objects' updates.

Abstract: A method for performing a system level backup of a log-ahead database management system (DBMS) without suspending updates by application programs is described. The DBMS comprises a database mainline system, a backup utility and a restore utility. The data and log records are stored on separate storage volumes. Log records are written to identify objects that require special handling during the point-in-time recovery. The database engine operates normally during a backup except for suspending actions that would alter the file system catalog or write updates across a storage volume boundary; and by freezing the REDO log point in its checkpoint information. The backup utility copies the data volumes first and optionally the log volumes second while updates are allowed. The resulting inconsistencies are resolved either during a DBMS restart or during a point-in-time (PIT) recovery performed by the restore utility.

Abstract: The present invention discloses a technique for restoring a database in a computer. In accordance with the present invention, the database contains objects and is stored on a data storage device connected to the computer. After a system failure, a log file is read. The log file contains one or more modifications to the database objects. Each modification has an associated data page and time stamp or sequence number. The modifications are sorted by at least one predefined sorting key value. The sorted modifications are then grouped by database object. The sorted modifications are applied to each database object in parallel.

Abstract: A method, apparatus, and article of manufacture for a computer implemented recovery system for restoring a database in a computer. The database contains objects and is stored on a primary data storage device connected to the computer. Objects of different types in the database are copied from the primary data storage device to a secondary data storage device. Modifications to the objects are logged in a log file. A recovery indicator is received that indicates that recovery of the objects in the database is required. The objects are copied from the secondary data storage device to the database on the primary data storage device. Modifications in the log file are applied to the copied objects during one pass through the log file.