Results 1 to 5 of 5
  1. #1
    Join Date
    Sep 2009
    Posts
    66

    Unanswered: how to understand error

    How to understand error:

    FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
    DATA #1 : String, 146 bytes
    LOADID: 12752.2009-09-29-04.11.39.987815.5 (12;14)
    Failed to lock table and fix TCB , -2147221458, (nil), Detected in
    file:sqluTarget.C, Line:2966

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    You can use "db2diag -rc -2147221458"

  3. #3
    Join Date
    Sep 2009
    Posts
    66
    okay. I do not understand why put this information in db2diag.log. How DBA knows about fix TCB and -2147221458, (nil), Detected in file:sqluTarget.C, Line:2966. No useful for me.

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by L_DBA_L
    okay. I do not understand why put this information in db2diag.log. How DBA knows about fix TCB and -2147221458, (nil), Detected in file:sqluTarget.C, Line:2966. No useful for me.
    db2 support needs this information in order to debug problems

  5. #5
    Join Date
    Nov 2005
    Location
    IL
    Posts
    557
    Quote Originally Posted by L_DBA_L
    okay. I do not understand why put this information in db2diag.log. How DBA knows about fix TCB and -2147221458, (nil), Detected in file:sqluTarget.C, Line:2966. No useful for me.
    Where do you suggest db2 logs this information?

    Using Bella's suggestion earlier I was able to decipher what the error was on my side with out calling to Mother Ship.
    --
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows

    DB2 v9.7.0.6 os 6.1.0.0

Posting Permissions

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