在同一个server上建两个实例，不能同时启动
db2 部署在linux上，DB版本是： 10.5, Linux内存大约不到16G。
因为项目需要，想在一个server上建2个相同的db，让他们端口号不同，供两个开发环境使用。然后就在原有一个实例db2inst1的基础上又建了一个实例db2inst2, 端口不同。建好db2inst2恢复好数据库后发现两个实例不能同时启动，如果一同时启动两个实例就都会自动停掉，导致都不能用。看了db2diag.log, 相关的内容为：
2016-05-17-11.46.18.139121+480 I323409E384 LEVEL: Event
PID : 6086 TID : 139806840297280 PROC : db2start
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, sqleGetStStLockFile, probe:15083
MESSAGE : Obtained exclusive mode lock on the file:
DATA #1 : String, 39 bytes
/home/db2inst2/sqllib/ctrl/db2strst.lck
2016-05-17-11.46.18.177802+480 I323794E1655 LEVEL: Event
PID : 6086 TID : 139806840297280 PROC : db2start
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/db2inst2/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFF53705370 : 2F68 6F6D 652F 6462 3269 6E73 7432 2F73 /home/db2inst2/s
0x00007FFF53705380 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFF53705390 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFF537053A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF537053B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF537053C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF537053D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF537053E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF537053F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF53705400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF53705410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF53705420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF53705430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF53705440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF53705450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF53705460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
2016-05-17-11.46.18.617107+480 I325450E384 LEVEL: Event
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, sqleGetStStLockFile, probe:15083
MESSAGE : Obtained exclusive mode lock on the file:
DATA #1 : String, 39 bytes
MESSAGE : Obtained exclusive mode lock on the file:
DATA #1 : String, 39 bytes
/home/db2inst2/sqllib/ctrl/db2stst.0000
2016-05-17-11.46.19.044823+480 E325835E871 LEVEL: Warning
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
MESSAGE : ADM12007E There are "83" day(s) left in the evaluation period for
the product "DB2 Advanced Enterprise Server Edition". For evaluation
license terms and conditions, refer to the IBM License Acceptance and
License Information document located in the license directory in the
installation path of this product. If you have licensed this product,
ensure the license key is properly registered. You can register the
license using the db2licm command line utility. The license file can
be obtained from your licensed product CD.
2016-05-17-11.46.19.220038+480 E326707E259 LEVEL: Warning
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:0
2016-05-17-11.46.19.220306+480 E326967E871 LEVEL: Warning
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
MESSAGE : ADM12007E There are "83" day(s) left in the evaluation period for
the product "DB2 Advanced Enterprise Server Edition". For evaluation
license terms and conditions, refer to the IBM License Acceptance and
License Information document located in the license directory in the
installation path of this product. If you have licensed this product,
ensure the license key is properly registered. You can register the
license using the db2licm command line utility. The license file can
be obtained from your licensed product CD.
2016-05-17-11.46.19.220707+480 I327839E843 LEVEL: Warning
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
MESSAGE : SQL8007W There are "83" day(s) left in the evaluation period for the
product "DB2 Advanced Enterprise Server Edition". For evaluation
license terms and conditions, refer to the License Agreement document
located in the license directory in the installation path of this
product. If you have licensed this product, ensure the license key is
properly registered. You can register the license by using the
db2licm command line utility. The license key can be obtained from
your licensed product CD.
2016-05-17-11.46.20.551502+480 E328683E1564 LEVEL: Event
PID : 6096 TID : 139874128619264 PROC : db2syscr
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1
START : DB2 DBM
DATA #1 : Build Level, 232 bytes
Instance "db2inst2" uses "64" bits and DB2 code release "SQL10056"
with level identifier "0607010E".
Informational tokens are "DB2 v10.5.0.6", "s150731", "IP23643", Fix Pack "6".
DATA #2 : System Info, 664 bytes
System: Linux o2m02 10 3 x86_64
CPU: total:4 online:4 Cores per socket:4 Threading degree per core:1 SIMD:Y
CPU binding: not in use
Physical Memory(MB): total:14027 free:3991
Virtual Memory(MB): total:14027 free:3991
Swap Memory(MB): total:0 free:0
Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:28050
msgNumberOfHeaders:65536 msgMaxQueueSize:65536
msgMaxSegmentSize:16 shmMax:14708314112 shmMin:1 shmIDs:4096
shmSegments:4096 semMap:256000 semIDs:3584 semNum:256000
semUndo:256000 semNumPerID:250 semOps:32 semUndoSize:20
semMaxVal:32767 semAdjustOnExit:32767
Cur cpu time limit (seconds) = 0xFFFFFFFFFFFFFFFF
Cur file size limit (bytes) = 0xFFFFFFFFFFFFFFFF
Cur data size (bytes) = 0xFFFFFFFFFFFFFFFF
Cur stack size (bytes) = 0x0000000000800000
Cur core size (bytes) = 0x0000000000000000
Cur stack size (bytes) = 0x0000000000800000
Cur core size (bytes) = 0x0000000000000000
Cur memory size (bytes) = 0xFFFFFFFFFFFFFFFF
nofiles (descriptors) = 0x0000000000001000
Cur maximum number of processes = 0x0000000000001000
2016-05-17-11.46.20.894953+480 I330248E553 LEVEL: Event
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfBufferManager::initBufferManager, probe:10
START : Starting FCM Buffer Manager
1 resource group(s).
128 buffers allocated.
Maximum number of buffers supported is 8192.
Total buffer manager memory required for 1 logical and 0 fail-over partition(s) is 925704 bytes.
2016-05-17-11.46.20.896520+480 I330802E560 LEVEL: Event
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfChannelManager::initChannelManager, probe:10
START : Starting FCM Channel Manager
1 resource group(s).
128 channels allocated.
Maximum number of channels supported is 8192.
Total channel manager memory required for 1 logical and 0 fail-over partitions(s) is 512024 bytes.
2016-05-17-11.46.20.897535+480 I331363E559 LEVEL: Event
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfSessionManager::initSessionManager, probe:10
START : Starting FCM Session Manager
1 resource group(s).
128 sessions allocated.
Maximum number of sessions supported is 64000.
128 sessions allocated.
Maximum number of sessions supported is 64000.
Total session manager memory required for 1 logical and 0 fail-over partitions is 1957888 bytes.
2016-05-17-11.46.20.899566+480 I331923E440 LEVEL: Event
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqlkf_init_allocate_shared, probe:500
START : FCM infrastructure started
FCM running in non-shared mode; FCM parallelism degree: 1; comm protocol: TCP/IPv4
2016-05-17-11.46.20.911099+480 I332364E423 LEVEL: Info
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, Self tuning memory manager, stmmAttachToShmAtStartup, probe:1178
MESSAGE : Attached to STMM shared memory segment.
DATA #1 : Pointer, 8 bytes
0x00007ff3f2f43000
2016-05-17-11.46.20.954033+480 I332788E2571 LEVEL: Info
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, base sys utilities, sqleRollupCacheALInfo, probe:249
DATA #1 : String, 25 bytes
Rollup History at Startup
DATA #2 : sqeRollupALHistory, PD_TYPE_sqeRollupALHistory, 152 bytes
sqeRollupALHistory: Address:0x200839350, Size:x98, Size:152
x0088 m_activateNewRollupSetLatch {
state = 0x0000000000000000
= {
held X: 0
reserved for X: 0
shared holders: 0
firstSharIndex: 0x0
firstExclIndex: 0x0
6952,1 98%
firstSharIndex: 0x0
firstExclIndex: 0x0
}
starve X mode = true
xWaitCount = 0
requestCount = 0
identity = sqeRollupALHistory::m_activateNewRollupSetLatch (853)
}
x0080 m_activeRollupLevelSet 1
x0000 m_rollupLevelSets[0] SQLE_ROLLUP_LEVEL_SET: Address:0x200839350, Size:x20, Size:32
x0000 levelSetActivationTime 01/01/1970 08:00:00.000000
x0008 ceal
V:0 R:0 M:0 F:0 I:0 SB:0
x0010 cecl
V:0 R:0 M:0 F:0 I:0 SB:0
x0018 cesl
V:0 R:0 M:0 F:0 I:0 SB:0
x0020 m_rollupLevelSets[1] SQLE_ROLLUP_LEVEL_SET: Address:0x200839370, Size:x20, Size:32
x0000 levelSetActivationTime 05/17/2016 11:46:20.954013
x0008 ceal
V:10 R:5 M:0 F:6 I:0 SB:0
x0010 cecl
V:10 R:5 M:0 F:6 I:0 SB:0
x0018 cesl
V:0 R:0 M:0 F:0 I:0 SB:0
x0040 m_rollupLevelSets[2] SQLE_ROLLUP_LEVEL_SET: Address:0x200839390, Size:x20, Size:32
x0000 levelSetActivationTime 01/01/1970 08:00:00.000000
x0008 ceal
V:0 R:0 M:0 F:0 I:0 SB:0
x0010 cecl
V:0 R:0 M:0 F:0 I:0 SB:0
x0018 cesl
V:0 R:0 M:0 F:0 I:0 SB:0
x0060 m_rollupLevelSets[3] SQLE_ROLLUP_LEVEL_SET: Address:0x2008393b0, Size:x20, Size:32
x0000 levelSetActivationTime 01/01/1970 08:00:00.000000
x0008 ceal
V:0 R:0 M:0 F:0 I:0 SB:0
x0010 cecl
V:0 R:0 M:0 F:0 I:0 SB:0
x0018 cesl
6991,24 98%
V:0 R:0 M:0 F:0 I:0 SB:0
x0018 cesl
V:0 R:0 M:0 F:0 I:0 SB:0
2016-05-17-11.46.21.000329+480 I335360E396 LEVEL: Event
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfNodeManager::initNodeManager, probe:9
DATA #1 :
Is Cluster Manager enabled? true or false = 0
2016-05-17-11.46.21.129113+480 I335757E389 LEVEL: Event
PID : 6100 TID : 140685101491968 PROC : db2sysc 0
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, Columnar Data Engine, cdeStartup, probe:130
DATA #1 :
BLU: HW SIMD enabled: SCAN(Y), ARITH(Y), HASH(Y), CPU(0)
2016-05-17-11.46.22.547770+480 E336147E488 LEVEL: Event
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM ARCHITECTURE LEVEL: A05000600000000 CURRENT EFFECTIVE ARCHITECTURE LEVEL: A05000600000000 CODE LEVEL: A05000600000000 CURRENT EFFECTIVE CODE LEVEL: A05000600000000
2016-05-17-11.46.22.549256+480 I336636E375 LEVEL: Warning
PID : 6088 TID : 140172051654464 PROC : db2star2
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, sqleReleaseStStLockFile, probe:14796
MESSAGE : Released lock on the file:
DATA #1 : String, 39 bytes
/home/db2inst2/sqllib/ctrl/db2stst.0000
2016-05-17-11.46.22.577435+480 I337012E1263 LEVEL: Event
PID : 6086 TID : 139806840297280 PROC : db2start
7030,1 99%
2016-05-17-11.46.22.577435+480 I337012E1263 LEVEL: Event
PID : 6086 TID : 139806840297280 PROC : db2start
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:10813
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: 0 sqlerrml: 0
sqlerrmc:
sqlerrp : SQL10056
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:
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1063 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLEPFIN
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:
DATA #3 : Boolean, 1 bytes
false
DATA #4 : Boolean, 1 bytes
false
DATA #5 : Boolean, 1 bytes
false
DATA #6 : Boolean, 1 bytes
false
DATA #7 : Boolean, 1 bytes
false
2016-05-17-11.46.22.577936+480 I338276E375 LEVEL: Warning
PID : 6086 TID : 139806840297280 PROC : db2start
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, base sys utilities, sqleReleaseStStLockFile, probe:14796
MESSAGE : Released lock on the file:
DATA #1 : String, 39 bytes
7109,1 99%
MESSAGE : Released lock on the file:
DATA #1 : String, 39 bytes
/home/db2inst2/sqllib/ctrl/db2strst.lck
2016-05-17-11.48.14.212984+480 E338652E436 LEVEL: Error
PID : 6096 TID : 139874128619264 PROC : db2wdog 0 [db2inst2]
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 2 EDUNAME: db2wdog 0 [db2inst2]
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:7825
DATA #1 :
Beginning cleanup of Process id: 6112, OSS term code: 0x101, signal: 15
2016-05-17-11.48.14.213277+480 E339089E462 LEVEL: Error
PID : 6096 TID : 139874128619264 PROC : db2wdog 0 [db2inst2]
INSTANCE: db2inst2 NODE : 000
HOSTNAME: o2m02
EDUID : 2 EDUNAME: db2wdog 0 [db2inst2]
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:7977
DATA #1 :
A fenced vendor process crashed. Process id: 6112, OSS term code: 0x101, signal: 15, bringDown: 0
大家能帮忙分析下是什么原因吗？谢谢了！
附件：
db2support.zip (1.4 MB)
DB操作说明.txt (2.05 KB)
15同行回答
你在恢复数据库的时候有没有指定新的数据库目录？
从报错：OSS term code: 0x101, signal: 15
系统信号signal 15（ENOTBLK） 表明可能把普通文件挂载成块文件。另外请提供详细的db2support文件db2support -d -c -s
收起然后今天又试了下，在一个实例下装2个db，还是不能同时启动，诊断日志Error部分信息是：
2016-05-18-16.24.18.123188+480 E1759965E818 LEVEL: Warning
PID : 13374 TID : 140165464975104 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : TS
APPHDL : 0-19 APPID: 210.21.51.36.6067.160518082413
AUTHID : BILLUSER HOSTNAME: o2m02
EDUID : 60 EDUNAME: db2agent (TS) 0
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemLogPoolConditions, probe:20
DATA #1 :
Reserved heap size exceeded for Kernel(BSU) Heap on node 0,
allocating additional unreserved memory.
Requested block size : 1180160 bytes.
Physical heap size : 33619968 bytes.
Configured heap size : 32440320 bytes.
Unreserved memory used by heap : 1179648 bytes.
Unreserved memory left in set : 5505024 bytes.
2016-05-18-16.24.24.025589+480 E1760784E590 LEVEL: Severe
PID : 13372 TID : 140374693635840 PROC : db2wdog 0 [db2inst1]
INSTANCE: db2inst1 NODE : 000
HOSTNAME: o2m02
EDUID : 2 EDUNAME: db2wdog 0 [db2inst1]
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20
MESSAGE : ADM0503C An unexpected internal processing error has occurred. All
DB2 processes associated with this instance have been shutdown.
Diagnostic information has been recorded. Contact IBM Support for
further assistance.
2016-05-18-16.24.24.076189+480 I1761375E501 LEVEL: Error
PID : 13384 TID : 139777151952704 PROC : db2vend (PD Vendor Process - 1)
INSTANCE: db2inst1 NODE : 000
HOSTNAME: o2m02
FUNCTION: DB2 UDB, oper system services, DB2VEND_main, probe:1040
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not exist"
DIA8506C Unexpected end of file was reached.
DATA #1 : String, 63 bytes
Fenced vendor process pipe failure, terminating vendor process.
2016-05-18-16.24.24.167448+480 E1761877E466 LEVEL: Error
PID : 13372 TID : 140374693635840 PROC : db2wdog 0 [db2inst1]
INSTANCE: db2inst1 NODE : 000
HOSTNAME: o2m02
EDUID : 2 EDUNAME: db2wdog 0 [db2inst1]
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:8959
DATA #1 : Process ID, 4 bytes
13374
DATA #2 : Hexdump, 8 bytes
0x00007FAB87BFD268 : 0201 0000 0900 0000 ........
收起