Linux, db2V9.7 删除实例删除不掉
删除实例删除不掉，报错信息：bogon:/opt/ibm/db2/V9.7/instance # ./db2ilistdb2inst1bogon:/opt/ibm/db2/V9.7/instance # ./db2idrop -f db2inst1DBI1324W Support of the -f command is deprecated. For more information, see the ...显示全部
删除实例删除不掉，报错信息：
bogon:/opt/ibm/db2/V9.7/instance # ./db2ilist
db2inst1
bogon:/opt/ibm/db2/V9.7/instance # ./db2idrop -f db2inst1
DBI1324W Support of the -f command is deprecated. For
more information, see the DB2 Information Center.
DBI1135E The primary group 'users' of user ID 'db2inst1' is
invalid.
Explanation:
The primary group name of the instance user ID:
1. Cannot be one of "guests", "admins", "users" or "local".
2. Cannot start with "sql" or "ibm".
3. Cannot start with a numeral number.
4. Can contain only lowercase letters (a-z), numbers (0-9), and the
underscore character ( _ ).
User response:
Ask a user with root privilege to change the primary group of the
instance user ID to a valid group as described above and then try the
command again.
DBI1079I Output is saved in the log file /tmp/db2idrop.log.3114.
Explanation:
All processed and failed operations have been saved into this log file.
User response:
Do not modify this file in any way. This file is for IBM Technical
Support reference.
我安装数据库的情况：
我装的 是 db2V9.7 ESE版本的
安装包 放到 /home/db2install 中
然后解压 安装文件
运行 ./home/db2install/ese/db2_install 进行安装
安装目录 /opt/ibm/db2/V9.7
然后我开始建立组和用户
建了三个组 db2grp，db2fgrp，db2agrp
然后创建三个用户
db2inst1 在 db2grp 下
db2das 在 db2fgrp 下
db2fenc 在 db2agrp 下
然后创建实例
运行 ./dascret -u db2das 命令成功了
在运行 ./db2icet -u db2inst1 db2inst1
这时候 在 /home/db2inst1/下创建了 sqllib
但是 命令执行的结果是报错 说是我组和用户有问题
我就把 之前建立的所有用户和组 还有 /home/db2inst1/ 下的 sqllib全部都删除了
现在我想重新来过
我查看 ./db2ilist 发现 有 db2inst1 这个实例 使用 db2idrop 确怎么也删不掉
我创建实例的错误：
/opt/ibm/db2/V9.7/instance/db2iutil: line 5192: 17077 Segmentation fault ${DB2DIR?}/instance/db2isrv -addfcm -i ${INSTNAME?} ${DB2ISRVOPTS?}
2015-03-23-16.54.06.868060+480 I1E1437 LEVEL: Event
PID : 17521 TID : 140392391333664PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2inst1" uses "64" bits and DB2 code release "SQL09070"
with level identifier "08010107".
Informational tokens are "DB2 v9.7.0.0", "s090521", "LINUXAMD6497", Fix Pack "0".
DATA #2 : System Info, 440 bytes
System: Linux bogon 0 3 x86_64
CPU: total:12 online:12 Cores per socket:16 Threading degree per core:1
Physical Memory(MB): total:40976 free:35325
Virtual Memory(MB): total:43030 free:37379
Swap Memory(MB): total:2054 free:2054
Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:20487
msgNumberOfHeaders:65536 msgMaxQueueSize:65536
msgMaxSegmentSize:16 shmMax:9223372036854775807 shmMin:1
shmIDs:4096 shmSegments:4096 semMap:256000 semIDs:1024
semNum:256000 semUndo:256000 semNumPerID:250 semOps:32
semUndoSize:20 semMaxVal:32767 semAdjustOnExit:32767
Cur data size (bytes) = 0xFFFFFFFF
Cur stack size (bytes) = 0x00800000
Cur core size (bytes) = 0x00000400
nofiles (descriptors) = 0x00000400
Information in this record is only valid at the time when this file was
created (see this record's time stamp)
2015-03-23-16.54.06.867732+480 I1439E707 LEVEL: Severe
PID : 17521 TID : 140392391333664PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.06.869970+480 I2147E331 LEVEL: Severe
PID : 17521 TID : 140392391333664PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, command line process, clp_bp_main, probe:2
DATA #1 : Hexdump, 4 bytes
0x00007FFFB5264768 : 71E8 FFFF q...
2015-03-23-16.54.15.133832+480 I2479E707 LEVEL: Severe
PID : 17530 TID : 139967285405472PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.25.236191+480 I3187E707 LEVEL: Severe
PID : 17632 TID : 140409390843680PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.35.346518+480 I3895E707 LEVEL: Severe
PID : 17733 TID : 139849577690912PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.45.553348+480 I4603E707 LEVEL: Severe
PID : 17834 TID : 139968871282464PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.55.652038+480 I5311E707 LEVEL: Severe
PID : 17936 TID : 140192821503776PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.55.05.751799+480 I6019E707 LEVEL: Severe
PID : 18037 TID : 139678034786080PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.55.06.842843+480 I6727E387 LEVEL: Error
PID : 17519 TID : 140329021663008PROC : db2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, command line process, clp_start_bp, probe:3
MESSAGE : CLP frontend unable to get REQUEST queue handle
DATA #1 : Hexdump, 4 bytes
0x00007FFFFF214C58 : 4200 0F87 B...
DBI1703E No valid service name or port number found.
Explanation:
No valid service name or port number for this instance can be found in
the TCP/IP services file. This information is either missing or is
invalid.
If you installed "DB2 Extended Server Edition" product, a service name
must be specified for the instance before using this command.
User response:
Specify valid service name and port number for this instance and enter
this command again.
DBI1079I Output is saved in the log file /tmp/db2icrt.log.16307.
Explanation:
All processed and failed operations have been saved into this log file.
User response:
Do not modify this file in any way. This file is for IBM Technical
Support reference.
12:04:47收起
bogon:/opt/ibm/db2/V9.7/instance # ./db2ilist
db2inst1
bogon:/opt/ibm/db2/V9.7/instance # ./db2idrop -f db2inst1
DBI1324W Support of the -f command is deprecated. For
more information, see the DB2 Information Center.
DBI1135E The primary group 'users' of user ID 'db2inst1' is
invalid.
Explanation:
The primary group name of the instance user ID:
1. Cannot be one of "guests", "admins", "users" or "local".
2. Cannot start with "sql" or "ibm".
3. Cannot start with a numeral number.
4. Can contain only lowercase letters (a-z), numbers (0-9), and the
underscore character ( _ ).
User response:
Ask a user with root privilege to change the primary group of the
instance user ID to a valid group as described above and then try the
command again.
DBI1079I Output is saved in the log file /tmp/db2idrop.log.3114.
Explanation:
All processed and failed operations have been saved into this log file.
User response:
Do not modify this file in any way. This file is for IBM Technical
Support reference.
我安装数据库的情况：
我装的 是 db2V9.7 ESE版本的
安装包 放到 /home/db2install 中
然后解压 安装文件
运行 ./home/db2install/ese/db2_install 进行安装
安装目录 /opt/ibm/db2/V9.7
然后我开始建立组和用户
建了三个组 db2grp，db2fgrp，db2agrp
然后创建三个用户
db2inst1 在 db2grp 下
db2das 在 db2fgrp 下
db2fenc 在 db2agrp 下
然后创建实例
运行 ./dascret -u db2das 命令成功了
在运行 ./db2icet -u db2inst1 db2inst1
这时候 在 /home/db2inst1/下创建了 sqllib
但是 命令执行的结果是报错 说是我组和用户有问题
我就把 之前建立的所有用户和组 还有 /home/db2inst1/ 下的 sqllib全部都删除了
现在我想重新来过
我查看 ./db2ilist 发现 有 db2inst1 这个实例 使用 db2idrop 确怎么也删不掉
我创建实例的错误：
/opt/ibm/db2/V9.7/instance/db2iutil: line 5192: 17077 Segmentation fault ${DB2DIR?}/instance/db2isrv -addfcm -i ${INSTNAME?} ${DB2ISRVOPTS?}
2015-03-23-16.54.06.868060+480 I1E1437 LEVEL: Event
PID : 17521 TID : 140392391333664PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2inst1" uses "64" bits and DB2 code release "SQL09070"
with level identifier "08010107".
Informational tokens are "DB2 v9.7.0.0", "s090521", "LINUXAMD6497", Fix Pack "0".
DATA #2 : System Info, 440 bytes
System: Linux bogon 0 3 x86_64
CPU: total:12 online:12 Cores per socket:16 Threading degree per core:1
Physical Memory(MB): total:40976 free:35325
Virtual Memory(MB): total:43030 free:37379
Swap Memory(MB): total:2054 free:2054
Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:20487
msgNumberOfHeaders:65536 msgMaxQueueSize:65536
msgMaxSegmentSize:16 shmMax:9223372036854775807 shmMin:1
shmIDs:4096 shmSegments:4096 semMap:256000 semIDs:1024
semNum:256000 semUndo:256000 semNumPerID:250 semOps:32
semUndoSize:20 semMaxVal:32767 semAdjustOnExit:32767
Cur data size (bytes) = 0xFFFFFFFF
Cur stack size (bytes) = 0x00800000
Cur core size (bytes) = 0x00000400
nofiles (descriptors) = 0x00000400
Information in this record is only valid at the time when this file was
created (see this record's time stamp)
2015-03-23-16.54.06.867732+480 I1439E707 LEVEL: Severe
PID : 17521 TID : 140392391333664PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.06.869970+480 I2147E331 LEVEL: Severe
PID : 17521 TID : 140392391333664PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, command line process, clp_bp_main, probe:2
DATA #1 : Hexdump, 4 bytes
0x00007FFFB5264768 : 71E8 FFFF q...
2015-03-23-16.54.15.133832+480 I2479E707 LEVEL: Severe
PID : 17530 TID : 139967285405472PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.25.236191+480 I3187E707 LEVEL: Severe
PID : 17632 TID : 140409390843680PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.35.346518+480 I3895E707 LEVEL: Severe
PID : 17733 TID : 139849577690912PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.45.553348+480 I4603E707 LEVEL: Severe
PID : 17834 TID : 139968871282464PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.54.55.652038+480 I5311E707 LEVEL: Severe
PID : 17936 TID : 140192821503776PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.55.05.751799+480 I6019E707 LEVEL: Severe
PID : 18037 TID : 139678034786080PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
MESSAGE : ZRC=0xFFFFE871=-6031
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4
sqlerrmc: 0 11
sqlerrp : SQLFRCFG
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:
2015-03-23-16.55.06.842843+480 I6727E387 LEVEL: Error
PID : 17519 TID : 140329021663008PROC : db2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, command line process, clp_start_bp, probe:3
MESSAGE : CLP frontend unable to get REQUEST queue handle
DATA #1 : Hexdump, 4 bytes
0x00007FFFFF214C58 : 4200 0F87 B...
DBI1703E No valid service name or port number found.
Explanation:
No valid service name or port number for this instance can be found in
the TCP/IP services file. This information is either missing or is
invalid.
If you installed "DB2 Extended Server Edition" product, a service name
must be specified for the instance before using this command.
User response:
Specify valid service name and port number for this instance and enter
this command again.
DBI1079I Output is saved in the log file /tmp/db2icrt.log.16307.
Explanation:
All processed and failed operations have been saved into this log file.
User response:
Do not modify this file in any way. This file is for IBM Technical
Support reference.
12:04:47收起