IBM DB2 V8, DB2 9 manual 12/18/2007Page 45

Page 45

-Recover to a prior point in time corresponding to the time of FlashCopy

-Reset volumes using FlashCopy, including BSDS and logs

-Restart DB2

-Use transaction SM13 to resolve R/3 units of work

-Recover to a prior point in time using FlashCopy + logs

-Reset volumes using FlashCopy , but use current BSDS and active logs.

Use CHKFREQ of 15 minutes to keep at least a day worth of checkpoints in the current BSDS. Make the active log configuration large enough to hold all log records written between FlashCopy.

Example: FlashCopy every 12 hours. Make sure the same active log data set is not being reused within 12 hours.

- Requires archive logs from point of FlashCopy

(If the active log configuration is large enough, then archives won’t be required).

-Follow the same steps for Conditional Restart, except specify the LOGONLY option on the RECOVERY commands

-If using volume-level-copies to re-establish the date and time of the data (automatically assumes data is being regressed) and then coming forward on the log, the two points-in-time are; A.) The RBA/LRSN of the log suspend, or consistency group, when the volume-level-copy was taken, and B.) The point-in-time to which the database is to be reset to (coming forward on the log, but not all the way to current).

-Use transaction SM13 to resolve R/3 units of work

-Disaster Recovery

-point in time copies, send offsite

-DB2 image copies, send offsite

-disk to disk remote copy mirroring, PPRC, XRC

Copyright 2006 IBM Solutions Technical Sales (STS)

12/18/2007Page 45 of 51

12/18/2007

 

Image 45
Contents Albert D. Rodi Trademarks VII What is new with SAP Web Application Server 7.0 ? What is new with SAP Web Application Server 6.40 ?General Preparation Steps DB2 DBA 12/18/2007Page 6 12/18/2007Page 7 12/18/2007Page 8 12/18/2007Page 9 II z/OS Hardware Preparation 12/18/2007Page 11 III AIX Hardware Preparation IV z/OS Software Preparation Required for High Availability ENQ/SCS SolutionRequired Highly Recommended12/18/2007Page 14 12/18/2007Page 15 Class Nameiggcas 12/18/2007Page 17 DB2 Preparation MLMT=4 MAXCSA=0 DEADLOK=5,1 12/18/2007Page 20 System Longlog Drain Delay Drainwait Retry Retrydelay Timeout TermMaxro Drain ALLVI DB2 Related OSS Notes Sapcl FAQ12/18/2007Page 24 Highly Recommended for AIX Application Servers AIX Software PreparationViii Windows Hardware/Software Preparation SAP Installation Preparation Sample BPXPRMxx Member MAXSHAREPAGES131072Forkcopycow Afinet Transport for TCP/IP DB2 = required/recommended value for SAP Sample DB2 DsnzparmsIRLMSWT=300, * LRDRTHLD=10 MAXKEEPD=8000, * MINSTOR=YES NPGTHRSH=10SYSOPR1=SYSOPR RECALL=YES RECALLD=120 RELCURHL=YESXLKUPDLT=TARGET DSN6ARVP ALCUNIT=TRK, CYL CATALOG=YESMON=YES IDFORE=60 LBACKOUT=NOAPPENSCH=EBCDIC MAXKEEPD=8000, * MINSTOR=YES MXDTCACH=128, * NPGTHRSH=10 PARTKEYU=YES RECALL=YES RECALLD=120 PROTECT=NOSECQTY=100 IDFORE=60 IDXBPOOL=BP3 IMPDSDEF=NO IMPTSCMP=YES LBACKOUT=NO, * LOGAPSTG=100 LOBVALA=1GB LOBVALS=50GBMGEXTSZ=YES MON=YES TSQTY=720 TIMELEN=0 END TCP/IP Connectivity XIISAP SID DR1 SapinstDR11DBM1 DR11IRLMXIV XV Sample OSA-Express GB Configuration GatewayStart PORTGBF8 Recover TABLESPACE/RECOVER Indexspace DB2 Backup/Recovery Notes OSS NoteStop DB2 12/18/2007Page 45 12/18/2007Page 46 Xvii SAP Automation And High Availability Solution NFS 12/18/2007Page 49 XIX Sample SMS Storage Group Assignments Sort SYSSoftw HFS

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.