db2 备库经常挂掉？

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

背景：目前是主备模式，采用NEARSYNC模式，经常自动挂掉
在备库重启hadr：db2 start hadr on db lanmao as Standby 又变正常

报错内容：

2019-06-24-18.30.32.967772+480 I4469754584E1016 LEVEL: Error
PID : 8834 TID : 140368381208320 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2682 EDUNAME: db2redom (LM) 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
000000733D2F870C
DATA #5 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
000000734FE5E3AE
DATA #6 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
FFFFFFFFFFFFFFFF
DATA #7 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
00000073501D4B8D

2019-06-24-18.30.32.967911+480 I4469755601E181 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_DBCB
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.968234+480 I4469755783E193 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.969300+480 I4469755977E193 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.970289+480 I4469756171E193 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.971270+480 I4469756365E193 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.972199+480 I4469756559E193 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.973165+480 I4469756753E193 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.974115+480 I4469756947E193 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.32.975080+480 I4469757141E181 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLP_LFPB
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.33.000732+480 I4469757323E182 LEVEL: Error
PID:8834 TID:140368381208320 NODE:000 Title: SQLPR_PRCB
Dump File:/home/db2inst1/sqllib/db2dump/8834.2682.000.dump.bin

2019-06-24-18.30.40.783188+480 I4469757506E558 LEVEL: Error
PID : 8834 TID : 140364170127104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2453 EDUNAME: db2agent (LM) 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.

2019-06-24-18.30.40.783393+480 I4469758065E597 LEVEL: Error
PID : 8834 TID : 140364170127104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2453 EDUNAME: db2agent (LM) 0
FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:1230
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"

      DIA8526C A fatal error occurred in data protection services.

DATA #1 : unsigned integer, 2 bytes
1

2019-06-24-18.30.40.792125+480 I4469758663E1041 LEVEL: Severe
PID : 8834 TID : 140364170127104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2453 EDUNAME: db2agent (LM) 0
FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster, probe:2500
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"

      DIA8526C A fatal error occurred in data protection services.

DATA #1 : String, 37 bytes
Replay master fatal error: localSqlca
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1042 sqlerrml: 0
sqlerrmc:
sqlerrp : sqlpRepl
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000

       (4) 0x00000000      (5) 0x00000000      (6) 0x00000000

sqlwarn : (1) (2) (3) (4) (5) (6)

       (7)      (8)      (9)      (10)        (11)

sqlstate:

2019-06-24-18.30.40.793171+480 I4469759705E650 LEVEL: Severe
PID : 8834 TID : 140364170127104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2453 EDUNAME: db2agent (LM) 0
FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster, probe:2500
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"

      DIA8526C A fatal error occurred in data protection services.

DATA #1 : <preformatted>
Fatal error during HADR replay. Forcing the database to shut down.

2019-06-24-18.30.40.798402+480 I4469760356E1320 LEVEL: Info
PID : 8834 TID : 140364170127104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2453 EDUNAME: db2agent (LM) 0
FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::ForceDBShutdown, probe:13769
MESSAGE : Regular agent EDU doing ForceDBShutdown. Force DB shutdown agent ID

      is:

DATA #1 : APPHDL, PD_TYPE_SQLZ_APPHDL, 4 bytes
0-23039
DATA #2 : sqeApplication_acbInfo, PD_TYPE_sqeApplication_acbInfo, 4 bytes
x0
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0x00007FBCBD5B1269 pdLog + 0x3B9
[1] 0x00007FBCBF14C77E _ZN16sqeLocalDatabase15ForceDBShutdownEi + 0x2BE
[2] 0x00007FBCBFBB4FA0 _Z16sqlpReplayMasterP8sqeAgent + 0x940
[3] 0x00007FBCBD8A014C _Z26sqleIndCoordProcessRequestP8sqeAgent + 0x41C
[4] 0x00007FBCBD8B25F8 _ZN8sqeAgent6RunEDUEv + 0x2B8
[5] 0x00007FBCBE94DF63 _ZN9sqzEDUObj9EDUDriverEv + 0xF3
[6] 0x00007FBCBE94DE69 _Z10sqlzRunEDUPcj + 0x9
[7] 0x00007FBCBE3B5071 sqloEDUEntry + 0x2A1
[8] 0x00007FBCC3DF8806 /lib64/libpthread.so.0 + 0x7806
[9] 0x00007FBCBB4DE64D clone + 0x6D

2019-06-24-18.30.40.851671+480 I4469761677E1364 LEVEL: Severe
PID : 8834 TID : 140364170127104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2453 EDUNAME: db2agent (LM) 0
FUNCTION: DB2 UDB, data protection services, SQLP_DBCB::setLogState, probe:5000
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"

      DIA8414C Logging can not continue due to an error.

CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0x00007FBCBD5B1269 pdLog + 0x3B9
[1] 0x00007FBCBE3D24E8 _ZN9SQLP_DBCB11setLogStateEim + 0x48
[2] 0x00007FBCBFC3C51C _Z18sqlpSetLogStateBadP16sqeLocalDatabase + 0x2C
[3] 0x00007FBCBF14C830 _ZN16sqeLocalDatabase15ForceDBShutdownEi + 0x370
[4] 0x00007FBCBFBB4FA0 _Z16sqlpReplayMasterP8sqeAgent + 0x940
[5] 0x00007FBCBD8A014C _Z26sqleIndCoordProcessRequestP8sqeAgent + 0x41C
[6] 0x00007FBCBD8B25F8 _ZN8sqeAgent6RunEDUEv + 0x2B8
[7] 0x00007FBCBE94DF63 _ZN9sqzEDUObj9EDUDriverEv + 0xF3
[8] 0x00007FBCBE94DE69 _Z10sqlzRunEDUPcj + 0x9
[9] 0x00007FBCBE3B5071 sqloEDUEntry + 0x2A1
[10] 0x00007FBCC3DF8806 /lib64/libpthread.so.0 + 0x7806
[11] 0x00007FBCBB4DE64D clone + 0x6D

2019-06-24-18.30.40.863114+480 E4469763042E988 LEVEL: Critical
PID : 8834 TID : 140364170127104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : LM
APPHDL : 0-23039 APPID: *LOCAL.DB2.190715144851
HOSTNAME: xm_cunguan_db_02
EDUID : 2453 EDUNAME: db2agent (LM) 0
FUNCTION: DB2 UDB, base sys utilities, sqleDoForceDBShutdownFODC, probe:10
MESSAGE : ADM14001C An unexpected and critical error has occurred:

      "ForceDBShutdown". The instance may have been shutdown as a result.
      "Automatic" FODC (First Occurrence Data Capture) has been invoked and
      diagnostic information has been recorded in directory
      "/home/db2inst1/sqllib/db2dump/FODC_ForceDBShutdown_2019-06-24-18.30.
      40.857146_0000/". Please look in this directory for detailed evidence
      about what happened and contact IBM support if necessary to diagnose
      the problem.