Clearcase error: db_VISTA error -901
Posted on December 25, 2008
Symptom:
Vob rpc_server and vob server crashed and can not been restart.And with the following error in db_server_log
db_server(13306): Error: Shared memory version changed on lock from 44dee33d to 44d5a8bf. db_server(13306): Error: DBMS error in "../db1.c" line 1189 db_server(13306): Error: DBMS error in /net/host/vobstg/test.vbs/db. db_server(13306): Error: db_VISTA error -901 (errno == "Resource temporarily unavailable")
Cause
There is a db_server process that has been running for a substantial amount of time because the string_report script is accessing a VOB that is not stored on the local ClearCase server. The long running db_server process could be, for example, a GUI left open for a long time, such as cleartool lsvtree -g.
Note: The string_report script is located in /opt/rational/clearcase/etc/utils/.
This occurs when the VOBs are stored on a remote storage device, such as a Network Appliance (NetApp),while the ClearCase server processes are running locally on a different VOB server host.
Currently, string_report can be run on a machine that is not the VOB host, but has NFS (Network File System) access to the VOB storage directory of a VOB hosted on another machine. This results in contention in updates of the memory mapped /var/adm/atria/almd file, which results in errors being reported in the db_server log file.
Solution
No complete solution.
You relocate your vob direcotory to other disk space the fix the issue temporarily.
Eg.If your vob located in /vobs/vobname.vbs,then you can
cp -R /vobs/vobname.vbs /vobs/vobname_new.vbs mv /vobs/vobname.vbs /vobs/vobname_dist.vbs mv /vobs/vobname_new.vbs /vobs/vobname.vbs
Popularity: 7% [?]
» Filed Under Clearcase
Comments
Leave a Reply