5 Error Messages and Debugging

This chapter provides all Management Connector specific error messages and debugging information. The errors are returned in the response model.

Error Messages

This section provides error codes, descriptions, causes, and suggested actions for all Connector Framework error messages.

CNTR-0001: Cause: Authentication failed. The credential to log in to Enterprise Manager is incorrect.; Action: Correct the Enterprise Manager credential element in the request.

CNTR-0002: Cause: In setModel, the requested aggregate target list is of size 0. This operation is not supported. In setModel, the requested aggregate target list is of size 0. This operation is not supported.; Action: Correct the request model to include two aggregate targets: one of type cluster, and the other of type rac_database.

CNTR-0003: Cause: The current cluster aggregate target and rac_database aggregate target have a different number of member targets.; Action: Make sure the numbers of members of the current cluster aggregate target and the rac_database aggregate target are the same.

CNTR-0004: Cause: The target name or type element is NULL in the request model for getModel.; Action: Correct the target name or target type in the request model.

CNTR-0005: Cause: There is an unrecognized property in the request model for getModel.; Action: Remove the unrecognized property.

CNTR-0006: Cause: The name or type of element of an aggregate target is NULL.; Action: Correct the name or type of the aggregate target in the request model.

CNTR-0007: Cause: The aggregate target type is something other than cluster and rac_database.; Action: Correct the aggregate target type. Only two types are supported in this release: cluster and rac_database.

CNTR-0008: Cause: The request model is invalid.; Action: Correct the request model. Make sure the request model has either zero or two aggregate targets (one of type cluster and one of type rac_database). If aggregate targets are included, make sure the numbers of targets in the two aggregate targets are the same with the same set of hosts. Make sure the name and host elements of each target in the cluster aggregate target are the same.

CNTR-0009: Cause: Either the cluster aggregate target or the rac_database aggregate target is missing in the request model.; Action: Add the missing aggregate target.

CNTR-0010: Cause: No software library image was found based on the description of the model.; Action: Correct the name of the software library image, or make sure the image is available in the Enterprise Manager software library.

CNTR-0011: Cause: No existing node could be found to run some steps of the add node job.; Action: Correct the request model to make sure all existing nodes are specified correctly in the request model.

CNTR-0012: Cause: No credential was specified for the RAC nodes.; Action: Add the credentials for the RAC nodes.

CNTR-0013: Cause: The name of the member target of the rac_database aggregate target does not follow the <rac_name>_<instance_name> naming rule.; Action: Correct the name of the member target of the rac_database aggregate target.

CNTR-0014: Cause: The storage element was missing during the RAC creation request.; Action: Add the storage element in the request model.

CNTR-0015: Cause: The number of nodes in the request model is less than the number of nodes in the current model minus one.; Action: Correct the response model by deleting only one node.

CNTR-0016: Cause: The cluster aggregate target and rac_database aggregate target have a different number of member targets.; Action: Correct the request model with the correct member targets for both the cluster aggregate target and rac_database aggregate target.

CNTR-0017: Cause: More than one node was specified in the request when the RAC database did not exist yet.; Action: Correct the request model to use only one node for the new RAC database.

CNTR-0018: Cause: The member targets of the aggregate targets do not match those in the Enterprise Manager repository.; Action: Correct the request model with the correct member target names.

CNTR-0019: Cause: Nothing to do: there are no member differences between the current and requested model. The members of the current model inside Enterprise Manager are the same as the one in the request. The connector cannot infer any action.; Action: Correct the request model to indicate a provisioning action.

CNTR-0020: Cause: The number of nodes in the request model is more than the number of nodes in the current model plus one.; Action: Correct the request model by adding only one node.

CNTR-0022: Cause: There is an error in the host of RAC aggregate target of the request model. The host attribute of the member targets does not match the host attribute in the Enterprise Manager repository.; Action: Correct the host attribute of the member target of the rac_database aggregate target.

CNTR-0023: Cause: There is an error in the host of the Oracle Clusterware aggregate target of the request model. The host attribute of the member targets does not match the host attribute in the Enterprise Manager repository.; Action: Correct the host attribute of the member target of the cluster aggregate target.

CNTR-0024: Cause: The host attribute of the member target of the cluster aggregate target does not match the host attribute for the corresponding member target of the rac_database aggregate target.; Action: Correct the host attribute of the member target of the cluster and rac_database aggregate targets.

CNTR-0025 (Windows only): Cause: The sl_OHPartitionsAndSpace_valueFromDlg property is missing from the cluster aggregate target properties.; Action: Add the sl_OHPartitionsAndSpace_valueFromDlg property to the cluster aggregate target properties in the request model.

CNTR-0026 (Windows only): Cause: The ret_PrivIntrList property is missing from the cluster aggregate target properties.; Action: Add the ret_PrivIntrList property to the cluster aggregate target properties in the request model.

The Connector Framework uses the log4j logging utility to log the types of messages shown in Table 5–1:

Table 5-1 Message Types and Corresponding Code Names

The following example shows the insertion of DEBUG in the following file:

$ORACLE_HOME/sysman/config/emomslogging.properties

Use the following emctl command to set the debug level as shown below:

emctl set property -name log4j.rootCategory -value "DEBUG, emlogAppender, emtrcAppender" -module emoms

Enter the SYSMAN password when prompted.

The debug messages from the Connector Framework are displayed in the following file:

$INSTANCE_HOME/sysman/log/emoms.trc