ORA-24316: illegal handle type

ORA-24316: illegal handle type

Cause: An illegal handle type was specified.

Action: Consult user manual to specify a valid handle type.

ORA-24315: illegal attribute type

ORA-24315: illegal attribute type

Cause: An illegal attribute type was specified for the handle.

Action: Consult user manual to specify an attribute valid for this handle.

ORA-24314: service handle not initialized

ORA-24314: service handle not initialized

Cause: The server context does not done exist.

Action: Establish the server context in the service context.

ORA-24313: user already authenticated

ORA-24313: user already authenticated

Cause: A user has already been authenticated on this service handle.

Action: Terminate the service context before using it for another user.

ORA-24312: illegal parameters specified for allocating user memory

ORA-24312: illegal parameters specified for allocating user memory

Cause: An illegal size or null pointer was specified for user memory.

Action: Specify a legal size and a valid pointer for user memory.

ORA-24311: memory initialization failed

ORA-24311: memory initialization failed

Cause: Cannot initialize user memory.

Action: Contact customer support.

ORA-24310: length specified for null connect string

ORA-24310: length specified for null connect string

Cause: The connect string is null, but a length was specified for it.

Action: Set length to zero if connect string is null.

ORA-24309: already connected to a server

ORA-24309: already connected to a server

Cause: This server handle is already attached to a server.

Action: Disconnect from the server and then retry the call to establish a connection.

ORA-24308: illegal define position

ORA-24308: illegal define position

Cause: Call to modify attributes was done for a non-existent position

Action: Verify that a define has been done for this position

ORA-24307: invalid length for piece

ORA-24307: invalid length for piece

Cause: The length of the piece exceeded the maximum possible size.

Action: Verify that the length of this piece and the cumulative length of all the previous pieces is not more than the desired value supplied by the application.

ORA-24306: bad buffer for piece

ORA-24306: bad buffer for piece

Cause: A zero length buffer or a null buffer pointer was provided.

Action: Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column.

ORA-24305: bad bind or define context

ORA-24305: bad bind or define context

Cause: The call was executed on a cursor for which this is invalid.

Action: Verify that this call is valid for this cursor. For example, Get piece information and set piece information are valid on a cursor if appropriate binds and defines have been done on this cursor.

ORA-24304: datatype not allowed for this call

ORA-24304: datatype not allowed for this call

Cause: Data of this datatype cannot be sent or fetched in pieces.

Action: Use other bind or define calls for this datatype.

ORA-24303: call not supported in non-deferred linkage

ORA-24303: call not supported in non-deferred linkage

Cause: One of the calls that is supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred.

Action: Use this call in deferred mode of linkage.

ORA-24302: host connection in use by another thread

ORA-24302: host connection in use by another thread

Cause: An attempt was made to use the host connection while it was in use by another thread.

Action: Wait for another thread to finish before using this connection.

ORA-24301: null host specified in thread-safe logon

ORA-24301: null host specified in thread-safe logon

Cause: An HDA was not specified in the logon call while running in a thread safe environment.

Action: Make sure that HDA is not NULL when calling the logon routine.

ORA-24300: bad value for mode

ORA-24300: bad value for mode

Cause: An undefined mode value was specified.

Action: Check that the correct mode is selected and that an allowed value for that mode is specified.

ORA-24295: max key length (string) for sorted hash cluster exceeded

ORA-24295: max key length (string) for sorted hash cluster exceeded

Cause: Sorted hash clusters have a maximum key size

Action: none

ORA-24292: no more tables permitted in this sorted hash cluster

ORA-24292: no more tables permitted in this sorted hash cluster

Cause: A sorted hash cluster only supports a maximum of 2 tables

Action: none

ORA-24281: invalid access past the maximum size of LOB parameter string

ORA-24281: invalid access past the maximum size of LOB parameter string

Cause: The value of positional or size parameters exceeds the maximum allowed LOB size of 4 Gigabytes.

Action: Correct the input values for amount and offset such that their sum is less than or equal to 4 Gigabytes. If error occurs in a read or write loop, check the looping conditions and or or offset increments.

ORA-24280: invalid input value for parameter string

ORA-24280: invalid input value for parameter string

Cause: The parameter has been provided a negative, out of range, or NULL input value.

Action: Correct the input value such that it is valid, and is within the range as specified in the documentation.

ORA-24276: function string output string maximum value exceeded

ORA-24276: function string output string maximum value exceeded

Cause: The function lamp;lt;lamp;nbsp;pkgname.funcnamelamp;gt; computed a value for the output lamp;lt;lamp;nbsp;parmnamelamp;gt; that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype.

Action: Correct the input values to produce a result that will comply with the limits as specified in the documentation.

ORA-24275: function string parameter string missing or invalid

ORA-24275: function string parameter string missing or invalid

Cause: The function lamp;lt;lamp;nbsp;pkgname.funcnamelamp;gt; was called with a parameter lamp;lt;lamp;nbsp;parmnamelamp;gt; that was null, 0 length, or had an invalid value.

