PLS-00632: NOT INSTANTIABLE method cannot have a body

PLS-00632: NOT INSTANTIABLE method cannot have a body

Cause: An attempt was made to provide an implementation for a NOT INSTANTIABLE method.

Action: Remove the implementation for the NOT INSTATIABLE method.

PLS-00631: PARTITION-BY and CLUSTER or ORDER-BY clauses must be used with the same function argument

PLS-00631: PARTITION-BY and CLUSTER or ORDER-BY clauses must be used with the same function argument

Cause: PARTITION-BY and CLUSTER or ORDER-BY clauses are specified on different function arguments.

Action: Use the same argument in both PARITITON-BY and CLUSTER or ORDER-BY clauses.

PLS-00629: PIPE statement cannot be used in non-pipelined functions

PLS-00629: PIPE statement cannot be used in non-pipelined functions

Cause: A PIPE statement was used in a non-pipelined function.

Action: Use PIPE statement only in pipelined functions.

PLS-00628: string must be a valid record attribute

PLS-00628: string must be a valid record attribute

Cause: A partitioning or clustering or ordering specification must use only valid record attributes.

Action: Specify partitioning or clustering or ordering based on valid record attributes.

PLS-00627: string must be a strongly typed ref cursor

PLS-00627: string must be a strongly typed ref cursor

Cause: A partitioning or clustering or ordering specification specified on an argument that is not a strongly typed ref cursor.

Action: Specify partitioning or clustering or ordering based on the function ref-cursor formal argument.

PLS-00626: partitioned or clustered or ordered parameter must be a function argument

PLS-00626: partitioned or clustered or ordered parameter must be a function argument

Cause: A partitioning or clustering or ordering specification specified on an argument that is not one of the function arguments.

Action: Specify partitioning or clustering or ordering based on the function ref-cursor formal argument.

PLS-00625: PARTITION or CLUSTER or ORDER-BY clause can only be used with IN parameters

PLS-00625: PARTITION or CLUSTER or ORDER-BY clause can only be used with IN parameters

Cause: A PARTITION or CLUSTER or ORDER-BY clause was used with an OUT or IN OUT ref-cursor parameter.

Action: Change the parameter mode to IN or use some other parameter with the PARTITION or CLUSTER or ORDER-BY clause.

PLS-00624: USING clause must be used with either aggregate or pipelined functions

PLS-00624: USING clause must be used with either aggregate or pipelined functions

Cause: USING clause cannot be used with functions that are not declared with AGGREGATE or PIPELINED properties.

Action: Define function body in PL or SQL or some other language (using external callout call specification).

PLS-00623: FLOAT precision constraint must be between 1 and 126

PLS-00623: FLOAT precision constraint must be between 1 and 126

Cause: The precision specified for a FLOAT, REAL or DOUBLE PRECISION did not fall between 1 and 126.

Action: Use precision constraints between 1 and 126.

non-NULL. PLS-00622: range constraints must be between -2147483647 and 2147483647

non-NULL. PLS-00622: range constraints must be between -2147483647 and 2147483647

Cause: The range constraints specified for a pls_integer or binary_integer declaration did not fall between -2147483647 and 2147483647.

Action: Use range constraints between -2147483647 and 2147483647.

PLS-00621: at least one operand in the COALESCE expression must not be NULL

PLS-00621: at least one operand in the COALESCE expression must not be NULL

Cause: All the operands in the COALESCE expression are the literal NULL.

Action: Change at least one operand in the COALESCE expression to be

PLS-00620: type mismatch found at string among operands in a COALESCE expression

PLS-00620: type mismatch found at string among operands in a COALESCE expression

Cause: In a COALESCE expression, the operands do not match in datatype, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the operands so that their datatypes match. Consider using datatype conversion functions in the operands.

PLS-00619: the first operand in the NULLIF expression must not be NULL

PLS-00619: the first operand in the NULLIF expression must not be NULL

