Results 1 to 2 of 2
  1. #1
    Join Date
    Jun 2017

    Unanswered: 1 out of 3 Transactions in DB2 fail with SQL 998, State 58005, error code 8, sub code

    We have a few back-end applications using an XA switch module connected to a DB2 (10.5).
    2 or 3 transactions will pass until this shows up:
    SQL Error XXXXXX CODE=-000000998 STATE=58005 9?2

    I’ve found this document that talks about “Code 998, state 58005, reason code 9, subcode 2:
    Unfortunately, all they say is: For reason code 9, subcode 02, ensure that the tp_mon_name configuration parameter contains the name of the dynamic library in the external product which has the ax_reg() function used for dynamic registration of transactions.

    1. On the other hand, I found this document:
    Where, on the explanation of tm_database, they say "don't use tp_mon_name, if you are using XA switch module, which I am.
    But they don't explain tm_database.

    2. I have two versions of the switch module, one with 'CONSTANT DYNAMICREGISTRATION "Y"' and one with 'CONSTANT DYNAMICREGISTRATION "N"'. The latter exists somewhere and will take me huge time to find. Do you think it could be it?


  2. #2
    Join Date
    Apr 2012
    Provided Answers: 27
    Which fixpack of DB2 V10.5 is running?
    In the XA setup, which product is acting as the TM, which which is the other RM?
    You need to check the db2diag to see the prior messages, and also check the diagnostics of the other RM - it's unclear from your description which RM suffered the error that caused the -998 and what was that error exactly.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts