Any chance to open a database which needs recovery?

[MCMartin]

Any chance to open a database which needs recovery in read-only mode? My attempts with dbeng -r lead to the error message that the database needs recovery and dbeng refuses to start. Recovery is no option as the database has a checksum problem in the checkpoint log 😞

[VolkerBarth]

Recovery is no option

So if the current database file is damaged, can't you go back to the last full backup and the current transaction log (and possibly intermediate TLs), in case those files are not damaged?

[MCMartin]

yes that is our last option, before that I would liked to run a dbvalid -s to check all checksums and see how much damaged has occurred

[VolkerBarth]

AFAIK read-only mode requires a valid database file and will fail in your case. (I assume dbeng -f against a copy of the database file will fail, as well.)

If the current database file is damaged but the current TL is OK, and there is a clear backup path, I would

1. use my recovery plan to bring the system up again to the point of the last committed transaction,
2. and then might take the time to find out why the current database file has been damaged afterwards.

Of course I do not know your requirements and recovery times so treat this as just my 2 cents.

(In case you except the server hardware to be questionable, well, then that would require a different doing...)

[regdomaratzki]

You cannot open a database which needs recovery in read-only mode. The recovery process makes changes to the database.