Cause: The first operand in the NULLIF expression is the literal NULL.

Action: Change the first operand in the NULLIF expression to be non-NULL.

PLS-00618: type mismatch found at string between operands in a NULLIF expression

PLS-00618: type mismatch found at string between operands in a NULLIF expression

Cause: In a NULLIF expression, the two operands do not match in datatype, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the operands so that their datatypes match. Consider using datatype conversion functions in the operands.

PLS-00617: at least one result in the CASE expression must not be NULL

PLS-00617: at least one result in the CASE expression must not be NULL

Cause: All the results in the CASE expression are the literal NULL.

Action: Change at least one result in the CASE expression to be non-NULL.

PLS-00616: type mismatch found at string among result expressions in a CASE expression

PLS-00616: type mismatch found at string among result expressions in a CASE expression

Cause: In a CASE expression, the result expressions do not match in datatype, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the result expressions so that their datatypes match. Consider using datatype conversion functions in the result expressions.

PLS-00615: type mismatch found at string between CASE operand and WHEN operands

PLS-00615: type mismatch found at string between CASE operand and WHEN operands

Cause: In a simple CASE statement or expression, the CASE operand and WHEN operands do not match in datatype, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the CASE operand and WHEN operands so that their datatypes match. Consider using datatype conversion functions in the CASE operand and or or WHEN operands.

PLS-00614: creating a FINAL NOT INSTANTIABLE type

PLS-00614: creating a FINAL NOT INSTANTIABLE type

Cause: An attempt was made to create a FINAL NOT INSTANTIABLE type. No useful operation can be performed with this type.

Action: Avoid using the keywords FINAL and NOT INSTANTIABLE together when creating types.

PLS-00613: only one item is allowed, when using variables of record type

PLS-00613: only one item is allowed, when using variables of record type

Cause: You are trying to use more than one values in VALUES clause or RETURNING INTO clause, when one of the value is of record type..

Action: Specify only one variable of record type, or don t use variables of record type.

PLS-00612: Number of attributes do not match in SET clause

PLS-00612: Number of attributes do not match in SET clause

Cause: Number of columns do not match with number of attributes on record type on rhs.

Action: Make sure that number of columns match with the number of attributes in record on rhs.

PLS-00611: right hand side can be only the variables of record type

PLS-00611: right hand side can be only the variables of record type

Cause: with ROW on LHS, only PL or SQL records or %ROWTYPE variables are allowed on right hand side..

Action: Make appropriate changes, so that right hande side should only have variables of record or %ROWTYPE.

PLS-00610: ROW can be used only once in SET clause of UPDATE statement

PLS-00610: ROW can be used only once in SET clause of UPDATE statement

Cause: You were trying to use ROW more than once in UPDATE statement.

Action: Remove all the additional ROW in set clause of UPDATE statement.

PLS-00609: the OVERRIDING clause is not valid for SQLJ Object Types

PLS-00609: the OVERRIDING clause is not valid for SQLJ Object Types

Cause: You were trying to a SQLJ Object Type method that override an inherited method.

Action: Change the SQLJ Object Type defintion by removing the OVERRIDING method.

TNS-00552: no valid cipher suites were specified

TNS-00552: no valid cipher suites were specified

Cause: SSL cipher specs were specified, but none were valid.

Action: Specify correct cipher suites.

TNS-00551: underlying transport connection failed

TNS-00551: underlying transport connection failed

Cause: The underlying transport adapter used by the SSL adapter failed to connect.

Action: Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.

TNS-00550: disconnection error

TNS-00550: disconnection error

Cause: The SSL protocol adapter encountered an error when the underlying transport disconnected.

Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.

TNS-00549: value specified for the SSL version is not valid

TNS-00549: value specified for the SSL version is not valid

Cause: The value specified for the SSL version is not valid.

Action: Specify a valid value for the SSL version.

TNS-00548: value specified for client authentication parameter is not boolean

