Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00100 to ORA-00200
- ORA-00100: no data found
Cause: An application made reference to unknown or inaccessible data.
Action: Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.
Cause: The syntax for the DISPATCHERS parameter is incorrect.
Action: Refer to the manual for correct syntax.
Cause: The network specified in DISPATCHERS does not have the functionality required by the dispatchers.
Action: Refer to the manual on network protocols supported by the dispatchers.
Cause: The network specified in the SQL*Net connect string is reserved for use by the dispatchers.
Action: Specify other network protocols in the connection string.
Cause: All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources.
Action: Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS.
Cause: Too many dispatcher configurations have been specified. No more can be added.
Action: Consolidate the dispatcher configurations if possible.
Cause: An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.
Action: Re-connect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string.
Cause: Most likely due to the fact that ORACLE listener has not been started.
Action: Start ORACLE listener if it has not been started. Or else contact your ORACLE representative.
Cause: Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.
Action: Contact your ORACLE representative.
Cause: The value specified for the attribute was incorrect.
Action: Refer to the manual for the proper values.
Cause: The value specified for the attribute was incorrect.
Action: Specify a value within the range allowed.
Cause: The specified attribute was not recognized.
Action: Refer to the manual for the proper keyword to use to specify a dispatcher attribute.
Cause: The attribute was specified with no value.
Action: Specify a non-null value.
Cause: A protocol name specified in the DISPATCHERS system parameter is too long.
Action: Use a valid protocol name for the DISPATCHERS value.
Cause: No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.
Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified.
Cause: A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.
Action: Connect to a different dispatcher, or use a dedicated server.
Cause: A service name specified in the SERVICE_NAMES system parameter is too long.
Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars).
Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified.
Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
Cause: The syntax for the specified parameter is incorrect.
Action: Refer to the Oracle Reference Manual for the correct syntax.
Cause: ‘shared_servers’ cannot be set to a non-zero value in a non-ROOT pluggable database (PDB).
Action: In a multitenant container database (CDB) setup, shared servers can be configured only in ROOT. A non-ROOT PDB can disable shared servers for the PDB by setting ‘shared_servers’ to 0. No other values are allowed. To reenable within the PDB, use ‘alter system reset shared_servers’.
Cause: ORACLE could not initialize SQL*Net version 2.
Action: Check the error stack for detailed information.
Cause: Too many idle servers were waiting on the common queue.
Action: This error is used internally, no action is required.
Cause: The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
Action: Correct the PRESENTATION specified in the TNS address.
Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
Action: Correct the DUPLICITY specified in the TNS address.
Cause: There is currently no dispatcher running with the specified name.
Action: Retry with a name of the form “D###” denoting an existing dispatcher process.
Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN
Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] ‘dispatcher name’
Cause: An error was encountered while validating the listener address.
Action: Resolve error or contact your ORACLE representative.
Cause: The listener address specification is not valid.
Action: Make sure that all fields in the listener address (protocol, port, host, key, …) are correct.
Cause: The specified protocol does not support async notification.
Action: Refer to the manual for information on supported network protocols.
Cause: Listener address has syntax error or cannot be resolved.
Action: If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct.
Cause: The value specified for the attribute was too long.
Action: Use shorter names and keywords or remove unneeded blanks.
Cause: The syntax for the n-th DISPATCHERS specification was incorrect.
Action: Refer to the Oracle Reference Manual for the correct syntax.
Cause: The indicated mandatory attribute was not specified.
Action: Specify a non-null value for the attribute.
Cause: The syntax for the nth LISTENER_NETWORKS specification was invalid.
Action: Refer to the Oracle Reference Manual for the correct syntax.
Cause: The syntax for the LISTENER_NETWORKS specification with the indicated NAME was invalid.
Action: Refer to the Oracle Reference Manual for the correct syntax.
Cause: All of the specified addresses or aliases for the attribute were invalid.
Action: Specify at least one valid address or alias.
Cause: The indicated attribute was specified more than once.
Action: Specify the attribute at most once.
Cause: An internal network name has been specified.
Action: Specify a different network name.
Cause: All of the specified addresses or aliases for the parameter were invalid.
Action: Specify at least one valid address or alias.
Cause: FORWARD_LISTENER was used with LOCAL_LISTENER for the same network.
Action: Do not use FORWARD_LISTENER with LOCAL_LISTENER in the same network.
- ORA-00143: The registration of a remote port is not supported without the registration of a local port.
Cause: The remote HTTP/HTTPS port could not be registered without the local HTTP/HTTPS port.
Action: Register the local HTTP/HTTPS port first.
Cause: Attempted to start a new transaction with an ID already in use by an existing transaction.
Action: Check your application.
Cause: The specified transaction ID does not correspond to an existing valid transaction.
Action: Check your application.
Cause: The current session is not the same as the session that was passed into a upixado() call.
Action: Check your application.
Cause: The XA library could not access thread-specific pointers.
Action: Contact customer support.
Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.
Action: Contact the transaction monitor customer support.
Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.
Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work.
Cause: An external global transaction ID with a too large length field was passed in.
Action: Report the problem to your external transaction coordinator vendor.
Cause: An external transaction branch ID with a length either too large or 0 was passed in.
Action: Report the problem to your external transaction coordinator vendor.
Cause: An external database name with too large a length field was passed in.
Action: Report the problem to your external transaction coordinator vendor.
Cause: An internal database name with a too large length field was passed in.
Action: Report the problem to your external transaction coordinator vendor.
Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.
Action: Roll back or commit the current distributed transaction first.
Cause: A request was made by the application to start a migratable distributed autonomous transaction with remote operation.
Action: n/a
Cause: Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table.
Action: Rearrange the query or co-locate the functions with the tables.
Cause: It was not possible to create the control file.
Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.