注册登录
提 问
English中文版
金融其它数据同步suse LinuxHADRdb2 10.1Db2数据库同步

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

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

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

x4gazc193v

x4gazc193v

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.
关注3
评论
参与11

3同行回答
|
按赞同排序
按时间排序

jtnijtni数据库运维工程师it
local fixreactivate the db on HADR standby在备库上重新激活下库显示全部

local fix
reactivate the db on HADR standby
在备库上重新激活下库

收起
IT咨询服务 · 2019-03-21
浏览3315
查看赞同的人
评论1
匿名用户匿名用户
可以打个补丁试试看。显示全部

可以打个补丁试试看。

收起
银行 · 2019-03-21
浏览2738
查看赞同的人
评论
long8501long8501数据库管理员瀚高软件
2019-03-20-15.46.28.765627+480 I1527802086E1318 LEVEL: InfoPID : 8269 TID : 140155411228416 PROC : db2sysc 0INSTANCE: db2inst1 NODE : 000 DB : LANMAOAPPHDL : 0-278 APPID: *LOCAL.DB2.19...显示全部

2019-03-20-15.46.28.765627+480 I1527802086E1318 LEVEL: Info
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, 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-278
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] 0x00007F7888050269 pdLog + 0x3B9
[1] 0x00007F7889BEB77E _ZN16sqeLocalDatabase15ForceDBShutdownEi + 0x2BE
[2] 0x00007F788A653FA0 _Z16sqlpReplayMasterP8sqeAgent + 0x940
[3] 0x00007F788833F14C _Z26sqleIndCoordProcessRequestP8sqeAgent + 0x41C
[4] 0x00007F78883515F8 _ZN8sqeAgent6RunEDUEv + 0x2B8
[5] 0x00007F78893ECF63 _ZN9sqzEDUObj9EDUDriverEv + 0xF3
[6] 0x00007F78893ECE69 _Z10sqlzRunEDUPcj + 0x9
[7] 0x00007F7888E54071 sqloEDUEntry + 0x2A1
[8] 0x00007F788E897806 /lib64/libpthread.so.0 + 0x7806
[9] 0x00007F7885F7D64D clone + 0x6D

2019-03-20-15.46.28.801130+480 I1527803405E1364 LEVEL: Severe
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, 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] 0x00007F7888050269 pdLog + 0x3B9
[1] 0x00007F7888E714E8 _ZN9SQLP_DBCB11setLogStateEim + 0x48
[2] 0x00007F788A6DB51C _Z18sqlpSetLogStateBadP16sqeLocalDatabase + 0x2C
[3] 0x00007F7889BEB830 _ZN16sqeLocalDatabase15ForceDBShutdownEi + 0x370
[4] 0x00007F788A653FA0 _Z16sqlpReplayMasterP8sqeAgent + 0x940
[5] 0x00007F788833F14C _Z26sqleIndCoordProcessRequestP8sqeAgent + 0x41C
[6] 0x00007F78883515F8 _ZN8sqeAgent6RunEDUEv + 0x2B8
[7] 0x00007F78893ECF63 _ZN9sqzEDUObj9EDUDriverEv + 0xF3
[8] 0x00007F78893ECE69 _Z10sqlzRunEDUPcj + 0x9
[9] 0x00007F7888E54071 sqloEDUEntry + 0x2A1
[10] 0x00007F788E897806 /lib64/libpthread.so.0 + 0x7806
[11] 0x00007F7885F7D64D clone + 0x6D

2019-03-20-15.46.28.832027+480 E1527804770E988 LEVEL: Critical
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, 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-03-20-15.46.
      28.815160_0000/". Please look in this directory for detailed evidence
      about what happened and contact IBM support if necessary to diagnose
      the problem.

2019-03-20-15.46.28.846492+480 E1527805759E569 LEVEL: Severe
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, base sys utilities, sqleDoForceDBShutdownFODC, probe:14034
MESSAGE : ADM7518C The database manager has shut down the following database

      because a severe error has occurred: "LANMAO  ".

