DB00605E - DBUTLTY COMM CONSOLE BAD CONTEXT - QUIESCE_DBID_SET YES

Products

• Datacom
• Datacom/AD
• Datacom/DB

Issue/Introduction

Running a Datacom console command to set a dbid to be quiesced:

QUIESCE_DBID_SET YES,5

returns error message:

DB00605E - DBUTLTY COMM CONSOLE BAD CONTEXT - QUIESCE_DBID_SET YES

This can also occur with QUIESCE_DBID_SET NO.

 

Environment

Release: 15.1

Cause

The DB00605E BAD CONTEXT message means the syntax of the command is correct but is not valid.
From the DB00605E message documentation:

If the error, however, was a context error, it means that although the command and the value aaaaaaaaaaaaaa in the message text are both valid, other rules make the combination invalid at this time.

Resolution

A common cause of the error is that QUIESCE_DBID_ALLOW YES was not specified in the MUF startup options. If this is the case, add the option and restart the MUF.

Another cause for the error is that a QUIESCE_DBID TXN is still in effect.

While a QUIESCE_DBID_APPLY TXN is still in effect, no new QUIESCE_DBID_SET commands can be run. Attempts to do so  will return the DB00605E error. This can be confirmed by checking in the MUF log if the last quiesce message is:

DB02924I - QUIESCE_DBID TXN IN EFFECT 

This means a QUIESCE_DBID_APPLY OFF command was not run to turn off the prior quiesce.

If a QUIESCE_DBID_APPLY OFF command was run the message issued would be:

DB02930I - QUIESCE_DBID OFF ENDED, WAS IN EFFECT 

To resolve the problem in this situation, run a QUIESCE_DBID_APPLY OFF command before running a new QUIESCE_DBID_SET commands.

Note that it is safe to run a  QUIESCE_DBID_APPLY OFF command even when a quiesce is not in effect. In this case  the message issued will be:

DB02930I - QUIESCE_DBID OFF ENDED, NOT NEEDED

Additional Information

See Datacom documentation sections QUIESCE_DBID_SET and QUIESCE_DBID_APPLY.

See article Using the Datacom QUIESCE_DBID processing commands.