TNS-00548: value specified for client authentication parameter is not boolean

Cause: The value specified for the parameter that specifies that SSL client authentication is to be used was not boolean.

Action: Specify a correct value for the parameter.

TNS-00547: user information retrieval failed

TNS-00547: user information retrieval failed

Cause: The SSL protocol adapter was unable to retrieve information about the remote user.

Action: Examine the first error in the error stack. It should describe the error in more detail.

TNS-00546: control failure

TNS-00546: control failure

Cause: The SSL protocol adapter was unable to perform a command.

Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.

TNS-00545: parameter retrieval failure

TNS-00545: parameter retrieval failure

Cause: The SSL protocol adapter was not able to retrieve a configuration parameter for some reason.

Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.

TNS-00544: unsupported operation

TNS-00544: unsupported operation

Cause: The SSL adapter could not perform a given command.

Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.

TNS-00543: internal error

TNS-00543: internal error

Cause: The SSL protocol adapter encountered an unexpected error.

Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.

TNS-00542: SSL Handshake failed

TNS-00542: SSL Handshake failed

Cause: The SSL protocol adapter was unable to connect to another process.

Action: This error can be caused by a variety of problems including the termination of the peer process. Enable Oracle Net tracing and attempt the connection again. The trace file should give some clues as to what the exact problem is.

ORA- error. TNS-00541: underlying transport does not exist.

ORA- error. TNS-00541: underlying transport does not exist.

Cause: The SSL protocol adapter was unable to locate an adapter for the protocol that it is going to use as the data transport.

Action: In most cases, the underlying transport is TCP. Make sure that the Oracle Net TCP or IP adapter was installed.

TNS-00540: SSL protocol adapter failure

TNS-00540: SSL protocol adapter failure

Cause: The SSL protocol adapter encountered an error.

Action: In most cases, this error should only be pair with a more meaningful

TNS-00539: Network or Protocol services are down

TNS-00539: Network or Protocol services are down

Cause: The Network services on or from your node are not running or have stopped running.

Action: Restart your network or protocol services on this platform. If error persists, contact Oracle Customer Support.

TNS-00537: Index into protocol adapter table is out of legal range

TNS-00537: Index into protocol adapter table is out of legal range

Cause: Internal protocol adapter error.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-00536: Connection entered inappropriate state

TNS-00536: Connection entered inappropriate state

Cause: Internal protocol adapter error.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-00535: Failed to send or receive disconnect message

TNS-00535: Failed to send or receive disconnect message

Cause: Internal protocol adapter error.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-00534: Failed to grant connection ownership to child

TNS-00534: Failed to grant connection ownership to child

Cause: Internal protocol adapter error.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-00533: Connection dissolved or not yet made

TNS-00533: Connection dissolved or not yet made

Cause: Internal protocol adapter error.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-00532: No previous async operation to wait on

TNS-00532: No previous async operation to wait on

Cause: Internal protocol adapter error.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-00530: Protocol adapter error

TNS-00530: Protocol adapter error

Cause: A generic protocol adapter error occurred.

Action: For further details, turn on tracing and reexecute the operation.

TNS-00526: No caller (false async event)

TNS-00526: No caller (false async event)

Cause: Internal error.

Action: For further details, turn on tracing and reexecute the operation.

TNS-00525: Insufficient privilege for operation

TNS-00525: Insufficient privilege for operation

Cause: Operating system failed to complete operation because user lacked sufficient privileges.

Action: Check your platform-specific privileges.

TNS-00524: Current operation is still in progress

TNS-00524: Current operation is still in progress

Cause: Internal operation is still in progress but will complete.

Action: None; wait for operation to complete.

TNS-00523: Previous operation was busy

TNS-00523: Previous operation was busy

Cause: Operation tried could not be successfully completed because the requested resource was busy.

Action: Attempt the operation again. If error persists, contact Oracle Customer Support.

TNS-00014: INTCTL: error while opening terminal input channel

