3322030 - DB6: Standby server shutdown after re-initializing

You have rebuilt standby server following KBA 3264518

Standby server gets shutdown shortly after it starts up.

In the database log (/db2/<SID>/db2dump/db2diag.log), you find following error messages:

2023-03-06-23.38.15.160991+000 I917087A490          LEVEL: Info
PID     : 5702368              TID : 40351          PROC : db2sysc 0
INSTANCE: db2abc               NODE : 000           DB   : abc
APPHDL  : 0-3810               APPID: *LOCAL.db2abc.230306233056
AUTHID  : DB2abc               HOSTNAME: abcde001
EDUID   : 40351                EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduStartup, probe:21152
MESSAGE : HADR Startup has completed.

2023-03-06-23.38.15.201113+000 I918485A460          LEVEL: Info
PID     : 5702368              TID : 44463          PROC : db2sysc 0
INSTANCE: db2abc               NODE : 000           DB   : abc
APPHDL  : 0-3815               APPID: *LOCAL.DB2.230306233815
HOSTNAME: abcde001
EDUID   : 44463                EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster, probe:300
DATA #1 : <preformatted>
Starting Replay Master on standby.

2023-03-06-23.38.35.449993+000 I953764A570          LEVEL: Info
PID     : 5702368              TID : 5880           PROC : db2sysc 0
INSTANCE: db2abc              NODE : 000           DB   : abc    
HOSTNAME: abcde001
EDUID   : 5880                 EDUNAME: db2logmgr (LNR) 0
FUNCTION: DB2 UDB, data protection services, sqpLogMgrEdu::sqlpgRetrieveLogFile, probe:4148
DATA #1 : <preformatted>
Completed retrieve for log file S0011330.LOG on chain 9 to /db2/LNR/log_archive2/db2lnr/LNR/NODE0000/LOGSTREAM0000/LOGSTREAM0000/.  The newly retrieved log will be verified.

2023-03-07-00.24.50.529219+000 I1100305A458         LEVEL: Info
PID     : 5702368              TID : 7165           PROC : db2sysc 0
INSTANCE: db2abc               NODE : 000           DB   : abc     
HOSTNAME: abcde001
EDUID   : 7165                 EDUNAME: db2logalloc.0 (abc) 0
FUNCTION: DB2 UDB, data protection services, sqlpLogAllocCandidatePool::removeExtraCandidates, probe:10100
DATA #1 : <preformatted>
Delete log extent 11330 from log stream 0.

2023-03-07-02.17.02.384536+000 I1166733A590         LEVEL: Error
PID     : 5702368              TID : 6908           PROC : db2sysc 0
INSTANCE: db2abc              NODE : 000           DB   : abc    
HOSTNAME: abcde001
EDUID   : 6908                 EDUNAME: db2lfr.0 (LNR) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrDoScanNext, probe:1100
MESSAGE : hit EOL for hadr
DATA #1 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes
LFR Scan Num            = 5
LFR Scan Caller's EDUID = 44670
DATA #2 : Hex integer, 8 bytes
0x0000000004031008
DATA #3 : unsigned integer, 4 bytes
2249129994

2023-03-07-02.17.02.776362+000 I1174575A1088        LEVEL: Info
PID     : 5702368              TID : 44463          PROC : db2sysc 0
INSTANCE: db2abc               NODE : 000           DB   : abc
APPHDL  : 0-3815               APPID: *LOCAL.DB2.230306233815
HOSTNAME: abcde001
EDUID   : 44463                EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster, probe:2460
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
          DIA8411C A file "" could not be found.
DATA #1 : String, 88 bytes
Replay master encoutered some error. Try to restart standby to handle recoverable error.
DATA #2 : unsigned integer, 8 bytes
0
DATA #3 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1042   sqlerrml: 0
 sqlerrmc: 
 sqlerrp : sqlpRepl

2023-03-07-02.17.02.778304+000 I1176143A479         LEVEL: Info
PID     : 5702368              TID : 41893          PROC : db2sysc 0
INSTANCE: db2abc               NODE : 000           DB   : abc
APPHDL  : 0-4111               APPID: *LOCAL.DB2.230307021702
HOSTNAME: abcde001
EDUID   : 41893                EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetExplicitStarted, probe:125
MESSAGE : HADR turned database explicitly started OFF.

2023-03-07-02.17.02.779192+000 I1177103A477         LEVEL: Info
PID     : 5702368              TID : 44463          PROC : db2sysc 0
INSTANCE: db2abc               NODE : 000           DB   : abc
APPHDL  : 0-3815               APPID: *LOCAL.DB2.230306233815
HOSTNAME: abcde001
EDUID   : 44463                EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster, probe:9500
MESSAGE : Stopping replay master on standby
DATA #1 : Boolean, 1 bytes
true

2023-03-07-02.17.04.514512+000 I1178122A454         LEVEL: Info
PID     : 5702368              TID : 41893          PROC : db2sysc 0
INSTANCE: db2abc               NODE : 000           DB   : abc
APPHDL  : 0-4111               APPID: *LOCAL.DB2.230307021702
HOSTNAME: abcde001
EDUID   : 41893                EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduShutdown, probe:29001
MESSAGE : HADR Shutdown has begun.

• SAP on IBM Db2 for Linux, UNIX, and Windows
• Db2 version 11.5.6 and 11.5.7.    

Replay master, handle recoverable error, hdrSetExplicitStarted, hit EOL for hadr , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem