配置tsm在格式化資料庫資訊的時候報錯:This database name already exists
執行下面命令格式化資料庫時由於目錄許可權的問題報錯了,再執行的時候提示:
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.
百度了一下找到一篇文章:
防止連結過期,內容複製如下:
--===================================
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之後找到相關錯誤說明:
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/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 奇怪報錯資訊“db already exists with different case already have”解決方法
- django資料庫同步時報錯“Table 'XXX' already exists”Django資料庫
- vagrant up 啟動報錯 Stderr: VBoxManage.exe: error: A NAT rule of this name already existsError
- beego報錯 table name: `xxx` not existsGo
- git使用報錯fatal: remote origin already exists.GitREM
- HIVE運算的時候報HADOOP Name node is in safe mode 錯HiveHadoop
- 從32位資料庫還原到64bit資料庫open的時候報錯資料庫
- 奇怪的問題: 資料庫使用者登入的時候報錯資料庫
- srvctl新增資料庫資訊報錯資料庫
- 啟動oracle資料庫的時候報ORA-00205錯誤:Oracle資料庫
- 配置hive後設資料庫mysql時候出現 Unable to find the JDBC database jar on host : masterHive資料庫MySqlJDBCDatabaseJARAST
- 物理data guard備standby庫的時候報錯。
- linux oracle建立資料庫的時候報錯ORA-12547:TNS:lost contactLinuxOracle資料庫
- 【MybatisPlus】資料庫的datetime型別欄位為空的時候,報錯空指標?MyBatis資料庫型別指標
- Oracle資料庫配置錯誤資訊解決方法(轉)Oracle資料庫
- 分析資料庫的事務隔離級別在資料庫選型分析的時候很重要資料庫
- windows 安裝的oracle資料庫版本 登入的時候出現報錯,ORA-12560:TNS:協議配置器失敗WindowsOracle資料庫協議
- rsync 客戶端同步的時候報錯客戶端
- 執行dbca命令的時候報錯了
- 更換帶庫的壞Driver後,在TSM 做的配置操作
- 複製資料庫的報錯資料庫
- rman映象備份全庫的時候報ora-00600錯誤。
- Angular路由——在路由時候傳遞資料Angular路由
- 在查詢資料庫中,那些表在什麼時候改動結構資料庫
- setInterval()呼叫其他函式時候報錯函式
- tsm在client端執行dsmj報錯:jre version低client
- 配置 C3 工具時,修改/etc/host,再重新安裝叢集的時候報錯
- 在設定JIVE資料庫驅動時出錯資料庫
- 站點資訊配置-使用資料庫資料庫
- 在事件中實現 佇列的時候報錯請教一下事件佇列
- Oracle 資料庫的眾多 “NAME”Oracle資料庫
- npm publish 釋出一個 Angular 庫的時候報錯以及解決方法NPMAngular
- 資料庫升級報錯資料庫
- 12c 應答方式安裝資料庫的一點補充already exists. Specify another SID資料庫
- 在開啟dbcc連線資料庫檢視資料庫配置引數時提示SQL1337錯誤資料庫SQL
- “線上教育”來了!——隨時都是學習的好時候–資料資訊圖
- ora-27100:shared memory realm already exists錯誤的解決
- 資料庫啟動在mount狀態,無任何報錯資料庫