配置tsm在格式化資料庫資訊的時候報錯:This database name already exists

warehouse發表於2014-06-06

執行下面命令格式化資料庫時由於目錄許可權的問題報錯了,再執行的時候提示:

ANR0367W The server failed to format the database TSMDB1. This database name already exists.配置tsm在格式化資料庫資訊的時候報錯: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.

百度了一下找到一篇文章:
防止連結過期,內容複製如下:
--===================================

ANR0367W The server failed to format the database TSMDB1. This database name already exists.配置tsm在格式化資料庫資訊的時候報錯: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.

 配置tsm在格式化資料庫資訊的時候報錯:This database name already existsCauseWhile 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之後找到相關錯誤說明:

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

Before reissuing the command to format a new database, check the following items:
  • 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/,如需轉載,請註明出處,否則將追究法律責任。

相關文章