Tuesday 15 May 2012

ORA-29818: column name not properly specified

ORA-29818: column name not properly specified

Cause: Name of the column should contain the table and the column name.

Action: Specify a valid column name.

ORA-29817: non-supported option with disassociate statement

ORA-29817: non-supported option with disassociate statement

Cause: The type of object specified is not supported with the disassociate statistics statement.

Action: Use a object type which is supported with the disassociate command.

ORA-29816: object being disassociated is not present

ORA-29816: object being disassociated is not present

Cause: Object which is being disassociated is not present.

Action: Ensure that the object which needs to be disassociated is present.

ORA-29815: object being associated is not present

ORA-29815: object being associated is not present

Cause: The object for which the association is being defined is not present.

Action: Ensure that all the objects for which the association is being defined are present.

ORA-29814: expecting USING or DEFAULT keyword

ORA-29814: expecting USING or DEFAULT keyword

Cause: Expecting the USING or DEFAULT keyword after the names of object(s).

Action: Provide the USING or DEFAULT keyword.

ORA-29813: non-supported object type with associate statement

ORA-29813: non-supported object type with associate statement

Cause: The type of object specified is not supported with the associate statistics statement.

Action: Use a valid object type with the associate command.

ORA-29812: incorrect object name specified

ORA-29812: incorrect object name specified

Cause: The specified name is not a valid name.

Action: Specify the correct name of the object with for which an association needs to be defined.

ORA-29811: missing STATISTICS keyword

ORA-29811: missing STATISTICS keyword

Cause: This is not a valid option with the ASSOCIATE command.

Action: Specify STATISTICS keyword after the ASSOCIATE command.

ORA-29810: inadequate operator privileges

ORA-29810: inadequate operator privileges

Cause: The user does not have the appropriate privileges to perform the specified operation on the operator.

Action: Grant the appropriate privileges to the user and then reissue the statement.

ORA-29809: cannot drop an operator with dependent objects

ORA-29809: cannot drop an operator with dependent objects

Cause: The operator which is being dropped has some dependent objects.

Action: Either drop the dependent objects first and then issue the DROP OPERATOR command or specify the FORCE option with DROP OPERATOR.

ORA-29808: specified primary operator binding does not exist

ORA-29808: specified primary operator binding does not exist

Cause: The specified binding for the primary operator does not exist.

Action: Ensure that the specified binding for the primary operator exists.

ORA-29807: specified operator does not exist

ORA-29807: specified operator does not exist

Cause: The operator which has been specified does not exist.

Action: Ensure that the operator that has been specified does exist.

ORA-29806: specified binding does not exist

ORA-29806: specified binding does not exist

Cause: The operator binding which has been specified does not exist.

Action: Ensure that the operator binding that has been specified does exist.

ORA-29805: missing COLUMN keyword

ORA-29805: missing COLUMN keyword

Cause: Keyword COLUMN is expected .

Action: Either specify the COLUMN keyword or specify another option.

ORA-29804: missing DATA keyword

ORA-29804: missing DATA keyword

Cause: The DATA keyword has not been specified.

Action: Specify the DATA keyword or check the SQL statement.

ORA-29803: missing ANCILLARY keyword

ORA-29803: missing ANCILLARY keyword

Cause: The ANCILLARY keyword has not been specified.

Action: Specify the ANCILLARY keyword or check the SQL statement.

ORA-29802: missing CONTEXT keyword

ORA-29802: missing CONTEXT keyword

Cause: The CONTEXT keyword has not been specified.

Action: Specify the CONTEXT keyword or check the SQL statement.

ORA-29801: missing RETURN keyword

ORA-29801: missing RETURN keyword

Cause: The RETURN keyword has not been specified.

Action: Specify the RETURN keyword or check the SQL statement.

ORA-29800: invalid name for operator

ORA-29800: invalid name for operator

Cause: The name specified for the operator is incorrect.

Action: Specify a correct name for the operator.

ORA-29760: instance_number parameter not specified

ORA-29760: instance_number parameter not specified

Cause: The init.ora file did not contain a value for the instance_number which is required to identify this instance to other instances of the database running on the same cluster

Action: Assign a value to the instance_number parameter in the init.ora parameter file

ORA-29746: Cluster Synchronization Service is being shut down.

ORA-29746: Cluster Synchronization Service is being shut down.

Cause: The administrator has shut down the Cluster Synchronization Service daemon. This error message is intended to be informative to users on the status of the service.

Action: Check the log file of the Cluster Synchronization Service daemon to verify the state of the service.

ORA-29741: IMR active for some, but not all members of cluster

ORA-29741: IMR active for some, but not all members of cluster

Cause: The IMR feature is not active for this instance, but is active for another instance in the cluster database.

Action: Ensure that all instances have the same value for the _imr_active init.ora parameter

