Can't connect to database, missing log files

[VikingDK]

Hi all

Our server (DB2 UDB 9.1 fp4) crashed earlier today while running a job, after a reboot everything looked fine again, except that now the database is no longer accessible. The log files are missing in SQLOGDIR and I'm unable to restore them.

The error I'm getting is this one:

[IBM][CLI Driver] SQL1036C An I/O error occurred while accessing
the database. SQLSTATE=58030

Only solution I could find was to do a database restore which I'm not very keen on doing, since it's gonna rollback 5 days and I've done alot of work on the database the past few days.

Please tell me there is a way to force DB2 to ignore or recreate those logs so we can connect to the database again.

On a side note, I'm not very experienced with DB2, so be gentle :)

Thanks in advance
Jimmi

[SuperKuper]

Call IBM - I recall they have a way to bypass crash recovery on startup. You send them one of the control files, they change it and send back to you. In the future you may want to consider using "mirror" logs.

[Shashank1984]

In this case you need to provide us/IBM SQLOGCTL.LFH.
Lemme give you what it's about ...
Resetting the SQLOGCT.LFH is a task which, allow you to connect to the
Database. We expect that you WILL export the data and REBUILD the
database via data imports. The reset is only done in cases where
customer do not have any backups and associated logs for roll forward.

In a reset of the LFH file we are essentially tricking the Database,
i.e. we change the consistency status to YES, and we also not look for
any transaction logs (Normally during crash recovery all the
transactions in active log files are read for replay purposes and they
should be available). So in essence we bypass crash recovery and
compromise with the database integrity.

Thanks,
Shashank Kharche