423,321 Members | 1,167 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 423,321 IT Pros & Developers. It's quick & easy.

Starting DB2 unix when Log Files Accidently Deleted

P: 2
I was doing a redirected restore in test from a backup of a prod DB. The application was stopped for the restore, the restore was to a DB called ABC.

I deactivated the ABC DB, and went to delete the logs files. I cut & paste the log location from a comment in the restore redir job by mistake and it had the wrong DB name in it, so I ended up deleting the log files for DB ABC2. Now that DB is dead :(

Is the only solution to restore the ABC2 DB?

Since there was no activity on the DB whose logs I deleted isn't there some way to get DB2 to create a new log file and go forward?

We never do roll forward restores, so we don't need the logs I deleted for restores.
Feb 23 '18 #1
Share this Question
Share on Google+
2 Replies


Expert 100+
P: 921
Is the error the same as given here?:
https://bytes.com/topic/db2/answers/...sing-log-files
Feb 25 '18 #2

P: 2
Similar. We had to restore the DB we hadn't planned on restoring. I don't like this process of manually deleting the log files, which seams extremely risky. I'm finding it hard to believe this is IBM's design to manually delete the transaction log files to do a restore but I'm new to DB2 on Unix and never did this on mainframe (where all my experience is).
Feb 26 '18 #3

Post your reply

Sign in to post your reply or Sign up for a free account.