TNS-00014: INTCTL: error while opening terminal input channel

Cause: Could not open standard terminal input. Internal error.

Action: Normally not visible to the user. Restart the INTCTL program. If error persists, contact Oracle Customer Support.

TNS-00013: INTCTL: error while performing NS disconnect command

TNS-00013: INTCTL: error while performing NS disconnect command

Cause: Internal NS error. Error in closing down connections.

Action: Make sure the networking protocol being used is properly installed on the machine. If the error persists contact Oracle Customer Support.

TNS-00012: INTCTL: error while processing Connection Manager request

TNS-00012: INTCTL: error while processing Connection Manager request

Cause: An improper command was sent to the Connection Manager or it is not responding. Not normally visible to the user.

Action: Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files. Also check that the Connection Manager is running by using the STATUS command of the Interchange Control Utility. If the error persists, contact Oracle Customer Support.

TNS-00011: INTCTL: error while starting the Connection Manager

TNS-00011: INTCTL: error while starting the Connection Manager

Cause: The Connection Manager could not be started.

Action: Assure that the executable can be found in the standard Oracle executable area. Check the configuration file INTCHG.ORA for errors and confirm that no other process is using the ADDRESS(es) for this Connection Manager as specified in TNSNET.ORA. Tracing can also be turned on in the Connection Manager and detailed information about the reason for the error determined. Consult the MultiProtocol Interchange Administrator s Guide and Chapter 2 of this manual for how to turn on tracing.

TNS-00010: Error while flushing NS context

TNS-00010: Error while flushing NS context

Cause: Internal NS error; connection may be lost.

Action: Make sure the connection is properly established. If the error persists, then contact Oracle Customer Support.

TNS-00009: INTCTL: could not contact destination Connection Manager

TNS-00009: INTCTL: could not contact destination Connection Manager

Cause: Connection could not be properly established to a Connection Manager. This may be because the Connection Manager (Interchange) specified is not running or the Connection Manager addresses are incorrect.

Action: Make sure the Connection Manager is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Connection Manager using the START command of the Interchange Control Utility. If it is running and the error persists, contact Oracle Customer Support.

TNS-00008: INTCTL: could not contact destination Navigator

TNS-00008: INTCTL: could not contact destination Navigator

Cause: Connection could not be properly established to a Navigator. This may be because the Navigator specified is not running or the Navigator addresses are incorrect.

Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Navigator using the START command of the Interchange Control Utility. If it is running and the error persists, contact Oracle Customer Support.

TNS-00007: INTCTL: unknown host

TNS-00007: INTCTL: unknown host

Cause: The pointer HOST is set to an unknown hostname.

Action: Set the pointer HOST properly and restart INTCTL program.

TNS-00006: INTCTL: HOST variable is not defined

TNS-00006: INTCTL: HOST variable is not defined

Cause: The HOST variable was not set.

Action: Set the variable HOST properly and restart the INTCTL program.

TNS-00005: INTCTL: error while sending request to the Navigator

TNS-00005: INTCTL: error while sending request to the Navigator

Cause: The Navigator is not responding. Either the Navigator is not running or another process is responding.

Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility. Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files.

TNS-00004: INTCTL: error while starting the Navigator

TNS-00004: INTCTL: error while starting the Navigator

Cause: The Navigator could not be started.

Action: Check to make sure that executables for the Navigator (navgatr) are present in the ORACLE executable directory on your platform. Check the configuration files TNSNET.ORA and TNSNAV.ORA for errors. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been rectified.

TNS-00003: INTCTL: error while sending request to the Interchange

TNS-00003: INTCTL: error while sending request to the Interchange

Cause: Improper command sent to the Interchange or the Interchange is not responding. Not normally visible to the user.

Action: Verify that the command sent to the Interchange is valid. Also check that the Interchange is running by using the INTCTL STATUS command. If necessary, start the Interchange using the INTCTL START command.