Unable to perform online checkpoints on Solaris

[Dan Newman]

My customer is running Solaris 10, Ingres 9.1.1 for x64 AMD. They have been attempting to perform online checkpoints using the command

ckpdb +j my_db

but keep getting the error message:

E_DM110D_CPP_DB_BUSY Database is currently being used.
Database lock conflict.

The command does work when all clients have been manually disconnected. However, they require creation of checkpoints while the system is online.

Is this the wrong command?
Is this a known issue on this platform with a patch available?

Thanks in advance.

[maspa05]

The +j is trying to switch on journalling which requires an offline checkpoint.

Check the journalling status of the database and if it's already journalled then there's no need to use the +j and ckpdb will do an online checkpoint if there are users connected.

[seran01]

Hello Dan:

If you wish to take online checkpoints, the command is :

ckpdb <my_db>

The command that you stated :

ckpdb +j <my_db>

---- which means, lock the database, and turn on journaling

is for off-line checkpoints.

You need to find some time, to log off all 'client' or user connections, and once the database is free, you can take a 'ckpdb +j <my_db> .

Then the next checkpoints, with the command, ckpdb <my_db>, will be online.

Regards,
Anton

[magxa01]

Hello Dan

This command means that you want to change the behaviour for your journaling mode :

When you specify the flag
+j|-j
Enables or disables journaling for a database. When this flag is not specified, current journaling status of the database is maintained.
If you specify this flag, the checkpoint is performed offline.
=============
so you'll have to disconnect or removed the existing sessions with IPM and run ckpdb
and when you'll run your next ckpdb you'll just have to do the command :

ckpdb my_db


I hope this help !
Regards.

[Dan Newman]

So even if journalling is already switched on, using the +j flag will cause problems if there are users connected?

[seran01]

Hello Dan:

That is correct, ckpdb +j will attempt to lock the database, and it will generate error
messages, if the database is busy and/or users/applications are connected to the database.

ckpdb +j means off line, no users connected to the database.

If the database is already journaled, you do not need to use +j flag with ckpdb.

The +j is either to turn on journaling or to force a new set of journal files.

Otherwise, if all you need is online checkpoints, you do not need to use +j.

Regards,
Anton

[magxa01]

Yes same for -j option if you want to stop the journaling of your database