If necessary, use gfix -force with a sufficient timeout to let them try to get off gracefully. ![]() If the server is running and is still accepting connections then ask all users to cancel their work and log out.Skip this step if the server is not running or is unable to accept connections.Important: Never attempt a recovery task by operating directly on the production database file. If it is not practicable to move the file then rename it. Take the database off-line as soon as evidence of a possible corruption appears and isolate the file to prevent any further connections. ![]() Because some of the steps make irreversible changes to structures within the database, it is essential to isolate the original database file from these operations and work with a file copy. If you suspect you have a corrupt database, it is important to follow a proper sequence of recovery steps in order to avoid further corruption.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |