LI71427: INSTANCE CRASH POSSIBLE DURING OFFLINE BACKUP OF QUIESCED DATABASE, IF CONNECT ATTEMPT FAILS WITH -20157

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• An instance crash may occur during hte start of an offline
  backup with the following entry in the db2diag.log :
  
  
  FUNCTION: DB2 UDB, SQO Latch Tracing, SQLO_SLATCH_UNIX::
  releaseConflict, probe:666
  MESSAGE :
  ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD
            "expected latch to be held."
  
  This can happen if the database had been quiesced before
  deactivating and there is another session that does not have the
  quiesce connect privilege trying to connect at the same time (
  resulting in error -20157 )
  
  This is a timing problem and will not happen every time.
  

Local fix

• avoid connection attempts leading to -20157 error
  

Problem summary

• problem summary : potential crash during offline backup
  users affected : users running offline backup whilst failed
  connection attempts are made
  problem conclusion : this apar avoids the possibility of this
  crash
  

Problem conclusion

• The problem was first fixed in db2 udb version v8.2 fixpak 16
  

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:

  IZ01847

Fix information

• Fixed component name

  DB2UDB ESE LINU

• Fixed component ID

  5765F4105

Applicable component levels

• R820 PSY

     UP