Recovering from a DB2 Crash

[subhbhav]

Hi,

Is there any way to get a db2 9.1 Windows UDB database which is in
inconsistent state to start without recovery?

We were loading data from a source and the database crashed. The
Server was restarted after this. DB2 has completed the forward phase
of crash recovery but the rollback phase is taking time. We are using
circular logging.

We have loaded a large number of tables during the weekend before the
last backup. In case the recovery is not successful, I would like to
start the database, drop and reload the last few tables and manually
set the database state to consistent. Is there an easy way to do
this? Any pitfalls?

Regards

Subhash

The db2dialog had an error message that logfile is full before the
shutdown. We are using DB2 9.1 Workgroup Edition on Windows 2003
server.

[shenanwei]

1. Change circular logging to Archive
2. Increase the log file size and number of logs
3. using load SAVECOUNT, ROWCOUNT

On Mar 12, 12:12 pm, [e-mail] wrote:

Hi,

Is there any way to get a db2 9.1 Windows UDB database which is in
inconsistent state to start without recovery?

We were loading data from a source and the database crashed. The
Server was restarted after this. DB2 has completed the forward phase
of crash recovery but the rollback phase is taking time. We are using
circular logging.

We have loaded a large number of tables during the weekend before the
last backup. In case the recovery is not successful, I would like to
start the database, drop and reload the last few tables and manually
set the database state to consistent. Is there an easy way to do
this? Any pitfalls?

Regards

Subhash

The db2dialog had an error message that logfile is full before the
shutdown. We are using DB2 9.1 Workgroup Edition on Windows 2003
server.

[Phil Sherman]

Circular logging means no online backup so your backup must be offline.

You can restore your last backup and will loose everything after the backup.

Phil Sherman
su******@gmail.com wrote:

Hi,

Is there any way to get a db2 9.1 Windows UDB database which is in
inconsistent state to start without recovery?

We were loading data from a source and the database crashed. The
Server was restarted after this. DB2 has completed the forward phase
of crash recovery but the rollback phase is taking time. We are using
circular logging.

We have loaded a large number of tables during the weekend before the
last backup. In case the recovery is not successful, I would like to
start the database, drop and reload the last few tables and manually
set the database state to consistent. Is there an easy way to do
this? Any pitfalls?

Regards

Subhash

The db2dialog had an error message that logfile is full before the
shutdown. We are using DB2 9.1 Workgroup Edition on Windows 2003
server.

[dotyet]

from the db engine's perspective, you are "deliberately" asking it to
forgo the consistency factor. I don't think it will allow that. you
"will | must" have to perform crash recovery, there is no other
choice. unless you want to restore an old copy or recreate the whole
db. maybe you may want to have a look at the db2 tool called db2dart.
i think there is some option/flag to change the consistency of the db,
but i am not sure. have a look at the documentation.

rgds,
dotyet
On Mar 12, 12:12 pm, [e-mail] wrote:

Hi,

Is there any way to get a db2 9.1 Windows UDB database which is in
inconsistent state to start without recovery?

We were loading data from a source and the database crashed. The
Server was restarted after this. DB2 has completed the forward phase
of crash recovery but the rollback phase is taking time. We are using
circular logging.

>
We have loaded a large number of tables during the weekend before the
last backup. In case the recovery is not successful, I would like to
start the database, drop and reload the last few tables and manually
set the database state to consistent. Is there an easy way to do
this? Any pitfalls?

Regards

Subhash

The db2dialog had an error message that logfile is full before the
shutdown. We are using DB2 9.1 Workgroup Edition on Windows 2003
server.