Action: Correct the parameter to supply values that comply with its datatype and limits as specified in the documentation.

ORA-24274: no row exists in the string table for these parameters

ORA-24274: no row exists in the string table for these parameters

Cause: A call was made to update a row that does not exist or a foreign key value supplied to create a table does not exist.

Action: Create the row using the appropriate API or check the parameters used to create the new row to ensure that all specified values exist.

ORA-24273: translation text is required if translation type is T or S

ORA-24273: translation text is required if translation type is T or S

Cause: If a translation type of T or S is specified, translation text must be supplied.

Action: Provide translation text and reexecute the API call.

ORA-24272: initialization value must be either F or T

ORA-24272: initialization value must be either F or T

Cause: The initialization value must be either F or T. A value other than F or T was specified.

Action: Correct the initialization value and reexecute the API call.

ORA-24271: translation type must be either T, S or M

ORA-24271: translation type must be either T, S or M

Cause: The translation type parameter is not a T, S or an M. A value other than T, S or M was specified.

Action: Correct the translation type and reexecute the API call.

ORA-24270: a row already exists in the string table for these parameters

ORA-24270: a row already exists in the string table for these parameters

Cause: A call was made to create a new row in the specified table. A row already exists in the table with the specified values.

Action: Delete the existing row using the appropriate API or check the parameters used to create the row.

ORA-24265: Insufficient privileges for SQL profile operation

ORA-24265: Insufficient privileges for SQL profile operation

Cause: A DDL operation was attempted on a SQL profile by a session without the proper privileges.

Action: Grant the user the appropriate privilege.

ORA-24240: invalid database access descriptor (DAD) name

ORA-24240: invalid database access descriptor (DAD) name

Cause: The specified Database Access Descriptor (DAD) name was invalid.

Action: Make sure the name of the Database Access Descriptor (DAD) is valid and its length does not exceed its limit.

ORA-24239: object could not be invalidated

ORA-24239: object could not be invalidated

Cause: A call to the DBMS_UTILITY.INVALIDATE routine failed. This error occurred because the object type of the object specified by the p_object_id argument is not one of the types that can be handled by this routine. Alternately, the object was an object type specification with table dependents, or the object was the specification of the STANDARD, DBMS_STANDARD, DBMS_UTILITY package, or the body of the DBMS_UTILITY package.

Action: Call DBMS_UTILITY.INVALIDATE only on supported object types.

ORA-24238: object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal

ORA-24238: object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal

Cause: This error occurred because the p_plsql_object_settings argument passed to the DBMS_UTILITY.INVALIDATE routine was NULL or malformed.

Action: Correct the illegal argument.

ORA-24237: object id argument passed to DBMS_UTILITY.INVALIDATE is not legal

ORA-24237: object id argument passed to DBMS_UTILITY.INVALIDATE is not legal

Cause: This error occurred because the p_object_id argument passed to the DBMS_UTILITY.INVALIDATE routine was NULL, there was no object with the specified object id, or the user calling the routine did not have sufficient privileges to invalidate the object.

Action: Correct the illegal argument.

ORA-24236: source text is empty

ORA-24236: source text is empty

Cause: The input source text supplied to a DBMS_PREPROCESSOR subprogram was empty.

Action: Pass a non-empty input source text as the input.

ORA-24235: bad value for object type: string

ORA-24235: bad value for object type: string

Cause: The specified object type was not appropriate.

Action: Make sure the specified object type is one of the following: package, package body, procedure, function, trigger, type, and type body.

ORA-24234: unable to get source of string string . string , insufficient privileges or does not exist

ORA-24234: unable to get source of string string . string , insufficient privileges or does not exist

Cause: The specified PL or SQL object in a DBMS_PREPROCESSOR subprogram did not exist or you did not have the privileges necessary to view its source.

Action: Make sure the specified object exists and you have the privileges necessary to view its source.

ORA-24233: argument passed to DBMS_UTILITY.VALIDATE is not legal

ORA-24233: argument passed to DBMS_UTILITY.VALIDATE is not legal

Cause: One or more input arguments to the DBMS_UTILITY.VALIDATE routine was not legal. This error occurred because the object name or owner or namespace arguments (if specified) were NULL or illegal.

Action: Identify and correct the illegal argument.

ORA-24232: unknown Embedded PL or SQL Gateway attribute string

ORA-24232: unknown Embedded PL or SQL Gateway attribute string

Cause: The specified Embedded PL or SQL Gateway attribute was not known.

Action: Make sure the name of the Embedded PL or SQL Gateway attribute is correct.

ORA-24231: database access descriptor (DAD) string not found

ORA-24231: database access descriptor (DAD) string not found

Cause: The specified Database Access Descriptor (DAD) did not exist.

Action: Make sure the name of the Database Access Descriptor (DAD) is correct and the DAD exists.

ORA-24230: input to DBMS_DDL.WRAP is not a legal PL or SQL unit

ORA-24230: input to DBMS_DDL.WRAP is not a legal PL or SQL unit