ORA-29740: evicted by member string, group incarnation string

ORA-29740: evicted by member string, group incarnation string

Cause: This member was evicted from the group by another member of the cluster database for one of several reasons, which may include a communications error in the cluster, failure to issue a heartbeat to the control file, etc.

Action: Check the trace files of other active instances in the cluster group for indications of errors that caused a reconfiguration.

ORA-29707: inconsistent value string for initialization parameter string with other instances

ORA-29707: inconsistent value string for initialization parameter string with other instances

Cause: The value of the initialization parameter in error must be identical on all Oracle cluster database instances and was not.

Action: Check your INIT.ORA files on all instances and ensure that the initialization parameters in error have the same value.

ORA-29706: incorrect value string for parameter ACTIVE_INSTANCE_COUNT

ORA-29706: incorrect value string for parameter ACTIVE_INSTANCE_COUNT

Cause: The ACTIVE_INSTANCE_COUNT parameter must be set to 1 in a two node cluster database configuration or unspecified if a secondary instance is not needed.

Action: Check your initialization parameter files and correct the value of the ACTIVE_INSTANCE_COUNT parameter. If you are configuring a two node primary or secondary cluster database, set this value to 1. Otherwise, do not specify any value for the parameter.

ORA-29705: ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances

ORA-29705: ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances

Cause: The value of the ACTIVE_INSTANCE_COUNT parameter must be the same in all Oracle cluster database instances.

Action: Check your initialization parameter files in all instances and ensure that the ACTIVE_INSTANCE_COUNT parameter has the same value. Then restart the instance.

ORA-29704: cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release

ORA-29704: cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release

Cause: The ACTIVE_INSTANCE_COUNT parameter was specified when one of the instances in the cluster was running Oracle 8.1.5 or an earlier release.

Action: Restart the instance without specifying the ACTIVE_INSTANCE_COUNT parameter. Or, upgrade all instances to Oracle 8.1.6 or later release and then specify the parameter.

ORA-29703: error occurred in global enqueue service operation

ORA-29703: error occurred in global enqueue service operation

Cause: An unexpected error occurred while performing a global enqueue service operation.

Action: Check oracle trace files for errors.

ORA-29702: error occurred in Cluster Group Service operation

ORA-29702: error occurred in Cluster Group Service operation

Cause: An unexpected error occurred while performing a CGS operation.

Action: Verify that the LMON process is still active. Also, check the Oracle LMON trace files for errors.

ORA-29701: unable to connect to Cluster Manager

ORA-29701: unable to connect to Cluster Manager

Cause: Connect to CM failed or timed out.

Action: Verify that the CM was started. If the CM was not started, start it and then retry the database startup. If the CM died or is not responding, check the Oracle and CM trace files for errors.

ORA-29665: Java thread deadlock detected

ORA-29665: Java thread deadlock detected

Cause: The Java VM has detected a thread deadlock.

Action: Modify the Java program to avoid the deadlock condition.

ORA-29664: Unable to generate the helper class for the defined type

ORA-29664: Unable to generate the helper class for the defined type

Cause: The helper class used for supporting SQLJ Object Type is not generated.

Action: No Action is required.

ORA-29663: Unable to find a method that matches one or more of the functions

ORA-29663: Unable to find a method that matches one or more of the functions

Cause: The EXTERNAL NAME option of one or more functions do not match any method in the defined class.

Action: Make sure the EXTERNAL NAME option of each function matches a method in the defined in the defined class.

ORA-29662: Unable to find a field that matches one or more of the attributes

ORA-29662: Unable to find a field that matches one or more of the attributes

Cause: The EXTERNAL NAME option of one or more attributes do not match any fields in the defined class.

Action: Make sure the EXTERNAL NAME option of each attribute matches a field in the defined in the defined class.

ORA-29661: Unable to find the superclass of the defined in the EXTERNAL NAME

ORA-29661: Unable to find the superclass of the defined in the EXTERNAL NAME

Cause: The class is not loaded in the database.

Action: Make sure the superclass of the EXTERNAL NAME is loaded in the the database.

ORA-29660: Unable to find the class defined in the EXTERNAL NAME clause

ORA-29660: Unable to find the class defined in the EXTERNAL NAME clause

Cause: The class is not loaded in the database.

Action: Make sure the EXTERNAL NAME corresponds to a loaded class in the the database.

ORA-29659: SQLJ Object Type validation failed to get default connection

ORA-29659: SQLJ Object Type validation failed to get default connection

Cause: Unable to connect using the JDBC default connection.

Action: No action required.

ORA-29658: EXTERNAL NAME clause is not compatible with its supertype

ORA-29658: EXTERNAL NAME clause is not compatible with its supertype

