GENERAL ERROR: The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker don't error, but won't remain started and the NetBackup Device Manager service generates event log error, "EMM interface initialization failed, status = 334"
Exact Error Message
status 334: EMM interface initialization failed.
V-118-55 Unable to connect to database.
Details:
Overview:
The services called NetBackup Enterprise Media Manager (EMM) and NetBackup Resource Broker don't error, but won't remain started and the NetBackup Device Manager service generates event log error, "EMM interface initialization failed, status = 334". This is most likely to happen after the initial install of NetBackup 6.0 or the initial upgrade to NetBackup 6.0.
Troubleshooting:
Several symptoms listed below all point to a similar problem.
Master Log Files:
1. The open database connectivity (ODBC) Data Source Administrator, under Administrative Tools > Data Sources (ODBC), shows VERITAS NB Adaptive Server Anywhere 9.0.1 as "Not marked" in the Version and Company fields on the Drivers tab. (See Figure 1)
Figure 1
2. The NetBackup Device Manager service will display this error in the Application Event Log:
Event Type: Error
Event Source: NetBackup Device Manager
Event Category: None
Event ID: 0
Date: 2/10/2006
Time: 1:50:48 PM
User: N/A
Computer: xxxxxxxxx
Description:
EMM interface initialization failed, status = 334
3. The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker don't error, but won't remain started.
4. The command line process \<InstallPath>\VERITAS\NetBackup\bin>nbdb_ping fails with, "Database [NBDB] is not available."
5. The log \<InstallPath>\VERITAS\NetBackup\logs\admin records this error after the failed nbdb_ping:
14:03:37.687 [3612.540] <16> nbdb_ping: ODBC connection failed.
14:03:37.687 [3612.540] <16> nbdb_ping: ErrMsg Specified driver could not be loaded due to system error 126 (VERITAS NB Adaptive Server Anywhere 9.0.1)., ErrCode -1, Sqlstate IM003
6. The VXUL Logs will show this sequence of errors: (syntax used to collect the log sample: vxlogview -t 00:10:00 -d all)
2/7/2006 18:58:55.104 [Diagnostic] NB 51216 nbemm 111 PID:3752 TID:3744 [No context] 1 V-111-1049 [ConnectionManager::OpenConnection] EMMServer generic error = Can't connect to the database (Specified driver could not be loaded due to system error 126 (VERITAS NB Adaptive Server Anywhere 9.0.1). <-1> )
2/7/2006 19:26:20.661 [Debug] NB 51216 nbrb 118 PID:3852 TID:740 [No context] 1 [RBDatabase::connectDatabase()] ODBC connection failed. ErrMsg: Specified driver could not be loaded due to system error 126 (VERITAS NB Adaptive Server Anywhere 9.0.1). ErrCode: -1 DBErrCode: 160 Sqlstate: IM003
2/7/2006 19:26:20.661 [Application] NB 51216 nbrb 118 PID:3852 TID:740 [No context] [Critical] V-118-55 Unable to connect to database. NetBackup Resource Broker will not start.
2/7/2006 19:26:20.661 [Debug] NB 51216 nbrb 118 PID:3852 TID:740 [No context] 1 [doRun] unable to initialize the database, error: 25
Resolution:
The path to a critical DLL for allowing ODBC communication to the EMM database can not be found at the specified location. The DLL is called DBODBC9.DLL. Check to see if the DLL exists in the correct location, \<InstallPath>\VERITAS\NetBackupDB\WIN32\DBODBC9.DLL
If the DLL is there, check the registry to make sure it is pointing to the correct working path for this DLL:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\VERITAS NB Adaptive Server Anywhere 9.0.1\ and verify the keys named Driver and Setup are pointing to the correct path. If they are incorrect, change them to reflect the correct path to DBODBC9.DLL.
Once the path statements have been adjusted, stop and start the NetBackup services:
1. Stop NetBackup services by running the following command:
<installPath>\veritas\netbackup\bin\bpdown
2. Verify all processes have been stopped by running the following command:
<installPath>\veritas\netbackup\bin\bpps
Note: A reboot may be necessary to fully eliminate any lingering NetBackup processes that might not terminate when the services are stopped.
3. Start the NetBackup services by running the following command:
<installPath>\veritas\netbackup\bin\bpup作者: tuzhu2046 时间: 2009-09-12 17:12 标题: 回复 #8 xiazhen9842 的帖子 3Q！
这种方式尝试过了，还是不行。。
现在的问题是，将两个media server 加进来一扫，netbackup device manager服务就会停掉。