Cause: The input supplied to DBMS_DDL.WRAP or DBMS_DDL.CREATE_ WRAPPED did not specify a legal PL or SQL package specification, package body, type specification, type body, function or procedure. This error can occur if you used incorrect syntax in the CREATE OR REPLACE statement or specified a unit that cannot be wrapped (e.g., a trigger or anonymous block).

Action: Provide a legal PL or SQL unit as input.

ORA-24203: operation failed, queue table string.string has errors

ORA-24203: operation failed, queue table string.string has errors

Cause: An operation attempt was made to a queue table which has errors.

Action: Drop the queue table setting the force option to true.

ORA-24202: publisher does not exist for the queue

ORA-24202: publisher does not exist for the queue

Cause: Attempted to alter or drop a non existent publisher from a queue.

Action: Specify another publisher.

ORA-24201: duplicate publisher, publisher already added to the queue

ORA-24201: duplicate publisher, publisher already added to the queue

Cause: Attempted to add a publisher to the queue again.

Action: Specify another publisher or user DBMS_AQADM.ALTER_PUBLISHER to alter the publisher s properties.

ORA-24199: message store is overflow

ORA-24199: message store is overflow

Cause: An attemp was made to access too many messages at the same time.

Action: Use the CLEAN procedure to clean up some of the messages.

ORA-24198: attempt to use an invalid operation ID

ORA-24198: attempt to use an invalid operation ID

Cause: An attempt was made to use an invalid operation ID to access messages.

Action: Use the correct operation ID returned by PREPARE or CLEAR_BODY procedure.

ORA-24197: JAVA stored procedure throws JAVA exceptions

ORA-24197: JAVA stored procedure throws JAVA exceptions

Cause: The JAVA stored procedure threw some exceptions that could not be catergorized.

Action: Use GET_EXCEPTION procedure to see what the exception is about.

ORA-24196: access the message in a wrong access mode

ORA-24196: access the message in a wrong access mode

Cause: StreamMessage and BytesMessage could not be read when they were in write only mode and vice versa.

Action: Change the access mode using PREPARE, CLEAR_BODY and RESET procedures.

ORA-24195: attemp to retrieve the name list of a map message with size exceeding 1,024

ORA-24195: attemp to retrieve the name list of a map message with size exceeding 1,024

Cause: The GET_NAMES function returns the names in a varray with a size limit of 1024.

Action: Retrieve in several smaller steps using the GET_NAMES function with OFFSET and LENGTH parameters.

ORA-24194: attempt to read data in a message as the wrong type

ORA-24194: attempt to read data in a message as the wrong type

Cause: According to JMS specification, some type conversions were not allowed.

Action: Make sure to use the correct READ function to retrieve message data.

ORA-24193: the property value exceeds the valid range string

ORA-24193: the property value exceeds the valid range string

Cause: the property valus being set exceeds the valid range.

Action: make sure the property value is within the valid range.

ORA-24192: the property name cannot be null

ORA-24192: the property name cannot be null

Cause: the property name cannot be null.

Action: make sure the property name not null.

ORA-24191: the property name string has existed

ORA-24191: the property name string has existed

Cause: the property name being set has existed.

Action: use another property name.

ORA-24190: length of payload exceeds string

ORA-24190: length of payload exceeds string

Cause: the length of payload being taken exceeds the limit of varchar2 or raw.

Action: use clob type or blob type to call get_text or get_bytes.

ORA-24186: wrong object type, could not transform message

ORA-24186: wrong object type, could not transform message

Cause: The object type of the message to be transformed does not match the source type of the specified transfomation.

Action: Specify another transformation, or specify a message of the correct type.

ORA-24185: transformation string.string does not exist

ORA-24185: transformation string.string does not exist

Cause: The specified transformation does not exist.

Action: Create the transformation before using it or specify an existing transformation.

ORA-24184: transformation string.string already exists

ORA-24184: transformation string.string already exists

Cause: The named transformation already exists.

Action: Specify another name for the transformation being created.

ORA-24183: invalid transformation

ORA-24183: invalid transformation

Cause: The transformation specified is invalid because the source or the target type have been dropped or modified.

Action: Drop and recreate the transformation

ORA-24182: attribute number specified does not exist

ORA-24182: attribute number specified does not exist

Cause: The target type of the transformation does not have the attribute number specified in the ADD_ATTRIBUTE_TRANSFORMATION command

Action: check the target type definition and specify a valid attribute number

ORA-24181: The type string does not exist

ORA-24181: The type string does not exist

Cause: The source or destination type for the transformation does not exist

Action: Create the type or specify one that exists

ORA-24180: invalid transformation expression, the transformation expression does not evaluate to the target type or attribute

ORA-24180: invalid transformation expression, the transformation expression does not evaluate to the target type or attribute

Cause: The transformation expression does not evaluate to the target type or the target type s specified attribute.

Action: Provide valid transformation expression which evaluates to the target type or the target type s specified attribute.