By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,018 Members | 930 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,018 IT Pros & Developers. It's quick & easy.

Lost active log, can't connect to database..

P: n/a
Hi there,

our system lost its only active log. I get an I/O error
when connecting, referencing the log file and sql error 1036C
sqlstate 58030. (Its version 7.1)

Is there any way to get the database to create a new log, without
having to do a restore? we don't have a backup.

Thanks

Tiroloco

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
You can create a new database as same as current database , and then
copy the data files from current database to new database which you
created newly , and keep the two database have same environment (same
location ,same file name ,same database name same users ,etc). Try it .

Nov 12 '05 #2

P: n/a
should'nt be that easy. my guess is that database seed information will
play a vital role. also, as per my understanding, you can't just
provide one database any other database's containers and use them
(otherwise, anyone can play with any ones data if he or she has the
access to containers).

regards,
dotyet

James Hoo wrote:
You can create a new database as same as current database , and then
copy the data files from current database to new database which you
created newly , and keep the two database have same environment (same
location ,same file name ,same database name same users ,etc). Try it .


Nov 12 '05 #3

P: n/a
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

Nov 12 '05 #4

P: n/a
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

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.