I have done this before myself, after they help you get the database up,
they make you swear on your mother's grave that you will
rebuild your entire database and give you a db2move command to do it with.
Before I did the db2move as a kind of backup and rebuilt a new database to
restore it to, I was not allowed to run a normal backup of my resurrected
database. Also, when doing the imports after the move, I ran into some
issues where I had to reset auto-increment fields because when you would add
data to them they would all try to start back at 1. If support ends up
saying that there is no hope with the LFH file, you might look at the
db2dart command, it allows you to read data directly from your containers
and dumps it out into export files for you.
Good Luck and sorry about those backups, sh-t happens.
"UDBDBA" <vi***********@gmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
Hi:
Call IBM Support, they can patch the SQLOGCTL.LFH (Log Header file).
You can then bring the db online and export the data out, run db2look
and pretty much get everything out that you would need to recreate.
Because, IBM does NOT support a patched DB, you will need to drop this
DB and create a new one.
HTH
Vijay