Oracle Error Messages: 12/13/11

TNS-00514: Contexts have different wait or test functions

TNS-00514: Contexts have different wait or test functions

Cause: Two protocol adapters have conflicting wait or test functions.

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

TNS-00513: Destination host unreachable

TNS-00513: Destination host unreachable

Cause: Contact cannot be made with remote party.

Action: Make sure the network driver is functioning and the network is up.

TNS-00512: Address already in use

TNS-00512: Address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with an unused address.

TNS-00511: No listener

TNS-00511: No listener

Cause: The connect request could not be completed because no application is listening on the address specified, or the application is unable to service the connect request in a sufficiently timely manner.

Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange. Start the listener on the remote machine.

TNS-00510: Internal limit restriction exceeded

TNS-00510: Internal limit restriction exceeded

Cause: Too many files or sockets open simultaneously (or some other resource has been depleted).

Action: For further details, trace the operation for protocol details.

TNS-00509: Buffer overflow

TNS-00509: Buffer overflow

Cause: Too much data for buffer.

Action: Reexecute with larger receive buffer or smaller send buffer.

TNS-00508: No such protocol adapter

TNS-00508: No such protocol adapter

Cause: The protocol adapter requested for this connection does not exist.

Action: Install the protocol adapter or use one that is available. Be sure that the correct protocols are listed in the configuration files.

TNS-00507: Connection closed

TNS-00507: Connection closed

Cause: Normal end of file condition has been reached; partner has disconnected.

Action: None needed; this is an information message.

TNS-00506: Operation would block

TNS-00506: Operation would block

Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking.

Action: None needed; this is an information message.

TNS-00505: Operation timed out

TNS-00505: Operation timed out

Cause: The requested operation could not be completed within the timeout period.

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

TNS-00504: Operation not supported

TNS-00504: Operation not supported

Cause: An internal function received a request to perform an operation that is not supported (on this machine).

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

TNS-00503: Illegal ADDRESS parameters

TNS-00503: Illegal ADDRESS parameters

Cause: An illegal set of protocol adapter parameters was specified.

Action: Check the parameters within the ADDRESS section of the TNSNAMES.ORA file. It may be helpful to turn on tracing and look at the addresses specified in the trace file, checking for spelling or other errors. Be sure to turn tracing off when the trace is complete.

TNS-00502: Invalid argument

TNS-00502: Invalid argument

Cause: An internal function received an invalid parameter.

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

TNS-00501: Cannot allocate memory

TNS-00501: Cannot allocate memory

Cause: Sufficient memory could not be allocated to perform the desired activity.

Action: Either free some resource for TNS or add more memory to the machine. For further details, turn on tracing and reexecute the operation.

TNS-00317: Failed to contact Connection Manager

TNS-00317: Failed to contact Connection Manager

Cause: Connection Manager is not running.

Action: Start the Connection Manager and retry

TNS-00316: Ran out of data buffers in the pump

TNS-00316: Ran out of data buffers in the pump

Cause: The Interchange is resource limited by having too few data buffers in the pump.

Action: If the problem persists (that is, there are a lot of log messages), increase the number of pump buffers by increasing the value of the parameter PUMP_ BUFFERS in INTCHG.ORA. Then shutdown and restart the Interchange to make the changes take effect.

TNS-00315: Failed to allocate larger connect data area for getting pump data: number

TNS-00315: Failed to allocate larger connect data area for getting pump data: number

Cause: Could not allocate a large enough area to get pump statistics; continue without them.

Action: None.

TNS-00314: Protocol Adapter Errors: number,number

TNS-00314: Protocol Adapter Errors: number,number

Cause: Protocol Adapter errors which go with message 233

Action: None.

TNS-00313: Navigator: Failed to get version information

TNS-00313: Navigator: Failed to get version information

Cause: Message sent back to control program from Connection Manager.

Action: None.

TNS-00312: Connection Manager: Failed to get version information

TNS-00312: Connection Manager: Failed to get version information

Cause: Message sent back to control program from Connection Manager.

Action: None.

TNS-00311: Connection Manager: Failed to start tracing after rereading parameter data

TNS-00311: Connection Manager: Failed to start tracing after rereading parameter data

Cause: Message sent back to control program from Connection Manager.

Action: None.

TNS-00310: Navigator: Failed to start tracing after rereading parameter data

TNS-00310: Navigator: Failed to start tracing after rereading parameter data

Cause: Message sent back to control program from Navigator.

Action: None.

