IC79283: TPC UNABLE TO COMMIT/ROLLBACK DB UPDATES RESULTING IN JOB DEFINITIONS NOT SAVING AND JOBS NOT RUNNING.

APAR status

• Closed as user error.

Error description

• Users unable to save new job definitions or changes to existing
  jobs due to an inaccessible TPCDB database; pop-up message shows
  SRV0081E referencing SQLSTATE 57011, vendor error code -964.
  TPC is unable to perform many database operations including
  quering the T_SCHEDULE table to run jobs that have already been
  defined.
  To identify this issue, examine the db2diag.log file, matching
  the timestamp of the TPC error messages mentioned previously.
  Entries such as the following will appear:
  20xx-MM-DD-HH.MM.SS.651000+180 E83572428F603      LEVEL: Error
  PID     : 3980                 TID  : 7736        PROC :
  db2syscs.exe
  INSTANCE: DB2                  NODE : 000         DB   : TPCDB
  APPHDL  : 0-563                APPID:
  <IP_ADDR>.52684.110914115656
  AUTHID  : DB2ADMIN
  EDUID   : 7736                 EDUNAME: db2agent (TPCDB) 0
  FUNCTION: DB2 UDB, data protection services, sqlpgResSpace,
  probe:2860
  MESSAGE : ADM1823E  The active log is full and is held by
  application handle
            "4698..".  Terminate this application by COMMIT,
  ROLLBACK or FORCE
            APPLICATION
  Database deadlock messages such as the following will aslo be
  seen in db2diag.log:
  20xx-MM-DD-HH.MM.021000+180 E226864806F919     LEVEL: Warning
  PID     : 3468                 TID  : 8164        PROC :
  db2syscs.exe
  INSTANCE: DB2                  NODE : 000         DB   : TPCDB
  APPHDL  : 0-800                APPID:
  127.0.0.1.37884.110921001123
  AUTHID  : DB2ADMIN
  EDUID   : 8164                 EDUNAME: db2agent (TPCDB1) 0
  FUNCTION: DB2 UDB, database monitor,
  sqmLockEvents::collectLockEvent, probe:267
  MESSAGE : ADM5506I  "Deadlock" event has occurred on lock
            "03005700000000000000000054" at timestamp
            "2011-09-21-03.11.22.884711" with event ID "4". The
  affected
            application is named "DVSProcess Processor", and is
  associated with
            the workload name "SYSDEFAULTUSERWORKLOAD" and
  application ID
            "127.0.0.1.37884.110921001123" at member "0". The role
  that this
            application plays with respect to this lock is:
  "Victim".
  20xx-MM-DD-HH.MM.084000+180 I226874966F813     LEVEL: Error
  PID     : 3468                 TID  : 4460        PROC :
  db2syscs.exe
  INSTANCE: DB2                  NODE : 000         DB   : TPCDB
  APPHDL  : 0-26                 APPID: *LOCAL.DB2.110920231649
  AUTHID  : XPAASTLAR_
  EDUID   : 4460                 EDUNAME: db2evmgi
  (DB2DETAILDEADLOCK) 0
  FUNCTION: DB2 UDB, database monitor,
  sqmEvmonWriter::evmonWriter, probe:130
  MESSAGE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor
  full of data"
            DIA8052C The Event Monitor "" has reached its file
  capacity. Delete
            the files in the target directory "" or move them to
  another
            directory.
     DATA #1 : String, 17 bytes
     DB2DETAILDEADLOCK
     DATA #2 : String, 51 bytes
     E:\DB2\NODE0000\SQL00002\DB2EVENT\db2detaildeadlock.
  RECREATE STEPS:  Attempt to save new TPC jobs (performance
  monitors, probes, etc) on a TPC server at the affected release
  

Local fix

• None known
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This was caused by DB2 parameter settings that led to
  transaction locks and other DB2 issues.  The DB2 settings
  specified in the TPC Hints and Tips document were
  accidentally applied to the wrong database (not the one TPC
  was using).
  http://www-01.ibm.com/support/docview.wss?uid=swg27008254
  
  The problem was resolved when the DB2 parameter settings from
  the TPC Hints and Tips document were reviewed again and
  applied to the correct TPC database.
  

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