Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2014
    Posts
    5

    Red face Unanswered: DB2 HADR not working after migration from V9.1 to V10.1 (via V9.7)

    Dear All,

    I migrated my db from V9.1 to V9.7 then V10.1 after applying latest fixpacks.
    HADR works fine at V9.7 but once migrated to V10.1 it has stopped working and the status i am getting "HADR_STATE = REMOTE_CATCHUP_PENDING"

    PRIMARY db2diag.log says:

    2014-05-25-21.36.30.027000+330 I75701H690 LEVEL: Error
    PID : 6356 TID : 7020 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 7020 EDUNAME: db2lfr.0 (EREMIT) 0
    FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:25
    MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
    DIA8411C A file "" could not be found.
    DATA #1 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes
    LFR Scan Num = 127
    LFR Scan Caller's EDUID = 1344
    DATA #2 : String, 25 bytes
    Problem opening log file:
    DATA #3 : String, 12 bytes
    S0002172.LOG

    2014-05-25-21.36.30.028000+330 I76393H601 LEVEL: Error
    PID : 6356 TID : 7020 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 7020 EDUNAME: db2lfr.0 (EREMIT) 0
    FUNCTION: DB2 UDB, recovery manager, sqlplfrSearchOnDiskForLsoMapping, probe:4180
    MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
    DIA8411C A file "" could not be found.
    DATA #1 : <preformatted>
    LFR Scan Num = 127
    LFR Scan Caller's EDUID = 1344
    Extent open failure 2172

    2014-05-25-21.36.30.028000+330 I76996H634 LEVEL: Error
    PID : 6356 TID : 7020 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 7020 EDUNAME: db2lfr.0 (EREMIT) 0
    FUNCTION: DB2 UDB, recovery manager, sqlplfrExtentFromLSO, probe:4185
    MESSAGE : ZRC=0x86100026=-2045771738=SQLPR_MISSING_LOG_EXT
    "Used by various operations reading the logs to indicate a missing log extent."
    DATA #1 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes
    LFR Scan Num = 127
    LFR Scan Caller's EDUID = 1344

    2014-05-25-21.36.30.029000+330 I77632H639 LEVEL: Error
    PID : 6356 TID : 1344 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 1344 EDUNAME: db2hadrp.0.1 (EREMIT) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduP, probe:20591
    MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
    DIA8411C A file "" could not be found.
    DATA #1 : <preformatted>
    HADR primary database failed to read log pages for remote catchup. sqlplfrScanNext scanPages = 0, scanFlagsOut = 0x2

    2014-05-25-21.36.30.029000+330 E78273H468 LEVEL: Event
    PID : 6356 TID : 1344 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 1344 EDUNAME: db2hadrp.0.1 (EREMIT) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetHdrState, probe:10000
    CHANGE : HADR state set to HDR_P_REM_CATCHUP_PENDING (was HDR_P_REM_CATCHUP), connId=127

    ================================================== =======

    STANDBY db2diag says:

    2014-05-25-21.51.31.395000+330 E84581H458 LEVEL: Error
    PID : 6964 TID : 4784 PROC : db2syscs.exe
    INSTANCE: DB2_01 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 4784 EDUNAME: db2hadrs.0.0 (EREMIT) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduS, probe:21580
    MESSAGE : ADM12509E HADR encountered an abnormal condition. Reason code: "1"

    2014-05-25-21.51.31.397000+330 I85041H604 LEVEL: Warning
    PID : 6964 TID : 4784 PROC : db2syscs.exe
    INSTANCE: DB2_01 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 4784 EDUNAME: db2hadrs.0.0 (EREMIT) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduS, probe:21580
    MESSAGE : ZRC=0x87800148=-2021654200=HDR_ZRC_BAD_LOG
    "HADR standby found bad log"
    DATA #1 : String, 99 bytes
    HADR standby error handling: will close connection to primary, then reconnect, and perform a retry.

    2014-05-25-21.51.31.398000+330 E85647H468 LEVEL: Event
    PID : 6964 TID : 4784 PROC : db2syscs.exe
    INSTANCE: DB2_01 NODE : 000 DB : EREMIT
    HOSTNAME: MGTECH27
    EDUID : 4784 EDUNAME: db2hadrs.0.0 (EREMIT) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetHdrState, probe:10000
    CHANGE : HADR state set to HDR_S_REM_CATCHUP_PENDING (was HDR_S_REM_CATCHUP), connId=156

    ================================================== ======

    I took offline back up from primary after stopping HADR service and restored it on Standby and did HADR configuration. Once i give the command: hadrpd -db dbname -hadr it goes from remote catchup to remote catchup pending.

    please help.......

    Thanks.

  2. #2
    Join Date
    Dec 2007
    Location
    Richmond, VA
    Posts
    1,328
    Provided Answers: 5
    seems you may be missing a log file? also, shouldn't the command
    hadrpd -db dbname -hadr
    be:
    Code:
    db2pd -db dbname -hadr
    Dave

  3. #3
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Hi,

    where is the S0002172.LOG log file on PRIMARY?
    Regards,
    Mark.

Posting Permissions

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