Let database file is damaged:
and log file is damaged:
- Unable to backup the database using "-k recover" & "-k nocopy":
P.S. I think it has something wrong, if we are due to breakage of undo-log are losing real data. |
Let database file is damaged:
and log file is damaged:
- Unable to backup the database using "-k recover" & "-k nocopy":
P.S. I think it has something wrong, if we are due to breakage of undo-log are losing real data. |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Question tags:
question asked: 04 Sep '15, 02:41
question was seen: 2,747 times
last updated: 04 Sep '15, 08:00
Is the error in the checkpoint log resolved when you shut down the database? (AFAIK, the checkpoint log is truncated then, except that v12 and above leave some pages there to re-claim a fitting space for the next start.)
When both database file and log are damaged, the usual road would be to go back to your latest backup and restore that...
To salvage data that has been modified since the backup status, you could try to use dbunload to unload the desired data, possibly with a list of tables that are excluded/included (options -e / -t). And you might try to use DBTRAN to generate at least parts of the data modification statements...
I used "dbtran -k D4w.log d4w.sql", but it returns data only until 22 June :(
The dbunload.exe does not start :(
The database file is damaged only the service log (Checkpoint log).
It is a pity that in such damaged real data can not be extracted :(