db2数据库的备库经常hadr挂掉？

数据库版本:db2 10.1
操作系统版本:SUSE Linux Enterprise Server 11 SP4 (x86_64)

目前架构是一主一备，通过hadr进行同步数据，同步模式为Near synchronous，每过一段时间备库的hadr就会挂掉，导致备库不可用，

Some log stream(s) have reached the maximum number of log files
that can be opened during recovery threshold.

没有太明白这是什么意思，这个对应的是哪个参数。求各位大佬解答

下面为备库宕机时刻的一些信息

PID : 8269 TID : 140110095968000 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LANMAO
APPHDL : 0-278 APPID: *LOCAL.DB2.190319070349
HOSTNAME: xm_cunguan_db_01
EDUID : 1343 EDUNAME: db2redom (LANMAO) 0
FUNCTION: DB2 UDB, recovery manager, sqlprProcessMaxLogFilesOpenInRecoveryThreshold, probe:7876
DATA #1 : String, 109 bytes
Some log stream(s) have reached the maximum number of log files
that can be opened during recovery threshold.
DATA #2 : Global Truncation Array, PD_TYPE_SQLP_GTA, 728 bytes
idx Lfs Lsn ChainTime Signature
0 0 0000000000000000 1450929329 1724432007

2019-03-20-15.46.27.979973+480 I1527790755E442 LEVEL: Info
PID : 8269 TID : 140110167271168 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LANMAO
HOSTNAME: xm_cunguan_db_01
EDUID : 1326 EDUNAME: db2hadrs.0.0 (LANMAO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk, probe:10370
DATA #1 : <preformatted>
WritePong set. Calling hdrSOpenLogFileForWrite

2019-03-20-15.46.28.488019+480 I1527791198E1424 LEVEL: Info
PID : 8269 TID : 140110095968000 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LANMAO
APPHDL : 0-278 APPID: *LOCAL.DB2.190319070349
HOSTNAME: xm_cunguan_db_01
EDUID : 1343 EDUNAME: db2redom (LANMAO) 0
FUNCTION: DB2 UDB, recovery manager, sqlprProcessMaxLogFilesOpenInRecoveryThreshold, probe:6876
DATA #1 : <preformatted>
Some log stream(s) have reached the maximum number of log files
that can be opened during recovery threshold.

   recoveryStartingLFSLSN: 0/0000000000000000
                  nextLso: 82574974775932
                  nextLsn: 00000069AB1CD262
             minPseudoLsn: FFFFFFFFFFFFFFFF
     LastFullRecLfsLsnLso: 33663472403/00000069AB1CD261/82574974775931
      LastRecLfsLsnLsoLFH: 33663472403/00000069AB1CD261/82574974775931

2019-03-20-15.46.28.488133+480 I1527792623E780 LEVEL: Info
PID : 8269 TID : 140110095968000 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LANMAO
APPHDL : 0-278 APPID: *LOCAL.DB2.190319070349
HOSTNAME: xm_cunguan_db_01
EDUID : 1343 EDUNAME: db2redom (LANMAO) 0
FUNCTION: DB2 UDB, recovery manager, sqlprProcessMaxLogFilesOpenInRecoveryThreshold, probe:7876
DATA #1 : String, 109 bytes
Some log stream(s) have reached the maximum number of log files
that can be opened during recovery threshold.
DATA #2 : Global Truncation Array, PD_TYPE_SQLP_GTA, 728 bytes
idx Lfs Lsn ChainTime Signature
0 0 0000000000000000 1450929329 1724432007

2019-03-20-15.46.28.488492+480 I1527793404E1016 LEVEL: Error
PID : 8269 TID : 140110095968000 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LANMAO
APPHDL : 0-278 APPID: *LOCAL.DB2.190319070349
HOSTNAME: xm_cunguan_db_01
EDUID : 1343 EDUNAME: db2redom (LANMAO) 0
FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:1434
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"

      DIA8526C A fatal error occurred in data protection services.

DATA #1 : String, 14 bytes
Too many logs.
DATA #2 : String, 64 bytes
logStreamId / lowtranlsn / minbufflsn / minPseudoLsn / recordLsn
DATA #3 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes
0
DATA #4 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
00000069982E4C67
DATA #5 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
00000069AAA30200
DATA #6 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
FFFFFFFFFFFFFFFF
DATA #7 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
00000069AB1CD262

2019-03-20-15.46.28.488671+480 I1527794421E181 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_DBCB
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.488866+480 I1527794603E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.489966+480 I1527794797E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.491004+480 I1527794991E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.492066+480 I1527795185E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.493148+480 I1527795379E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.494298+480 I1527795573E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.495192+480 I1527795767E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.496307+480 I1527795961E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.497305+480 I1527796155E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.498360+480 I1527796349E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.499284+480 I1527796543E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.500538+480 I1527796737E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.501583+480 I1527796931E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.502612+480 I1527797125E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.503646+480 I1527797319E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.504885+480 I1527797513E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.506301+480 I1527797707E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.507394+480 I1527797901E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.508495+480 I1527798095E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.509554+480 I1527798289E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.510509+480 I1527798483E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.511368+480 I1527798677E193 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.512368+480 I1527798871E181 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLP_LFPB
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.536152+480 I1527799053E182 LEVEL: Error
PID:8269 TID:140110095968000 NODE:000 Title: SQLPR_PRCB
Dump File:/home/db2inst1/sqllib/db2dump/8269.1343.000.dump.bin

2019-03-20-15.46.28.763718+480 I1527799236E558 LEVEL: Error
PID : 8269 TID : 140155411228416 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LANMAO
APPHDL : 0-278 APPID: *LOCAL.DB2.190319070349
HOSTNAME: xm_cunguan_db_01
EDUID : 36 EDUNAME: db2agent (LANMAO) 0
FUNCTION: DB2 UDB, recovery manager, sqlprDoForwardPhase, probe:330
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"

      DIA8526C A fatal error occurred in data protection services.