II14702: AVOIDING MIGRATION ISSUES FOR FASTER MIGRATION HINTS & TIPS TO V10

APAR status

• INTRAN

Error description

• Due to some customers running into issues while migrating, this
  Info APAR was recently developed with the following bullets to
  aid customers to have a faster Migration by avoiding known
  migration issues.
  .
  o  If CATMAINT | DSNTIJTC fails, please open an SR pmr and list
     the error and provide the appropriate doc for the error -
     when it happens.  L2 may be able to identify the +fix or
     resolution for V10 or recommend Fallback to V8 (asap) and
     then Rebuild, Recovery and/or Repair problem V8 objects
     there.  Especially for DSNxxxxx names objects.
     +  Please use the  1 (800) IBM SERV =1 (800) 426-7378 number
        for escalating, provide the error and error doc asap.
  .
  o  Having correct migration Maintenance level and/or latest
     Migration fixes applied first may help avoid any issues
     during V10 Migration. (L2 DB2XT can provide SIMPLEMOD Reports
     listing missing Hipers,  PE/y fixes for known PE issues for
     both V8 or V9  & V10 run against your Diagnose Display Mepl).
     Recent fixes for Migrations include:
     +  UK75727 v10/PM52752  04E E40601 DSNUEXDL+1402  (PE/y fix)
     +  UK76530 v10/PM56449  Multi abends Rollback/(2) DDF
        Threads (Hiper) includes  04E 00C90101 DSNKDLE: 500A
        & DSNB250E w/DSNKUNR2
     +  UK80924 v10, UK80925 v9/PM62119  04E E70014 DSNXLDDL+2234
        when accessing catalog objects or resources.
  .
  o  Dropping the User Defined objects in V8 or V9.  Use this
     query to find them.  (See V10 SMS-Managed bullet below.)
        SELECT * FROM SYSIBM.SYSINDEXES
           WHERE DBID = 0006
           AND OBID >398 AND OBID < 600;
  
     To get a good DSNTIJTC RC:00, and once established on DB2 V10
     CM8 you can elect to Create the ones you need again.
  .
  o  Remember, while in {Shadow like} V10 migration and DSNTIJTC
     has not successfully Run, all Catalog or Directory TBS
     updates/changes are restricted, resulting in 00C900A6 and/or
     00D70014 issues.  Users will only be allowed to do r/o
     activities.
     +  If you  -Display UTIL and  -Display Thread on V8 - V9 and
        eliminate these users; it will help avoid unnecessary
        delays caused by r/w requests - errors once DB2 V10 is
        started.
     +  There should be no Utilities, no DDL, no GRANTs or
        REVOKEs, and no BINDs.
     +  Have Mgmt send out EMails to DBA's & System Programmers
        to ensure they are aware of the migration timeframe.
     +  Ensure no long running Batch jobs have switched times or
        will exist during your planned migration timeframe.
     +  There are a number of vendor products that access the
        catalog and never commit.  These will also interfere with
        the DSNTIJTC and DSNTIJEN jobs.  Such products must be
        terminated before running either of these jobs.
     +  If 00C900A6 with ABEND0C1 DSN9SCN9 & DSNFWTO occurs during
        DSNTIJTC, CATMAINT to be restarted.  Please collect the
        Dump & Logrec for L2 review and confirmation on CA's
        ASR230Z 01/29/07, II14195 - CA Fix Q094419.
  .
  o  If a failed V8 utility was not terminated before DSNTIJTC job
     was started for V10 migration, and attempt to terminate will
     result in this message.
      DSN
            -TERM UTIL(*)
  
      DSNU115I  -DB2P DSNUGDIS - UNLOAD UTILITY WITH
                  UTILID = UNLOAD.BCT CAN ONLY BE
                  TERMINATED BY A MEMBER WITH THE
                  SAME RELEASE = 810
      DSN9022I  -DB2P DSNUGCCC '-TERM UTIL' NORMAL COMPLETION
  
     Based on DSNU115I message, customers need to go back V8 to
     terminate that utility and then continue the migration.  This
     emphasizes the importance of -Display and -Terminate commands
     already mentioned.
  .
  o  Having a clear go / no go timeline is also good, but you must
     to stick to it.  If you think you can fallback after DSNTIJTC
     fails and do the required recovery actions (rebuild, recover,
     repair, (terminate)) on V8 | V9 ... and then try migrating to
     V10 & run  CATMAINT | DSNTIJTC again -- then do so.
     If  L2  recommends a matching +fix, and you can accept, apply
     it in time to re-try running  CATMAINT | DSNTIJTC -- then do
     so.
  .
  o  A Soft Fallback when DSNTIJTC fails or even if RC:00 during
     the initial phase of V10 to V10 CM is relatively easy.  Every
     thing it creates or alters is against the real table spaces
     or indexes.  However, V8 and V9 can deal with all of these
     changes with no problem.  It is safe, easy and fast to
     fallback to the original V8 | V9 catalogs.
     +  Remember to Term Util  ( i.e. V10 DSNTIJTC CATMAINT job)
     +  If you ever run into a severe issue after migrating to
        V10 Compat mode,always contact IBM DB2 first.
        +  If the error occurred well after V10 CMx, please open
           a separate SR PMR, include the error and error doc.
  .
  o  Starting DB2 in Maint mode is good, even if it's not in the
     Migration steps.  It limits users to install SYSADM, install
     SYSOPR,and SECADM.  For Data Sharing, it restricts access
     only on the DB2 member you execute the command from.  Other
     members of the group are unaffected.
     +  Most Data Sharing migrations are less time consuming if
        the other members are down.
  
        Note:  Stored procedures calls will fail with SQLCODE -471
        reason code 00E79004, when DB2 is started in maintenance
        mode.  Therefore, restart DB2 in normal operating mode
        before attempting to run DSNTIJRV, the validation job
        for DB2-supplied routines.
  .
  o  For S222 issues : Double check status on IRLM and it is
     'unique' naming convention to ensure you have the correct
     Release levels and a separate unique name from DB2.
     Size or Space increases are necessary for V10.
  o  Check for an active bad IRLMPROC and disable if you receive
     DSNT803I  > DB2 CANNOT IDENTIFY TO IRLM.
  
     *DSNV086E > DB2 ABNORMAL TERMINATION REASON=00E30800
     *IEF450I DSNRMSTR DSNRMSTR - ABEND=S04E U0000 REASON=00E30800
  .
  o  V10 SMS-Managed EA requirements (Extended Addressability)
     With DB2 V10, SMS will manage and control all new catalog
     changes, all the conversions to universal table spaces and
     all new catalog and directory indexes and table spaces.  All
     the new indexes and table spaces being added in DB2 V10 will
     also use Extended Addressability (EA).  If DB2 detects that
     the catalog and directory are not in an SMS-compliant
     environment, an abend or DSNTIJEN or DSNTIJTC job failure
     can occur.  Messages IDC3009I IGG0CLAT 80, DSNTIJEN or
     DSNTIJTC failure with DSNT500I & 00D70025 issues.
  .
    +A fast circumvention is to Drop & Recreate the problem
     User-Defined objects and then rerun DSNTIJEN from the start.
  .
     Any such data sets not changed to SMS management during the
     initial DB2 V10 migration process will be SMS-Managed the
     next time the associated table space is ReORGANIZED -- for
     example, by job DSNTIJEN if the table space is those
     modified during ENFM.
  .
  o  Content Manager logon getting CMBException SQLCODE= 725
     SQLSTATE=42721 SQLERRMC=CURRENT SCHEMA via Distributed JDBC
     driver.  Ensure eClient using data source with UPPER CASE
     NAME and the WAS Connection Pooling is disabled.
  .
  .
  .
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

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