Results 1 to 3 of 3
  1. #1
    Join Date
    Jul 2006
    Location
    Pune , India
    Posts
    433

    Unanswered: Replication : db2LogRead error

    capture service during replication is going down giving following errors
    and i am not able to restrart the service again. I have observed this error many times on our systems but cant find solution fot it.
    anyone has any clue..... this has really frustated me


    Capture log:

    2007-02-06-15.31.13.968000 <logrd8::readTheLog> ASN8041D "Capture" : "ASN" : "WorkerThread" : db2LogRead API is sending us backwards in theDB2 Log: First LSN is "0000:0000:002e:b91f:dffa" while Next Start LSN is "0000:0000:0000:0000:0000"
    2007-02-06-15.31.13.968000 <logrd::readTheLog> ASN0005E CAPTURE "ASN" : "WorkerThread". The Capture program encountered an error when reading the DB2 log. The log sequence number is "0000:0000:002E:B91FFFA", the SQLCODE is "-2038", and the reason code is "".
    2007-02-06-15.31.13.968000 <logrd::readTheLog> ASN8999D "Capture" : "ASN" : "WorkerThread" :
    2007-02-06-15.31.13.968000 <CWorkerMain> ASN0589I "Capture" : "ASN" : "WorkerThread" The program received an unexpected return code "910" from routine "logtxrdr::getTrans".
    2007-02-06-15.31.13.968000 <CWorkerMain> ASN0123I CAPTURE "ASN" : "WorkerThread". At program termination, the highest log sequence number of a successfully captured log record is "4641:E002:0005:CA17:0000" and the lowest log sequence number of a record still to be committed is "0000:0000:002E:B90B:80CE".
    2007-02-06-15.31.15.406000 <asnThread::stop> ASN0590I "Capture" : "ASN" : "Initial" The thread "Initial" received return code "910" from the exiting thread "WorkerThread".
    2007-02-06-15.31.17.421000 <asnThread::stop> ASN0590I "Capture" : "ASN" : "Initial" The thread "Initial" received return code "2011" from the exiting thread "HoldLThread".
    2007-02-06-15.31.17.421000 <asnThread::stop> ASN0590I "Capture" : "ASN" : "Initial" The thread "Initial" received return code "2011" from the exiting thread "AdminThread".
    2007-02-06-15.31.17.421000 <asnThread::stop> ASN0590I "Capture" : "ASN" : "Initial" The thread "Initial" received return code "2011" from the exiting thread "PruneThread".
    2007-02-06-15.31.17.437000 <Asnenv:delEnvIpcQRcvHdl> ASN0595I "Capture" : "ASN" : "Initial" The program removed an IPC queue with keys "(Global\OSSEIPC48tempDB2.REP_SRC.ASN.CAP.IPC, Global\OSSEIPC49tempDB2.REP_SRC.ASN.CAP.IPC, Global\OSSEIPC50tempDB2.REP_SRC.ASN.C".
    2007-02-06-15.31.17.437000 <_asnCapture> ASN0008I CAPTURE "ASN" : "Initial". The Capture program was stopped.




    Db2diag logs :

    2007-02-06-15.31.13.953000+000 I19837H153 LEVEL: Error
    PID:3772 TID:3924 NODE:000 Title: SQLP_ALRCB
    Dump File:R:\DB2_DIAGNOSTICS\37723924.000

    2007-02-06-15.31.13.968000+000 I19992H153 LEVEL: Error
    PID:3772 TID:3924 NODE:000 Title: SQLP_ALRCB
    Dump File:R:\DB2_DIAGNOSTICS\37723924.000

    2007-02-06-15.31.13.968000+000 I20147H498 LEVEL: Error
    PID : 3772 TID : 3924 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : PERFDB03
    APPHDL : 0-702 APPID: *LOCAL.DB2.070213150105
    FUNCTION: DB2 UDB, data protection, sqlp_AsyncLogReadAPI, probe:120
    DATA #1 : String, 133 bytes
    Error: sqlcode -2038, rc -1961951232, hflag2LsnReuse 0
    action 1, startLSN 002E B91F DFFA, endLSN 002E B920 0F60, logBufferSize 204800
    Rahul Singh
    Certified DB2 9 DBA / Application Developer

  2. #2
    Join Date
    Feb 2016
    Posts
    1

    Facing the same error with IBM Infosphere CDC running on DB2 10.1

    Hello,

    We are facing the same log reader error on our environment with the replication software - IBM Infosphere CDC. Can you let me know on how this issue was resolved? Your thoughts on resolution would be greatly helpful for us.

    Thanks
    AJ

  3. #3
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Quote Originally Posted by AjayRk View Post
    Hello,

    We are facing the same log reader error on our environment with the replication software - IBM Infosphere CDC. Can you let me know on how this issue was resolved? Your thoughts on resolution would be greatly helpful for us.

    Thanks
    AJ
    Have you opened a PMR with IBM?
    If the 910 code is in the capture log file, look for SQL0910N in the Knowledge Centre for your version + fixpack + platform of DB2.

Posting Permissions

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