IC47523: AFTER DUMPDB, LOADDB FAILS WITH ANR0102E DLLOAD.C(2018): ERROR 10 INSERTING ROW IN TABLE "BACKUP.OBJECTS".

APAR status

• Closed as program error.

Error description

• Performed a dumpdb and the following errors were noted:
  ANR9999D dldump.c(3316): ThreadId<0> Logical page 681501 (lsn
  317299.192.2442,objName Backup.Objects) corrupted.
  ANR9999D dldump.c(3318): ThreadId<0> Key string packed column
  structure invalid for record 6.
  ANR4012W DUMPDB: Database page 681501 is damaged.
  ANR4011W DUMPDB: Database page 681501 is invalid - it will be
  skipped
  
  The dumpdb continued and completed with just the above error.
  But, during the loaddb, it encountered the following error
  and failed:
  ANR0102E dlload.c(2018): Error 10 inserting row in table
  "Backup.Objects".
  ANR1364I Input volume E:\FILECLASS\25522029.DMP closed.
  ANR9999D dlload.c(1379): ThreadId<24> Error 10 encountered
  during load processing.
  ANR4031I LOADDB: Copied 853841 database pages.
  ANR4033I LOADDB: Copied 1641 bit vectors.
  ANR4035I LOADDB: Encountered 1 bad database records.
  ANR4074I LOADDB: Encountered 0 bad database entries.
  ANR4036I LOADDB: Copied 26702413 database entries.
  ANR4037I LOADDB: 2472 Megabytes   copied.
  ANR9999D dlload.c(763): ThreadId<0> Missed 465 queued records
  for load.
  ANR4005E LOADDB: Database load process terminated due to
  error (100).
  ANR2106I : Quiescing database update activity.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TSM servers that perform either          *
  *                 DUMPDB/LOADFORMAT/LOADDB or                  *
  *                 UNLOADDB/LOADFORMAT/LOADDB where there       *
  *                 is damage to the database such that one      *
  *                 or more database records exceeds the         *
  *                 server database maximum record length.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level 5.2.7 and 5.3.3. Note that          *
  *                 this is subject to change at the             *
  *                 discretion of IBM.                           *
  ****************************************************************
  For a damaged TSM database, the UNLOADDB and DUMPDB
  processing may not identify damage to database records
  where the record exceeds the maximum allowable
  record length for the server.  Similarly, the LOADDB
  processing will fail to detect these damaged database
  records and may result in the LOADDB failing
  to complete due to a failure inserting the damaged record.
  
  This only occurs for those databases that are damaged and
  where the damage is such that a database record exceeds
  the maximum allowed database record length.
  

Problem conclusion

• The record length checking for both UNLOADDB/DUMPDB and
  LOADDB processing has been corrected to check for and
  exclude those records that exceed the maximum allowed
  record length.
  

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:

  PK13862 PK13864

Fix information

• Fixed component name

  TSM SERVER 510

• Fixed component ID

  5698ISMSV

Applicable component levels

• R52A PSY

     UP

• R52H PSY

     UP

• R52L PSY

     UP

• R52P PSY

     UP

• R52S PSY

     UP

• R52W PSY

     UP

• R53A PSY

     UP

• R53H PSY

     UP

• R53L PSY

     UP

• R53S PSY

     UP

• R53W PSY

     UP