Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

EMM database not starting on the Master server (NBU 7.1).

Created: 21 Jun 2013 | 5 comments
Mux's picture

EMM database not starting on the Master server.

There are many reasons why the EMM database wont start. Like an unexpected reboot of the server.

One of the main reason why EMM database wont start is due to the corrupted transaction log. The following procedure was performed in order to rebuild the transaction log:

1. Stop NetBackup if it is not already stopped:
/usr/openv/netbackup/bin/goodies/netbackup stop

2. Remove NBDB from auto_start option
/usr/openv/db/bin/nbdb_admin -auto_start NONE

3. Start the ASA database engine
/usr/openv/db/bin/nbdbms_start_server

4. To add the necessary environment variables to your shell, run the command:
/usr/openv/db/vxdbms_env.sh export SHLIB_PATH=/usr/openv/db/lib:/usr/openv/db/bin

5. Change directories to where the NBDB resides:
cd /usr/openv/db/data

6. Remove or rename the bad transaction log:
mv NBDB.log NBDB.log.bad

7. To force database recovery, while still in the /usr/openv/db/data directory, run the command (please note, the NBDB.log will not be created until step 10):
/usr/openv/db/bin/dbeng11 -f NBDB

8. Stop the database by running the command:
/usr/openv/db/bin/nbdbms_start_server -stop

9. Add NBDB and BMRDB to auto_start option
/usr/openv/db/bin/nbdb_admin -auto_start NBDB

10. To start the database, run the command:
/usr/openv/db/bin/nbdbms_start_server

11. Start Netbackup services

/usr/openv/netbackup/bin/goodies/netbackup start

Operating Systems:

Comments 5 CommentsJump to latest comment

Nicolai's picture

Look like copy and paste of http://www.symantec.com/docs/TECH55797

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Mark_Solutions's picture

Seems copy and paste is a recurring theme on here at the moment - if it is points they are after they won't get them!!no

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

mph999's picture

.... needs to be a sticky created with a list of forum rules me thinks ...

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Mux's picture

Well.. It wasnt a copy paste from the above mentioned link....

We faced the above issue last month due to an unexpected reboot and got the steps from the symantec technical support.

i posted it so that it may help others...

The mistake that I made was I didnt do a deep search before doing the post. Sorry for that and i will be more careful next time.

mph999's picture

No problem Mux.

What you need to do, is explain why the issue happened, but most importantly add something like this.

Unless confirmed that the the issue has the same cause as explained in this post, do not run this.

The reason, we have had people posting up 'commands' that could be very damaging, which no explanation as to why.

I appreciate you are trying to be helpful, but you can see the promblem this can cause.

I've seen major issues caused to systems by people just running commands and not understanding why.  In this case, to be fair, the above is fairly harmless - yess you could bring a system down if not run correctly, but not make it unrecoverable.

Many thanks,

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805