DSNJ391I REMOVELOG OPERATION FAILED. THE SPECIFIED ACTIVE LOG DATA SET dataset-name CANNOT BE REMOVED. REASON: reason-string

Explanation

The REMOVELOG option of the SET LOG command has failed. The value of reason-string describes the cause of the failure.

dataset-name

The active log copy data set name specified in the SET LOG REMOVELOG command.

reason-string

BSDS ERROR

An error occurred either reading or updating the BSDS. Check SYSLOG for related errors. Depending on cause, reissue the command. Issue -DIS LOG DETAIL to determine if the log was flagged removal pending.

COPY2 IN SINGLE LOGGING MODE

COPY(2) was specified, but Db2 was started in single logging mode.

CURRENT LOG

The specified log data set name is the current active log data set.

DOES NOT EXIST

The specified log data set name could not be found in the BSDS for the specified COPY. Make sure the log data set name is spelled correctly and exists in the specified COPY.

INVALID STATUS

The log data set to be removed must have a status of REUSABLE.

NEXT CURRENT LOG

The specified log data set is the next available active log that the current log will switch to so cannot be removed.

NOT SUPPORTED

The Db2 system is at a release in which REMOVELOG is not supported.

NOTIFY ERROR

Indicates a failure to notify data sharing members for the active log being removed. The active log will still be marked removal pending. The command should be reissued.

OFFLINE REQUIRED

Subsystem parameter OFFLOAD must be set to YES.

SOURCE OR PROXY

The Db2 member is defined as a SOURCE or PROXY member in GDPS Active/Active ZDL configuration and is not allowed to remove active log data sets online. The user can use DSNJU003 to delete the active log data set offline.