2019-03-20-15.46.28.878454+480 I1527806329E498 LEVEL: Severe
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, Query Gateway, sqlqg_signal_handler, probe:10
MESSAGE : DIA0505I Execution of a component signal handling function has begun.

2019-03-20-15.46.28.878941+480 I1527806828E511 LEVEL: Severe
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, Query Gateway, sqlqg_signal_handler, probe:20
MESSAGE : DIA0506I Execution of a component signal handling function is

      complete.

2019-03-20-15.46.28.879677+480 I1527807340E504 LEVEL: Severe
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, relation data serv, sqlrr_signal_handler, probe:100
MESSAGE : DIA0505I Execution of a component signal handling function has begun.

2019-03-20-15.46.28.879750+480 I1527807845E641 LEVEL: Severe
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, relation data serv, sqlrr_signal_handler, probe:125
MESSAGE : MASTER TIME INFO
DATA #1 : Hexdump, 32 bytes
0x00007F75E502ADB8 : F793 905C 0000 0000 D701 0000 ED2F 0700 ...\........./..
0x00007F75E502ADC8 : ED2F 0700 F793 905C 0000 0000 0000 0000 ./.....\........

2019-03-20-15.46.28.879851+480 I1527808487E667 LEVEL: Severe
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, trace services, sqlt_logerr_data (secondary logging function), probe:50
MESSAGE : RDS UCINTFC: pCurrentPID->rdbname =
DATA #1 : Hexdump, 18 bytes
0x00007F786B132F78 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007F786B132F88 : 0000 ..

2019-03-20-15.46.28.879883+480 I1527809155E589 LEVEL: Severe
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, trace services, sqlt_logerr_data (secondary logging function), probe:50
MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
DATA #1 : Hexdump, 2 bytes
0x00007F786B132F48 : 0000 ..

2019-03-20-15.46.28.879911+480 I1527809745E609 LEVEL: Severe
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, trace services, sqlt_logerr_data (secondary logging function), probe:50
MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
DATA #1 : Hexdump, 0 bytes
Object not dumped: Address: 0x00007F786B132F8A Size: 0 Reason: Zero-length data

2019-03-20-15.46.28.879939+480 I1527810355E588 LEVEL: Severe
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, trace services, sqlt_logerr_data (secondary logging function), probe:50
MESSAGE : RDS UCINTFC: pCurrentPID->pkgnameLen =
DATA #1 : Hexdump, 2 bytes
0x00007F786B132F58 : 0000 ..

2019-03-20-15.46.28.879966+480 I1527810944E607 LEVEL: Severe
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, trace services, sqlt_logerr_data (secondary logging function), probe:50
MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.pkgname=
DATA #1 : Hexdump, 0 bytes
Object not dumped: Address: 0x00007F786B132F9C Size: 0 Reason: Zero-length data

收起
金融其它 · 2019-03-20
浏览3000
评论

提问者

long8501
long8501
数据库管理员瀚高软件
擅长领域： 新核心系统，两地三中心，前置系统
关注1
回答9
评论20

相关问题

  • PG数据库如何实现同城异地多活数据同步？
  • NEWSQL分布式数据库数据同步？
  • 容灾建设的架构、数据同步模式、建设范围如何选择？
  • 当数据量较大时，数据同步问题？
  • 能否介绍一下线路需求情况?数据同步带宽是怎么评估，机构接入怎么处理?

    • 问题状态

  • 发布时间：2019-03-20
  • 关注会员：3 人
  • 问题浏览：4399
  • 最近回答：2019-03-21

    • 关于TWT使用指南社区专家合作厂商入驻社区企业招聘投诉建议版权与免责声明联系我们
    © 2024talkwithtrend — talk with trend,talk with technologist京ICP备09031017号-30

    X社区推广