执行下面命令格式化数据库时由于目录权限的问题报错了,再执行的时候提示:
ANR0367W The server failed to format the database TSMDB1. This database name already exists.
Problem(Abstract)After a failed initialisation of the TSM Server, the second attempt may fail with ANR0367W The server failed to format the database TSMDB1. This database name already exists.
百度了一下找到一篇文章:http://hi.baidu.com/asmboy001/item/1bb58608adab22334bc4a32c
防止链接过期,内容拷贝如下:
--===================================
ANR0367W The server failed to format the database TSMDB1. This database name already exists.
Problem(Abstract)After a failed initialisation of the TSM Server, the second attempt may fail with ANR0367W The server failed to format the database TSMDB1. This database name already exists. SymptomAfter a failed initialisation of a new TSM Server, the second attempt may fail with the following:
Tivoli Storage Manager for AIX
Version 6, Release 1, Level 2.0
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 2009.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR7801I Subsystem process ID is 966700.
ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt.
ANR7811I Using instance directory /tsmdata/server1
ANR4726I The ICC support module has been loaded.
ANR0152I Database manager successfully started.
ANR0152I Database manager successfully started.
ANR0367W The server failed to format the database TSMDB1. This database name already exists.
Error 2160 initializing the database
ANR2678E Server database format failed.
CauseWhile the initialization failed, the database was created. Resolving the problemMethod 1:
From the TSM Server installation directory, issue the following command:
dsmserv removedb TSMDB1
If it succeeds, you can retry creating an instance. If it fails, we will need to try method 2.
Method 2:
For the second method, is to drop the database from DB2.
set db2instance=server1
db2stop force
db2start
db2 drop database TSMDB1
Method 3:
For the third method is to do an uncatalog of the database.
set db2instance=server1
db2 uncatalog database tsmdb1
--===================================
用文章中提到的第二种办法先把存在db2 dbdrop掉:
Method 2:
For the second method, is to drop the database from DB2.
set db2instance=server1
db2stop force
db2start
db2 drop database TSMDB1
--=====================================
之后把权限搞定了重新继续执行下面命令初始化成功了:
[tsminst1@udev ~]$ dsmserv format dbdir=/tsmdb/db activelogdir=/tsmdb/dblog archlogdir=/tsmdb/dbarchlog
ANR7800I DSMSERV generated at 10:49:41 on May 12 2010.
Tivoli Storage Manager for Linux/x86_64
Version 6, Release 2, Level 1.0
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 2010.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR7801I Subsystem process ID is 5446.
ANR0900I Processing options file /home/tsminst1/dsmserv.opt.
ANR7814I Using instance directory /home/tsminst1.
ANR4726I The ICC support module has been loaded.
ANR0152I Database manager successfully started.
ANR1380I The buffer pool monitor switch is enabled.
ANR0992I Server's database formatting complete.
ANR0369I Stopping the database manager because of a server shutdown.
ANR2976I Offline DB backup for database TSMDB1 started.
ANR2974I Offline DB backup for database TSMDB1 completed successfully.
--===========================================
初始化的过程中由于要求的disk 空间不足还报过错误:
baidu之后找到相关错误说明:http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=%2Fcom.ibm.itsm.messages.doc%2Fmsgs219.html
ANR0370E: Diagnostic(ID) During the format operation, the server cannot create files in one or more directories that you specified for log type. Ensure that the file system where the directory is located has sufficient space.
Explanation
Space is not available for the server to write data to the directory.
System action
The format operation stops.
User response
- Check whether the format operation created a database but did not remove the database after the failure. If the database that was created was not removed, use the utility DSMSERV REMOVEDB db_name to remove it.
- Check that space is available to the directories that you specified for ACTIVELOGDIR,ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. Ensure that the amount of space meets requirements. For example, the directory for ACTIVELOGDIR must have at least 8 GB space available.
- Remove any files that are in the directories that you want to use for the recovery logs.
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/19602/viewspace-1176902/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/19602/viewspace-1176902/