Hi, I have some notes left from a previous admin, that we have some vldb corruption that can be fixed by running 'vldb_check -fix'. My understanding is that we need to shut down the vlserver on our 3 db servers, and run this command on the lowest IP site, bring that up first, and then bring up the rest.
In order to minimize downtime, I'd like to run vldb_check on an offline copy of the vldb, but I'm wondering if the vlserver needs to be completely shutdown prior to making the copy, or if read-only mode would be good enough? If yes, I would basically bring down the vlserver on two sites, leaving it running on the site with the lowest ip (which if I understand correctly would go into read-only mode at this point). Then I'd make a copy of vldb.db0, run 'vldb_check -fix' on the copy, hand-propagate that out to the remaining sites, and then bring down the vlserver on the lowest ip site just before moving the fixed copy into place. I could then bring up the vlserver on the lowest ip site, and the remaining sites. Does this sound reasonable? We're looking to migrate our db servers from 1.4 to 1.6 in the future, and if I can fix the vldb corruption this way, then I could copy the vldb (and other dbs) to the new servers and run 'vldb_check -fix' there, before finally switching over from the last old db server. k- -- : Kendrick Hernandez : UNIX Systems Administrator : UNIX Systems and Infrastructure : Division of Information Technology : University of Maryland, Baltimore County
