Frequent bpdbm <16> errors 'executing UPDATE DBM_MAIN.DBM)_ImageChangeLog'
Updated: 09 Feb 2012 | 11 comments
Recently created bpdbm legacy debug log folder on my master and see regular entries of the following for ALL of my clients.
02:44:33.545 [6322] <16> executeSql: Error executing UPDATE DBM_MAIN.DBM_ImageChangeLog SET Created DateTime = current utc timestamp WHERE (MasterServerKey = 1000002) AND (BackupID = 'barney_1327459414') AND (ClientType = 0) AND (OperationID = 1) (rc=100) ErrMsg , ErrCode 0, SqlState 02:45:05.483 [6647] <16> executeSql: Error executing UPDATE DBM_MAIN.DBM_ImageChangeLog SET Created DateTime = current utc timestamp WHERE (MasterServerKey = 1000002) AND (BackupID = 'fred_1327459036') AND (ClientType = 0) AND (OperationID = 1) (rc=100) ErrMsg , ErrCode 0, SqlState
Have performed a nbdb_admin -validate -full and get a clean bill of health
Master:
VERSION NetBackup 7.1.0.3
Linux SUSE 11 x86_64
Just a bit concerning. A bug perhaps. Ignore them as the ErrCode is 0 ?
Discussion Filed Under:
Comments
Nothing easy when you post,
Nothing easy when you post, Stuart!
Hopefully our Symantec BCE Martin will know...
Have you tried 'bpdbm -consistency 2' ?
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Stabs
Any funky locale settings which might be messing about with the time and date format?
Probably not related, but any chance you're bitten by the "1 licensed processor" bug in 7.1.0.3? (See TECH178219)
After applying the 7.1.0.3 upgrade, degraded performance may be seen in NetBackup and OpsCenter on Windows due to an unintentional CPU restriction imposed on the database.
http://symantec.com/docs/TECH178219
@CRZNo funky locale.Its a
@CRZ
No funky locale.
Its a linux master server - not a windows server which this technote says it only affects.
But I do have 4 physical CPU's
@Marianne
Can the consistency be run online.? Tried offline (netbackup shutdown) and taking a long time.... had to cancel to get daily backups going....
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
As far as I know it can be
As far as I know it can be executed with NBU online, but a quiet time should be chosen (no backups running).
Level 2 of consistency check does take a long time :
0 - A quick check of the NetBackup image database (the default).
1 - Performs more checks than the default check.
2 - The most in-depth consistency check. In addition to the level 0 and 1
checks, this level checks that the media that is mentioned in the image exists.
(That is, it cross-references the media servers databases.) On a large
NetBackup installation, the process takes much longer to complete than the
other checks.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
As per Mariannes excellent
As per Mariannes excellent post above, bpdbm -consistency 2 can be run with NBU running ...
M
02:45:05.483 [6647] <16>
Are all the errors related to clients that are ClientType = 0 ???
Martin
How do i correlate my clients
How do i correlate my clients to being ClientType = 0 ?
Have a mixture of clients OS Type Windows , UNIX, other (as seen in Admin Console Host Properties > Clients)
Have also got Virtual Machine clients. All are reported in the above type <16> errors. No distinction.
Thanks
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Looks like it is the
Looks like it is the multi-processor issue - the logs match previously seen issues.
M
On
On UNIX/Linux:
/usr/openv/db/log/server.log
Started up NetBackup and output in the above file shows.
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Can you run an All Log
Can you run an All Log Entries report for a period of an hour or so when you know you are seeing the errors - just in case we can spot anything else
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Open a case
I see a new Etrack opened earlier this week with a similar set of symptoms reported - 2684131 - and I think you should open a case, request an escalation and get attached to it...that is, if it's really bugging you. (It sounds like you're not seeing the high CPU utilization that was reported in the other case? There is one other difference - your server is SUSE and the Etrack was originally opened for a Windows server - but it's the same problem, namely lots of log entries reporting "executeSql: Error executing UPDATE DBM_MAIN.DBM_ImageChangeLog" despite an apparent successful finish)
Have your bpdbm log ready to move your case along to backline, then be ready for your backline engineer to request an EMM database dump (they'll tell you how).
Would you like to reply?
Login or Register to post your comment.