Recover to prior point in time

-A recovery of all tablespaces, indexspaces, DB2 catalog, and DB2 Directory to a previous log RBA (three ways to acomplish this)

-Conditional Restart to recover to any previous point in time using DB2 Image Copies

-Identify LOG RBA of prior point in time time: With DB2 V7 and the CHKFREQ parameter for controlling DB2 checkpoint time the recommendation is to set CHKFREQ at 15 minutes. That will ensure a days worth of checkpoints on the checkpoint queue in the BSDS, and will provide four RBAs / LRSNs every hour that can be used in the conditional restart.

-Identify Tablespaces modified after the RBA to reduce the number of recovery jobs. Perform an analysis of the DB2 logs from the recovery RBA to the

current end of the log in order to minimize the number of objects to be recovered. In this case recover the DB2 Catalog/Directory and

only those objects that are identified as a result of the analysis. Use REPORT RECOVERY utility against all tablespaces or run DSN1LOGP SUMMARY

The best approach to identifying only the objects that need recovering is to analyze the archive logs that have been created between the two points-in-time. The recommendation is to put an automated process in place to analyze the archive logs as they are created, rather than waiting until a recovery situation arises.

The archive logs should be analyzed for all objects that have at least one of the following four message numbers, indicating a change to the object. --DSN1151I,

--DSN1152I, --DSN1160I, --DSN1162I.

-STOP DB2

-Save the BSDS and log datasets after the target RBA

-Build DB2 Conditional Restart Rceord using DSNJU003 with ENDRBA=target RBA

-Update ZPARMS to set DEFER=ALL, Restart DB2

-Recover DB2 Catalog and Directory to current point in time. Refer to the Utility Guide, Chapter on RECOVER; Instructions for Specific Tasks; Recovering catalog and directory objects.

-all user indexes on the catalog and directory

-Recover R/3 Tablespaces and Indexspaces identified above to current point in time

-Stop DB2

-Update ZPARMS to reset DEFER parameter

-Perform Full Offline Backup

-Restart DB2

-Use transaction SM13 to resolve R/3 units of work (business transactions)

Copyright 2006 IBM Solutions Technical Sales (STS)

12/18/2007Page 44 of 51

12/18/2007

 

Page 44
Image 44
IBM DB2 9, DB2 V8 manual Stop DB2

DB2 V8, DB2 9 specifications

IBM DB2 is a family of data management products that provide powerful capabilities for managing large amounts of data. Among its various versions, DB2 9 and DB2 V8 stand out due to their advanced features and technologies that cater to both enterprise needs and modern database requirements.

DB2 9, also known as "Viper," was a significant release that brought substantial enhancements to the database management system. One of its standout features is its support for XML data. This version introduced a native XML storage architecture, allowing users to store, retrieve, and manage XML data efficiently. The advanced query capabilities for XML data made it easier to integrate both structured and unstructured information into applications.

Another notable aspect of DB2 9 is its enhanced security features. It introduced features like label-based access control, ensuring that sensitive data could be properly managed according to the security policies of an organization. This version also included a transparent data encryption mechanism, protecting data at rest without impacting performance.

DB2 V8, released prior to DB2 9, presented several key features that had a lasting impact on database technology. One of its major advancements was the introduction of pureXML, which laid the groundwork for handling XML data. DB2 V8 also provided improved performance through enhancements such as table partitioning, which allowed for more efficient data organization and retrieval.

Additionally, DB2 V8 emphasized high availability and disaster recovery, incorporating features like DB2 HADR (High Availability Disaster Recovery). This allowed organizations to ensure data continuity even in the event of system failures, a critical aspect for enterprise environments that rely on uninterrupted access to their data.

Both versions of DB2 leveraged advanced technologies such as multi-version concurrency control (MVCC), which enhanced transaction integrity and performance. Their ability to support various platforms, including Linux, UNIX, and Windows, demonstrated IBM's commitment to providing flexible solutions tailored to different environments.

In summary, both IBM DB2 9 and DB2 V8 established a strong foundation in the database management ecosystem. With features focused on XML data management, enhanced security, performance improvements, and high availability, these versions have equipped organizations with the tools necessary to handle contemporary data challenges efficiently and effectively. Their legacy continues to influence database technology today, highlighting IBM's enduring impact on data management solutions.