Articles & Content
Topic: DB2 for z/OS
DATE: 2009-10-7 (09:45 - 10:45)
SPEAKERS: Ulf Heinrich (Software Engineering)
Every DBA strives to maintain a healthy DB2 environment every day. However, there are numerous lingering misconceptions about database health to which many organizations fall prey. These misconceptions occur because DBAs believe in, or apply concepts that are, objectively false.Like old wives' tales, some misconceptions exist simply because they have been passed down from older generations. In terms of DB2, this means that even best practices true for older DB2 versions may no longer be best. This article comprises a number of the most common ones about DB2 maintenance and recovery.
EXP. LEVEL: Intermediate,Advanced
Lies, damned lies, and statistics.a. Dispelling the delusions about using real-time statistics.b. Eliminating unnecessary RUNSTATS.
All backups are there, but...a. Are you migrating too early to tape. Why you should wait.b. Virtual tape storage is as good as DASD. Not! Hard and fast rules concerning VTS.c. Oops, the archive logs are on tape. Serious considerations for logs.
d. Use mirroring instead of dual logging. Why this concept fails.e. Fast, faster, flash it! FlashCopy hailed as "the end of the image copy". Choosing objects wisely for FlashCopy.f. Copying indexes?
Recovery Ready, Set, Goa. What about recovery time objectives? Do you know what your RTOs are?b. Small objects are fast to recover; < misguided notion.c. Objects with high update rates. The risk of recovering such objects from nightly backups.
d. A, B, Z's of ZPARMs: Why ZPARM defaults are not one-size-fits-all.e. How will the CF perform during a recovery.f. Multi-volume data sets rule! Don't kiss your RTOs goodbye with this concept.Using logs for database auditing? Reasons why not.
Click Here to Download
NOTE: These are only open to members of IDUG. If you are not a member, please CLICK HERE for more information.