EMM database error (196
Hope anyone can help me with this problem.
I get the following error when I try to add new media or to inventory the robot: EMM database error (196). It does not affect storage unit, policies and I can run daily backup on disk. Problem is that I take our monthly backup on tape, and just figured out that this doesn't work. I think the error come from updating from 6.0 to 6.0MP3, but not sure if that's the case.
I have checked the nbemm log with vxlogview and it says that I need to run nbpushdata.exe -add. Problem is that I can't run this command, did a test with it yesterday and ended up with 50 duplicate media id and couldn't sort out the new "emm database". So I had to remove it all and run a catalog restore from a backup (which I took before I tried it).
Does anyone have any experience with 196 error?
Thanks in advance for the help, would be great if anyone can help me on this matter.
Best regards
Thomas.
Comments
There is/was a know bug when applying MP2 on Solaris (assuming this is a Solaris box), I would have thought that they would have incorporated the fix in MP3.
nbpushdata -add_flag NBPUSHDATA_G_GLOBDB_HOST
dummyhostname:dummyhostname fixes the problem
This may be some help as well.
http://seer.entsupport.symantec.com/docs/283176.htm
After I removed MP3, problem was solved.
Now I can backup to tape again, add new media pools and run an robot inventory. Look like it was MP3 who caused the problem.
Maybe I will set up a test scenario to see if I can find out anything.
You should definitely log a support call with Symantec.
Adding a Maintenance Pack should NOT break your install!
And throw some points out please, you asked a tough question and only 1 person replied ...
You should clean up your NetBackup catalog database of all inconsistencies before you upgrade to NetBackup 6.0. And running "nbpushdata -add" successfully after upgrading the binaries to NetBackup 6.0 is a must. Else the EMM database will not be properly populated.
Regards,
Karthik
I am running 6.0 mp3 on Solaris and ran into this. I think my solution was to restart PBX. Either that or I restated Netbackup. Pretty sure it was PBX though.
Would you like to reply?
Login or Register to post your comment.