II08939: CHANGES TO DB2 ADMINISTRATIVE GUIDE VOL. 2 SC26-4888-00 THAT DID NOT MAKE THE V3 GA PUBS. CONT. OF II07836, II08064, II08714

APAR status

• Closed as canceled.

Error description

• This APAR documents changes to the DB2 Administration Guide
  Volume 2 SC26488800 which did not make Version 3 GA pubs.
  5740xyr00 R310   Continuation of II07836, II08064, II08714.
  ================================================================
  Version 3 Book Title: Administration Guide, Vol. II
  chap6 page140:
  Change Description:
  
  When you switch back and forth between DB2- and user-managed
  data sets, you can lose the allocation values in columns
  PRQTY and SQTY in the catalog table, SYSIBM.SYSTABLEPART.
  One possible solution is to alter the table space between
  the original storage group and a second storage group,
  preserving the allocation quantitites.
  ================================================================
  Version 3 Book Title: Administration Guide Volume II
  chap6 page140:
  Change Description:
  
   5. Convert the datasets back to DB2-managed using
      new DB2 storage group. Use the following
      SQL ALTER TABLESPACE and ALTER INDEX statements:
  
      ALTER TABLESPACE dbname.tsname
        USING STOGROUP stogroup-name
        PRIQTY priqty
        SECQTY secqty;
  
      ALTER INDEX index-name
        USING STOGROUP stogroup-name
        PRIQTY priqty
        SECQTY secqty;
  ===============================================================
  Version 3 Book Title: Administration Guide Volume II
  chap6 page147:
  Topic: Order of Recovering Catalog & Directory Objects
  Item 14 incorrectly lists the catalog visibility tables as
  needing to be recovered. These tables no longer exist in V3.
  ================================================================
  Version 3 Book Title:  Administration Guide, Volume 2
  Pages: 4-140
  Change description as it appears on CD-Rom:
  Add the following information at the end of step 5 on
  page 4-140:
  
     If you specify USING STOGROUP without specifying the
     PRIQTY and SECQTY clauses, the default values are used.
     For more information about USING STOGROUP, see "SQL
     Reference".
  ===============================================================
  Version 3 Book Title: Admin. Guide Vol. 2
  Pages: 6-100
  Change Description under topic How to Defer Recovery:
  
  change the bullet from:
    Leave the object's data sets unready....
  to:
    Vary the device (or volume) on which the objects
    reside offline.  If the data sets containing
    an object are not available, and the object
    requires recovery during restart, DB2 flags it as
    stopped and requiring deferred restart.  DB2 then
    restarts without it.
  ============================================================
  Version 3 Book Title: Administration Guide, Volume 2
  Pages: 6-247
  Change Description:
  Replace the first sentence under topic Total Loss of Log with:
  
  Even if all current copies of the BSDS and the active or
  archive log or both have been destroyed or lost, DB2 can
  still be restarted and data that belongs to that DB2
  subsystem can still be accessed, provided that all system
  and user table spaces have remained intact and you have a
  recent copy of the BSDS.
  ===============================================================
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• close for DB2INFO retention
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels