My approach will be :
1) Copy the current active log directory to some location, just in case you loose the logs ..
2) Check the db2diag.log file to see which tablespace reports the error ..
3) From the same backup image, restore only that tablespace ...
4) ROLLFORWARD QUERY to see what the status is ...
If it is beyond the point I want, I'll prefer to go back to the full database restore and use ROLLFORWARD to some point following the backup end timestamp and see what the message says and take it from there ...
Cheers
Sathyaram
Quote:
Originally posted by niran
I am facing problems with a database rollforward db to end of logs. The log files are backed up using a user exit and so has timestamp appended to the SQL0112918.LOG files. However I don't have user exit enabled on my machine and so the rollforward is not able to know these log files having the timestamp as the extension. Due to time constraints, I restored these files from TSM server to a dummy directoy and then copied them to the active log directory and renamed them to have just the .LOG extension and issued the command:
rollforward db <dbname> to end of logs.
However the rollforward was still looking for the next file. I knew that I have provided the last log file (as listed in the history information) and so I issued a rollforward complete command.
The database was still in the rollforward state. I stopped db2 (db2stop) and then db2start. This took the database out of rollforward state and restore pending state but now I have a diff problem now.
I cannot connect to the database, it comes out with SQL0293N error. which is error accessing a table space container. ANY HELP PLEASE !!!!
|