nbemm stops after a few seconds

[Alexander_Malys]

Hello, colleagues.
we have a problems after upgrade procedure from NB5.1MP3 to 6.0MP2.
After we have installed 6.0 and used nbpushdata -add on all needed systems, we have tried to apply MP2.
NB_CLT_60_2_M was installed succesfully, but while installation NB_60_2_M? we have got a message:
Upgrading NBDB:

/usr/openv/db/bin/nbdb_upgrade -dbn NBDB
Verifying the running version of NBDB ...
Failed system call, '/usr/openv/db/bin//nbdb_unload -dbn NBDB -s /tmp'
Verification Failed.

ERROR: Unable to upgrade database to current level.
Installation of pack NB_60_2_M FAILED Fri May 5 14:39:12 MSD 2006 Rev. 1.33.4.13.
--------------------
And now nbemm stops after a seconds of starting without any messages. May be somebody knows a cause of such problems?

Thanks Sergey

[Stumpr2]

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"
http://support.veritas.com/docs/281817

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 \\VERITAS\NetBackup\bin>nbdb_ping fails with, "Database is not available."

5. The log \\VERITAS\NetBackup\logs\admin records this error after the failed nbdb_ping:
14:03:37.687 <16> nbdb_ping: ODBC connection failed.
14:03:37.687 <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 NB 51216 nbemm 111 PID:3752 TID:3744 1 V-111-1049 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 NB 51216 nbrb 118 PID:3852 TID:740 1 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 NB 51216 nbrb 118 PID:3852 TID:740 V-118-55 Unable to connect to database. NetBackup Resource Broker will not start.
2/7/2006 19:26:20.661 NB 51216 nbrb 118 PID:3852 TID:740 1 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, \\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:
\veritas\netbackup\bin\bpdown

2. Verify all processes have been stopped by running the following command:
\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:
\veritas\netbackup\bin\bpupBS

[Alexander_Malys]

Thanks Bob, but i forget to say, that im use Solaris and even could not find the log with reason of trouble with EMM

[zippy]

Alex,

Can you say

"6.x is a POC"

JD

PS

Please give Bob some points b4 he looses his mind!Message was edited by:
James Dunn

[Alexander_Malys]

Seems, like problem with EMM connected with unsuccessfull upgrade to MP2. This is output of /opt/openv/netbackup/bin/vxlogview -p 51216 -o 111
But even after uninstall MP2 problem steel exist

05/05/06 17:33:35.229 Should start
05/05/06 17:33:35.818 Unable to get local credential(/net/code/builds/60MP2/src/common/libVcnbac/cnbac.h:386)
05/05/06 17:33:36.137 V-111-1048 EMMServer verbose level = 1
05/05/06 17:33:36.227 NumberOrbThreads 10 NumberDbConnections 4 NumberDbBrowseConnections 3
05/05/06 17:33:36.424 Orb is set
05/05/06 17:33:36.669 Server initializing VxEMM
05/05/06 17:33:36.669 V-111-1000 EMMServer initializing = VxEMM
05/05/06 17:33:36.670 Option: -DbServer "VERITAS_NB_e220a"
05/05/06 17:33:36.670 V-111-1001 EMMServer initialization option = Option: -DbServer "VERITAS_NB_e220a"
05/05/06 17:33:36.670 Option: -DbPort "13785"
05/05/06 17:33:36.670 V-111-1001 EMMServer initialization option = Option: -DbPort "13785"
05/05/06 17:33:36.671 Option: -DbName "NBDB"
05/05/06 17:33:36.671 V-111-1001 EMMServer initialization option = Option: -DbName "NBDB"
05/05/06 17:33:36.671 Option: -DbConnections "4"
05/05/06 17:33:36.671 V-111-1001 EMMServer initialization option = Option: -DbConnections "4"
05/05/06 17:33:36.671 Option: -DbBrowseConnections "3"
05/05/06 17:33:36.671 V-111-1001 EMMServer initialization option = Option: -DbBrowseConnections "3"
05/05/06 17:33:36.672 Option: -ConnectString "PROWS=600;CS=utf8;UID=EMM_MAIN;PWD=******;LINKS=shmem,tcpip{PORT=13785};ENG=VERITAS_NB_e220a;DBN=NBDB"
05/05/06 17:33:36.672 V-111-1001 EMMServer initialization option = Option: -ConnectString "PROWS=600;CS=utf8;UID=EMM_MAIN;PWD=******;LINKS=shmem,tcpip{PORT=13785};ENG=VERITAS_NB_e220a;DBN=NBDB"
05/05/06 17:33:36.838 Server running
05/05/06 17:33:36.839 V-111-1002 EMMServer running
05/05/06 17:33:36.839 Total conn <4>
05/05/06 17:33:36.839 Total browse conn <3>
05/05/06 17:33:37.841 V-111-1049 EMMServer generic error = Schema version mismatch. expected <6.0.2.0> Db <6.0.0.0>
05/05/06 17:33:37.842 V-111-1041 Can't read schema version or version mismatch
05/05/06 17:33:37.863 EMM Server shutting down
05/05/06 17:33:37.863 V-111-1003 EMMServer shutting down
05/05/06 17:33:37.865 V-111-1049 EMMServer generic error = Exception caught for IORTable clean up
05/05/06 17:33:37.865
05/05/06 17:33:37.866 Cleaning MSR connction <1>
05/05/06 17:33:37.866 Cleaning MSR connction <2>
05/05/06 17:33:37.866 Cleaning MSR connction <3>
05/05/06 17:33:37.866 Released all result sets for all MSR connctions
05/05/06 17:33:37.867
05/05/06 17:33:37.867 Closed <1> SSR connection(s)
05/05/06 17:33:37.869 Closed <3> MSR connection(s). Still in use <0>
05/05/06 17:33:37.869 Done
05/05/06 17:33:37.869 done
05/05/06 17:33:37.869 Deactivated DB connections
05/05/06 17:33:37.870 EMM Server shut down complete
05/05/06 17:33:37.900

[Sergey_Evsyuk1]

Hello, this workaround from Veritas:

This has been reported previously on some systems.

One thing to try would be the following. The fix for this is due in MP3 and on occasions the binaries are required.

Could you try the following commands, make sure netbackup comes up and then we can look to install other patches

Please try the following commands:



1. /usr/openv/db/bin/nbdbms_start_stop start

2. /usr/openv/db/bin/nbdb_ping

3. /usr/openv/db/bin/nbdb_upgrade -v

4. /usr/openv/db/bin/nbdb_upgrade -dbn NBDB