Cause: The EXTERNAL NAME clause of the type is not a subclass of the supertype EXTERNAL NAME.

Action: Make sure the EXTERNAL NAME clause of the type is a subclass of the EXTERNAL NAME of its supertype.

ORA-29657: class defined in EXTERNAL NAME clause is used in another subtype

ORA-29657: class defined in EXTERNAL NAME clause is used in another subtype

Cause: The supertype has an existing type that has the same value for the EXTERNAL NAME.

Action: Make sure the EXTERNAL NAME clause is unique among subtypes.

ORA-29656: Invalid option for USING

ORA-29656: Invalid option for USING

Cause: The class has to implement the required interface for the value of the option for USING.

Action: Make sure the USING clause is supported.

ORA-29655: USING clause is incompatible with its supertype

ORA-29655: USING clause is incompatible with its supertype

Cause: The USING clause of a type has to be the same as its supertype or compatible with it.

Action: Make sure the USING clause is compatible with its supertype.

ORA-29558: JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.

ORA-29558: JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.

Cause: JAccelerator (NCOMP) is not installed.

Action: Please refer to the Post-installation Tasks section in the Database Install Guide for instructions on how to install JAccelerator (NCOMP).

ORA-29557: Java system class string cannot be modified

ORA-29557: Java system class string cannot be modified

Cause: A command was attempted that would have modified a Java system class.

Action: No action required.

ORA-29556: object type has changed

ORA-29556: object type has changed

Cause: A database object name that named a Java source, class, or resource now names an object of a different type.

Action: No action required.

ORA-29555: Java source, class or resource is not allowed here

ORA-29555: Java source, class or resource is not allowed here

Cause: A Java source, class, or resource was specified in an inappropriate place in a statement.

Action: Make sure the name is correct or remove it.

ORA-29554: unhandled Java out of memory condition

ORA-29554: unhandled Java out of memory condition

Cause: The session encountered an out of memory condition in Java from which it could not recover. Java session state was cleared.

Action: No action required.

ORA-29553: class in use: string.string

ORA-29553: class in use: string.string

Cause: An attempt was made to modify a Java class that is in use in the current call.

Action: Correct the code in use in this call.

ORA-29552: verification warning: string

ORA-29552: verification warning: string

Cause: An attempt was made to create a Java class object with bytecodes that caused the Java verifier to issue a warning.

Action: It is possible that the Java class was created from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using - in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver.

ORA-29551: could not convert string to Unicode

ORA-29551: could not convert string to Unicode

Cause: A string in the database character set could not be converted to Unicode, as required for use by Java.

Action: Correct the string.

ORA-29550: Java session state cleared

ORA-29550: Java session state cleared

Cause: The Java state in the current session became inconsistent and was cleared.

Action: No action required.

ORA-29549: class string.string has changed, Java session state cleared

ORA-29549: class string.string has changed, Java session state cleared

Cause: A class in use by the current session was redefined or dropped, invalidating the current Java session state and requiring that it be cleared.

Action: No action required.

ORA-29548: Java system class reported: string

ORA-29548: Java system class reported: string

Cause: A command that uses a Java system class was aborted due to an error reported by the Java system class.

Action: Correct the error that was reported.

ORA-29547: Java system class not available: string

ORA-29547: Java system class not available: string

Cause: An attempt was made to use a command that requires a Java system class that was not yet present or was invalid.

Action: Load the system classes, or do not use the command.

ORA-29546: badly formed resource: string

ORA-29546: badly formed resource: string

Cause: An attempt was made to create a Java resource object with data that was rejected by the Java verifier.

Action: Correct the data.

ORA-29545: badly formed class: string

ORA-29545: badly formed class: string

Cause: An attempt was made to create a Java class object with bytecodes that were rejected by the Java verifier.

Action: It is possible that an attempt was made to create the Java class from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using - in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver.

ORA-29544: invalid type

ORA-29544: invalid type

Cause: The type argument in a call to a Java export or import command did not have a recognized value.

Action: Correct the value.

ORA-29543: Java command string not yet implemented

ORA-29543: Java command string not yet implemented

Cause: An attempt was made to use a Java command that is not yet implemented.

Action: Do not use the command.

ORA-29542: class string already defined by source string

ORA-29542: class string already defined by source string

Cause: An attempt was made to create a Java source object that would define a class that is already defined by a different Java source object.

Action: Either drop the old source or modify the new source.

ORA-29541: class string.string could not be resolved

ORA-29541: class string.string could not be resolved

Cause: An attempt was made to execute a method in a Java class that had not been previously and cannot now be compiled or resolved successfully.

Action: Adjust the call or make the class resolvable.

ORA-29540: class string does not exist

ORA-29540: class string does not exist

Cause: Java method execution failed to find a class with the indicated name.

Action: Correct the name or add the missing Java class.