Effect Of Using -F to start the database

[taqvia]

Hi,

I would like to know the consequence of using -F to bring up the database. We tried bringing down the database gracefully but it was not down after waiting for a subsequent time we did Control-c which crashed the database. when tried bringing up the databse it didnt come up we have to forcefully truncate the BI and then bring up the database. The databse came up but with some erorrs we removed the error by running a MOck Index and the erros no longer appeared. Now the databse is UP and running I would like to know if there will be any long term effect because it is always advisable not to use -F option but there was no other way to bring it up as restoring from backup and then rolling forward the AI could have taken a long time .

Arshad

 

[TomBascom]

When you use dash-F to bring up a db your db is F'd.

-F throws away the bi file which means that your database integrity has been compromised.

You might think that you have "got away with it" if all bi notes had already been flushed to the database -- some people feel like this is the case if the db has been "quiet" for a while prior to the crash. But you have no way to be certain. The corruption that -F induces may be obvious but it is much more likely that it will be subtle and may not be noticed for quite some time. You should not take comfort in the thought that the problems may not be noticed for a while. If, for instance, your accounts don't balance but that isn't noticed until month-end things could get really ugly when you try to figure out why.

Do not ever use -F on a production database. Instead restore and roll forward.