Resolving errors when using CCI to perform Data Retention Utility operations (SSB1:2E31/B9BF/B9BD)

If an error occurs while using CCI to perform Data Retention Utility operations, you might identify the cause of the error by referring to the log appearing on the CCI window or the CCI operation log file.

The CCI operation log file is stored in the following directory. 

/HORCM/log*/curlog/horcmlog_HOST/horcm.log

where

  • * is the instance number.
  • HOST is the host name.

The following is an example of a log entry in the CCI window.

The following table provides troubleshooting information for Data Retention Utility operations performed using CCI.

Error code (SSB2)

Description

9100

The command cannot be executed because user authentication is not performed.

B9BD

The setting failed because the specified volume does not exist.

B9C2

The specified volume is a command device.

B9C4

The command was rejected due to one of the following reasons:

  • The specified volume is a virtual volume.
  • The specified volume is a pool volume.
  • The specified volume is an secondary volume of Universal Replicator.
  • The specified volume is a journal volume.
  • The specified volume is a primary volume or secondary volume of ShadowImage.
  • The consumed capacity exceeded the licensed capacity.
  • The access attribute cannot be changed because the data retention term is set.
  • The specified volume is a command device.
  • The specified volume is in the PAIR or COPY status.
  • The specified volume does not exist.
  • The S-VOL Disable attribute is set to the specified volume.
  • The reserve function cannot be canceled using CCI.
  • The specified volume is a quorum disk for global-active device, so that the requested setting of Data Retention Utility cannot be performed.
  • The specified volume is in an accelerated compression-enabled parity group.
  • The specified volume is a deduplication system data volume.

B9C7

Data Retention Utility is not installed.

B9C9

The consumed capacity exceeded the licensed capacity.

B9CA

The command was rejected due to one of the following reasons:

  • Fewer days are set as the data retention term.
  • More than 60 years are set as the data retention term.
  • An interface other than Java® updated the settings while Data Retention Utility was in the process of changing them. A conflict occurred between Java and the other interface.

B9CB

The retention term cannot be set because the access attribute is read/write.

Parent Topic