International Business Machines Corporation

Laura Michiko Kunioka-Weis

Thomas Majithia

James Z Teng

Jeffrey Allen Berger

Craig Alan Friske

Haakon Roberts

William James Franklin

James Alan Ruddy

John Marland Garth

Ka Chun Ng

Regina J Liu

Binghui Zhong

Szu-Huey Chuang

Daniel Keith Courter

Knut Stolze

Thomas Abel Beavin

James Zu-Chia Teng

Julie Ann Watts

Oliver Koeth

Jeffrey William Josten

Paramesh Sampatrai Desai

Bjoern Broll

Claus Kempfert

Kathryn Ruth Zeidenstein

Yufen Wang

Deborah A Matamoros

David Elmer Raiman

Haakon Philip Roberts

Kevin Daniel Gougherty

Ming-Hung Hu

A method for archiving a predefined portion of a table residing in a database system includes: creating a first backup copy of the portion of the table; assigning to the portion of the table an access state flag; setting the access state flag; using the access state flag for preventing modification of existing backup copies of the portion of the table and for preventing further backup operations on the portion of the table; archiving the portion of the table to a separate system; deleting the content of the portion of the table from the database system and retaining the access state flag in the database system.

Method and system for a safe archiving of data

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.

Relational database recovery

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 &#x201c;iii)&#x201d;, apply the sorted log records; vi) as &#x201c;e)&#x201d; completes and concurrently with &#x201c;v)&#x201d;, extract and sort index keys; vii) concurrently with &#x201c;vi)&#x201d; 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 &#x201c;vii)&#x201d; has completed.

Recovering data to a point in time before pending definition changes are materialized in a relational database management system. One or more definition changes to a database schema are received. Original data base schema attributes are saved as point in time metadata in a catalog table until the one or more definition changes have been materialized. During recovery processing, it is determined for each object being recovered whether the object is being recovered to a point in time prior to which the one or more definition changes were materialized. In response to determining that an object is being recovered to a point in time prior to which the one or more definition changes were materialized, the saved point in time metadata is used for the object in the recovery process.

Point in time recovery support for pending schema definition changes

Recovering data to a point in time before pending definition changes are materialized in a relational database management system. One or more definition changes to a database schema are received. Original data base schema attributes are saved and maintained as point in time metadata in a catalog table until the one or more definition changes have been materialized. During recovery processing, it is determined for each object being recovered whether the object is being recovered to a point in time prior to which the one or more definition changes were materialized. In response to determining that an object is being recovered to a point in time prior to which the one or more definition changes were materialized, the saved point in time metadata is used for the object in the recovery process.

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 &#x201c;e)&#x201d; completes for individual pages, and concurrently with &#x201c;e)&#x201d; 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 &#x201c;f)&#x201d;, 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 &#x201c;g)&#x201d; completed.

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.

System and method for minimizing data outage time and data loss while handling errors detected during recovery

A method, apparatus, and article of manufacture for a computer-implemented repartitioning system. Data is repartitioned in a database stored on a data storage device connected to a computer. First, it is detected that a partitioning scheme for the data has been altered. Next, partitions that would be affected by the altered partitioning scheme are identified. Then, the identified partitions are reorganized based on the altered partitioning scheme.

Repartitioning data

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.

Recovering different types of objects with one pass of the log

Data is loaded to a data structure while an image copy of the data structure is concurrently formed. After data records are obtained from one or more data sources, each of the data records is associated with one of multiple pages. As each page is completed, it is written to a primary data structure. Also upon completion of each page in the primary data structure, concurrently with storage of the page in the primary data structure, an image copy of the page is made in an image copy data set. Partially or completely failed primary data structures may also be restored using image copies made according to the invention. Timestamps mark the time at which each page are made; image copy pages include the same timestamp as their respective primary pages. Upon detecting a data structure failure, each page of the image copy is sequentially reviewed. For each image page being reviewed, the page's timestamp is compared with the timestamp of the corresponding page from the primary data structure. The page is copied from the image copy to the primary data structure only if the timestamp comparison indicates that the image page is more recent than the page from the primary data structure.

Growing community of inventors

Morgan Hill, CA, United States of America

Laura Michiko Kunioka-Weis