Results 1 to 5 of 5
  1. #1
    Join Date
    Jan 2010
    Posts
    207

    Unanswered: Reporting -1475; old SQLCA: ...

    Hello there,

    I get the following error log in my db2diag:

    2011-04-07-15.20.00.058402+120 I270633A1213 LEVEL: Error
    PID : 1634452 TID : 12595 PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : Database
    APPHDL : 0-201 APPID: 10.21.12.252.4402.110407132004
    AUTHID : DB2INST1
    EDUID : 12595 EDUNAME: db2agent (Database) 0
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
    MESSAGE : Reporting -1476; old SQLCA:
    DATA #1 : Hexdump, 136 bytes
    0x0780000000F97BA8 : 5351 4C43 4120 2020 0000 0088 FFFF FE63 SQLCA .......c
    0x0780000000F97BB8 : 0000 2020 2020 2020 2020 2020 2020 2020 ..
    0x0780000000F97BC8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x0780000000F97BD8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x0780000000F97BE8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x0780000000F97BF8 : 2020 2020 2020 2020 5351 4C52 4931 3641 SQLRI16A
    0x0780000000F97C08 : 8016 0008 0000 0008 0000 0000 0000 0000 ................
    0x0780000000F97C18 : FFFF FFF6 0000 0000 2020 2020 2020 2020 ........
    0x0780000000F97C28 : 2020 2020 2020 2020
    And that error comes again and again with a break of 10 min ... Does anyone know what i can do to fix this? Thanks in advance.

    DB_N00B

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    This is a secondary message, indicating that a transaction was rolled back because of another error. You'll need to look at earlier entries in the log to find out what was the root cause.

  3. #3
    Join Date
    Jan 2010
    Posts
    207
    Hello there,

    First of all thank you for your reply. As you mentioned, i should take a look into my db2diag file and I found this as the first up coming error message.


    2011-04-07-11.02.37.893897+120 E18139A765 LEVEL: Error
    PID : 1171522 TID : 13109 PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : Database
    APPHDL : 0-34199 APPID: 222.213.126.133.31232.54252050052
    AUTHID : METASUIT
    EDUID : 13109 EDUNAME: db2agent (Database) 0
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:10
    MESSAGE : ADM14005E The following error occurred: "AppErr". First Occurrence
    Data Capture (FODC) has been invoked in the following mode:
    "Automatic". Diagnostic information has been recorded in the
    directory named
    "/var/log/db2logs/db2inst1/FODC_AppErr_2011-04-07-11.02.37.854319_117
    1522_13109_000/".

    2011-04-07-11.02.37.894270+120 E18905A551 LEVEL: Severe
    PID : 1171522 TID : 13109 PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : Database
    APPHDL : 0-34199 APPID: 222.213.126.133.31232.54252050052
    AUTHID : METASUIT
    EDUID : 13109 EDUNAME: db2agent (Database) 0
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:200
    MESSAGE : ADM0001C A severe error has occurred. Examine the administration
    notification log and contact IBM Support if necessary.

    What should I do now? A new activation of the database didnt help!

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    MESSAGE : Reporting -1476; old SQLCA:
    DATA #1 : Hexdump, 136 bytes
    0x0780000000F97BA8 : 5351 4C43 4120 2020 0000 0088 FFFF FE63 SQLCA .......c


    FFFF FE63 -> SQL0413N

    Use "db2diag -rc fffffe63"

  5. #5
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by DB_N00b View Post
    What should I do now?
    Examine the administration notification log and contact IBM Support if necessary.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

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