PROT-00304: Failed to create dump file (string(

PROT-00304: Failed to create dump file (string(

Cause: Unable to create or open file for dumping cluster registry data

Action: Check access privilege or disk space of the requested path

PROT-00303: Dump file already exists (string(

PROT-00303: Dump file already exists (string(

Cause: Requested dump file exists in the given path

Action: Change the location for the dump file or remove the old dump file

PROT-00302: Failed to initialize ocrdump

PROT-00302: Failed to initialize ocrdump

Cause: Unable to initialize and start ocrdump

Action: Check log file for details about the failure

PROT-00301: Dump is not feasible when clusterware is running

PROT-00301: Dump is not feasible when clusterware is running

Cause: Unable to dump cluster registry data when clusterware is running

Action: Stop the clusterware before retrying ocrdump

PROT-00118: Please ensure you have file creation privileges in the above directory before running this tool.

PROT-00118: Please ensure you have file creation privileges in the above directory before running this tool.

Cause: ocrconfig called with incorrect or missing options

Action: Use ocrconfig with correct options

PROT-00022: Storage too small

PROT-00022: Storage too small

Cause: Specified storage is too small to mirror OCR content

Action: Run the command again using a device with large storage capacity

PROT-00021: Invalid parameter

PROT-00021: Invalid parameter

Cause: Input parameter is not valid

Action: Check log file for more information

PROT-00020: Insufficient permission to proceed. Require privileged user

PROT-00020: Insufficient permission to proceed. Require privileged user

Cause: User is not a privileged user.

Action: Run the command again using a privileged user.

PROT-00019: Cannot proceed while clusterware is running. Shutdown clusterware first

PROT-00019: Cannot proceed while clusterware is running. Shutdown clusterware first

Cause: Clusterware is running.

Action: Shutdown clustware on every node in the cluster

PROT-00018: Failed to open file

PROT-00018: Failed to open file

Cause: File does not exist or user does not have permission to open the file

Action: Try with a different file name

PROT-00017: Fatal Error

PROT-00017: Fatal Error

Cause: This is a generic fatal error for ocrconfig

Action: Contact Oracle Customer Support

PROT-00016: Internal Error

PROT-00016: Internal Error

Cause: This is a generic internal error for ocrconfig

Action: Contact Oracle Customer Support

PROT-00015: Unimplemented feature

PROT-00015: Unimplemented feature

Cause: Requested feature has not been implemented in current release

Action: Try the feature again in the next release.

PROT-00014: Oracle Cluster Registry to be downgraded has an earlier version

PROT-00014: Oracle Cluster Registry to be downgraded has an earlier version

Cause: Oracle Cluster Registry to be downgraded has an earlier version

Action: No action required

PROT-00013: Oracle Cluster Registry is in current version

PROT-00013: Oracle Cluster Registry is in current version

Cause: Oracle Cluster Registry is in current version

Action: No action required

PROT-00012: Oracle Cluster Registry to be upgraded has an unsupported version

PROT-00012: Oracle Cluster Registry to be upgraded has an unsupported version

Cause: Oracle Cluster Registry to be upgraded has an unsupported version

Action: Upgrade Oracle Cluster Registry to a version supported

PROT-00011: Failed to open the specified destination cluster registry

PROT-00011: Failed to open the specified destination cluster registry

Cause: Unable to access the specified destination cluster registry

Action: Check access privilege and location of the destination cluster registry. Also check the log file for more details

PROT-00010: Failed to open the specified source cluster registry

PROT-00010: Failed to open the specified source cluster registry

Cause: Unable to access the specified source cluster registry

Action: Check access privilege and location of the source cluster registry, and the log file for more detail

PROT-00009: Failed to open the specified import file

PROT-00009: Failed to open the specified import file

Cause: Unable to access the specified import file

Action: Check access privilege of the import file

PROT-00008: Failed to import data from specified file to the cluster registry

PROT-00008: Failed to import data from specified file to the cluster registry

Cause: Unable to read data from the import file and import to the cluster registry

Action: Check availability of the cluster registry and the details of the failure from the log file

PROT-00007: Failed to open the specified import file

PROT-00007: Failed to open the specified import file

Cause: Unable to access the specified import file

Action: Check access privilege of the import file

PROT-00006: The specified import file cannot be found

PROT-00006: The specified import file cannot be found

Cause: The import file does not exist

Action: Check the file and its correct path and try again

PROT-00005: Clusterware is not running properly

PROT-00005: Clusterware is not running properly

Cause: Unable to register with clusterware for access to the cluster registry

Action: Check the status of clusterware running on the machine

PROT-00004: Failed to retrieve data from the cluster registry

PROT-00004: Failed to retrieve data from the cluster registry

Cause: Unable to retrieve necessary information from the cluster registry

Action: Check the availability of the cluster registry and the details of the failure from the log file

PROT-00003: Failed to create export file

PROT-00003: Failed to create export file

Cause: Unable to create or open file for exporting cluster registry data

Action: Check access privilege or disk space of the requested path

PROT-00002: Export file already exists

PROT-00002: Export file already exists

Cause: Requested export file exists in the given path

Action: Change the location for export file or remove the old export file

PROT-00001: Failed to initialize ocrconfig

PROT-00001: Failed to initialize ocrconfig

Cause: Unable to initialize and start ocrconfig

Action: Check log file for details about the failure

PROC-00106: Unidentified component error

PROC-00106: Unidentified component error

Cause: An error occurred in an unidentified layer while performing a cluster registry operation.

Action: Contact Oracle customer support.

PROC-00105: Logging error

PROC-00105: Logging error

Cause: An error occurred in the logging layer while while performing a cluster registry operation.

Action: Contact Oracle customer support.

PROC-00104: Authentication error (string(

PROC-00104: Authentication error (string(

Cause: An error occurred in the authentication layer while performing a cluster registry operation.

Action: Contact Oracle customer support.

PROC-00103: Messaging error

PROC-00103: Messaging error

Cause: An error occurred in the messaging layer while performing a cluster registry operation.

Action: Contact Oracle customer support.

PROC-00102: Cluster services error (string(

PROC-00102: Cluster services error (string(

Cause: An error occurred in the cluster services layer while performing a cluster registry operation.

Action: Contact Oracle customer support.

PROC-00101: Operating System error (string(

PROC-00101: Operating System error (string(

Cause: An error occurred in the operating system layer while performing a cluster registry operation

Action: Contact Oracle customer support.

PROC-00037: Oracle Cluster Registry does not support the storage type configured

PROC-00037: Oracle Cluster Registry does not support the storage type configured

Cause: The configured storage type for cluster registry is not supported

Action: Change the configuration of the cluster registry to a supported storage type. Refer to Oracle documentation for an exhaustive list for each platform.