R
Ruanne Cluer
Guest
Yes, prorest is the way to go. These are instructions of last resort 
The Article 000046256, is specifically for UNIX. The objective of the instruction is to keep production running until you can fix the database structure again. On Windows you'd get "Permission denied" trying to delete your ai files while the database is running. The offline repair and recover instruction should work If you've deleted all AI files, you build them again by ensuring the Control Area is repaired: $ del foo.a* $ prostrct list foo (now remove the ai extents from the .st file) $ del foo.db $ prostrct builddb foo foo.st (this has every extent except ai files in it) $ prostrct add foo foo_ai.st (this only has the ai files in it)
Continue reading...
The Article 000046256, is specifically for UNIX. The objective of the instruction is to keep production running until you can fix the database structure again. On Windows you'd get "Permission denied" trying to delete your ai files while the database is running. The offline repair and recover instruction should work If you've deleted all AI files, you build them again by ensuring the Control Area is repaired: $ del foo.a* $ prostrct list foo (now remove the ai extents from the .st file) $ del foo.db $ prostrct builddb foo foo.st (this has every extent except ai files in it) $ prostrct add foo foo_ai.st (this only has the ai files in it)Continue reading...