02-16-2009 03:30 PM
These are some of the errors reported:
Query incomplete/failed ([12:1166] Velocis daemon error - the daemon is probably not running.)
[Critical] From: BSM@consola.sigmaq.com "PRO47_DBARCH" Time: 2/16/2009 6:45:14 AM
[61:4001] Error accessing the database, in line 1254, file x:\src\sm\bsm2\bcsmutil.c.
Database subsystem reports:
"[12:1165] Internal Database network communication error."
Additionaly I am not able to perform extended checks on the db, since the service since the "Data Protector RDS" Service crashes at the start of the check (omnidbcheck -extended).
02-16-2009 09:14 PM
Pls check the status of DP demons
if the any demon is not running then you can use
but be careful while excuting the omnisv -status command that time any backup session should not run
02-17-2009 08:22 AM
I finally determined that the "filenames" and "core" db were corrupted. After a few hours, I found this procedure to export/import the db.
Apparently, as part of the process the db corruption is fixed as well.
HP Tech support also sent me the attached document with a similar procedure.
02-17-2009 08:23 AM
Backups are running normaly.
Velocis is not crashing anymore.
I am now able to run db tests/checks without problems.
06-01-2009 04:46 AM
Now that you have been running for a few months after you fixed your db corruption, have you seen the error again?
I have been getting this error since December, and its very intermittent
HP told us in March:
This issue is caused by a combination of stale sessions and a particular limit set in the /var/opt/omni/server/db40/datafiles/catalog/rdmser
We changed the setting per HP - and error is still occuring.....
I'm wondering now if we have coruption - like you did -
How long did it take you to export and re-import your database?
Thanks for the advice.