Oracle® Enterprise Manager Connector Framework Integration Guide 10g Release 2 (10.2.0.2) Part Number B31191-01 |
|
|
View PDF |
This chapter provides all Connector Framework-specific error messages and debugging information. The errors are returned in the response model.
Table 3–1 provides error codes, descriptions, causes, and suggested actions for all Connector Framework error messages.
Table 3-1 Error Messages
Error Code | Description | Cause | Action |
---|---|---|---|
CNTR-0001 |
Authentication failed. |
The credential to log in to Enterprise Manager is incorrect. |
Correct the Enterprise Manager credential element in the request. |
CNTR-0002 |
In setModel, the requested aggregate target list is of size 0. This operation is not supported. |
There is no aggregate target in the setModel request. |
Correct the request model to include two aggregate targets: one of type cluster, and the other of type rac_database. |
CNTR-0003 |
The requested aggregate targets have a different number of targets. |
The current cluster aggregate target and rac_database aggregate target have a different number of member targets. |
Make sure the numbers of members of the current cluster aggregate target and the rac_database aggregate target are the same. |
CNTR-0004 |
A target name or target type is null. |
The target name or type element is NULL in the request model for getModel. |
Correct the target name or target type in the request model. |
CNTR-0005 |
Property unrecognized. |
There is unrecognized property in the request model for getModel. |
Remove the unrecognized property. |
CNTR-0006 |
An aggregate target name or aggregate target type is null. |
The name or type of element of an aggregate target is NULL. |
Correct the name or type of the aggregate target in the request model. |
CNTR-0007 |
An aggregate target type is unrecognized. |
The aggregate target type is something other than cluster and rac_database. |
Correct the aggregate target type. Only two types are supported in this release: cluster and rac_database. |
CNTR-0008 |
Invalid request model. |
The request model is invalid. |
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 |
Oracle Clusterware or RAC aggregate target is not found in model. |
Either the cluster aggregate target or the rac_database aggregate target is missing in the request model. |
Add the missing aggregate target. |
CNTR-0010 |
No software image found. |
No software library image was found based on the description of the model. |
Correct the name of the software library image, or make sure the image is available in the Enterprise Manager software library. |
CNTR-0011 |
No existing node to run add node job. |
No existing node can be found to run some steps of the add node job. |
Correct the request model to make sure all existing nodes are specified correctly in the request model. |
CNTR-0012 |
No host credential defined. |
No credential was specified for the RAC nodes. |
Add the credentials for the RAC nodes. |
CNTR-0013 |
Invalid member database name. The member database target name should be <rac_name>_<instance_name>. |
The name of the member target of the rac_database aggregate target does not follow the <rac_name>_<instance_name> naming rule. |
Correct the name of the member target of the rac_database aggregate target. |
CNTR-0014 |
No storage specified during the RAC creation. |
The storage element is missing during the RAC creation request. |
Add the storage element in the request model. |
CNTR-0015 |
This action is not supported. Delete one node. |
The number of nodes in the request model is less than the number of nodes in the current model minus one. |
Correct the response model by deleting only one node. |
CNTR-0016 |
Aggregate targets in the request model have different numbers of targets. |
The cluster aggregate target and rac_database aggregate target have a different number of member targets. |
Correct the request model with the correct member targets for both the cluster aggregate target and rac_database aggregate target. |
CNTR-0017 |
Action not supported: to create RAC, only one node is allowed in the request model. |
More than one node was specified in the request when the RAC database did not exist yet. |
Correct the request model to use only one node for the new RAC database. |
CNTR-0018 |
Error in request model: please check target names of the aggregate targets. |
The member targets of the aggregate targets do not match those in the Enterprise Manager repository. |
Correct the request model with the correct member target names. |
CNTR-0019 |
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. |
Correct the request model to indicate a provisioning action. |
CNTR-0020 |
Action not supported: please add one node at a time. |
The number of nodes in the request model is more than the number of nodes in the current model plus one. |
Correct the request model by adding only one node. |
CNTR-0022 |
Error in 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. |
Correct the host attribute of the member target of the rac_database aggregate target. |
CNTR-0023 |
Error in host of 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. |
Correct the host attribute of the member target of the cluster aggregate target. |
CNTR-0024 |
Conflict in host of Oracle Clusterware and RAC aggregate target of the request model. |
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. |
Correct the host attribute of the member target of the cluster and rac_database aggregate target. |
CNTR-0025 (Windows only) |
Property sl_OHPartitionsAndSpace_valueFromDlg is not found. |
The sl_OHPartitionsAnd Space_valueFromDlg property is missing from the cluster aggregate target properties. |
Add the sl_OHPartitionsAnd Space_valueFromDlg property to the cluster aggregate target properties in the request model. |
CNTR-0026 (Windows only) |
Property ret_PrivIntrList is not found. |
The ret_PrivIntrList property is missing from the cluster aggregate target properties. |
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 3–2:
Table 3-2 Message Types and Corresponding Code Names
Message Type | Code Option |
---|---|
Warning |
WARN |
Error |
ERROR |
Debugging |
DEBUG |
Information |
INFO |
The following example shows the insertion of DEBUG in the following lines of:
$ORACLE_HOME/sysman/config/emomslogging.properties
to receive debugging information:
log4j.appender.emlogAppender.Threshold = DEBUG log4j.rootCategory=DEBUG, emlogAppender, emtrcAppender
The debug messages from the Connector Framework are displayed in the following file:
$ORACLE_HOME/sysman/log/emoms.trc
The messages are prefixed with "connector.base".
The Connector Framework submits a job for each provisioning request. After you receive the job ID from your request, use the job ID to search Enterprise Manager jobs to obtain more job details. To look for a job in Enterprise Manager, select the Jobs tab on the Enterprise Manager console.