12.07.2015 Views

Caché High Availability Guide - InterSystems Documentation

Caché High Availability Guide - InterSystems Documentation

Caché High Availability Guide - InterSystems Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Error Conditions1.3.2 Sample Recovery Errors1.3.2.1 Error Opening CACHE.DATIf you cannot open a cache.dat or cache.ext file that needs to be restored, you see this messageduring the write phase:Can't open file: /usr/cache/cache.datIts blocks weren't writtenRecovery continues trying to write blocks to all other directories to be restored. If this happens,do the following:1. Do not delete the write image journal.2. Try to correct the problem with the <strong>Caché</strong> database on which the error occurred.3. Restart and let recovery try again.Directories that were restored the first time are not listed as having blocks to be writtenduring this second recovery attempt.1.3.2.2 Error Writing to <strong>Caché</strong> BlockIf recovery starts to write to a <strong>Caché</strong> database file, but cannot write a particular block number,you see this message:Error writing block number xxxxIf this error occurs four times in a single restoration, the restoration aborts, and you see thismessage:Error writing block number xxxxDo you want to delete the Write Image File (Y/N)? Y =>Enter N to retain the write image journal. Recovery attempts to continue. If it still does notsucceed and you receive this message again, call <strong>InterSystems</strong> Technical Support. If youmust continue immediately, you can delete or rename the write image journal. If you deleteit, you lose all changes recorded in it.1.3.2.3 Error Reading Write Image JournalIf an error occurs when recovery attempts to read the write image journal file, you see thismessage:<strong>Caché</strong> <strong>High</strong> <strong>Availability</strong> <strong>Guide</strong> 9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!