原因： Even though there may be SGA corruptions, the SGA was mapped. 解决： Use the DUMPSGA command to dump the SGA. ORA-00084: global area must be PGA, SGA, or UGA
原因： An attempt was made to dump an invalid global area. 解决： Specify either PGA, SGA, or UGA. ORA-00085: current call does not exist
原因： An invalid attempt was made to dump the current call heap. 解决： Wait until the process starts a call. ORA-00086: user call does not exist
原因： An invalid attempt was made to dump the user call heap. 解决： Wait until the process starts a call.
ORA-00087: command cannot be executed on remote instance
原因： Cluster database command issued for non cluster database ORADEBUG command. 解决： Issue the command without the cluster database syntax. ORA-00088: command cannot be executed by shared server 原因： Debug command issued on shared server.
解决： Reissue the command using a dedicated server.
ORA-00089: invalid instance number in ORADEBUG command
原因： An invalid instance number was specified in a cluster database ORADEBUG command. 解决： Reissue the command with valid instance numbers.
ORA-00090: failed to allocate memory for cluster database ORADEBUG command 原因： Could not allocate memory needed to execute cluster database oradebug. 解决： Reissue the command on each instance with single-instance oradebug. ORA-00091: LARGE_POOL_SIZE must be at least string
原因： The value of LARGE_POOL_SIZE is below the minimum size. 解决： Increase the value of LARGE_POOL_SIZE past the minimum size.
ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
原因： The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.
解决： Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.
ORA-00093: %s must be between string and string 原因： The parameter value is not in a valid range.
解决： Modify the parameter value to be within the specified range. ORA-00094: %s requires an integer value 原因： The parameter value is not an integer.
解决： Modify the parameter value to be an integer.
ORA-00096: invalid value string for parameter string, must be from among string 原因： The value for the initialization parameter is invalid. 解决： Choose a value as indicated by the message.
ORA-00097: use of Oracle SQL feature not in SQL92 string Level 原因： Usage of Oracle\解决： none
ORA-00100: no data found
第6页
原因： An application made reference to unknown or inaccessible data.
解决： 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.
ORA-00101: invalid specification for system parameter DISPATCHERS 原因： The syntax for the DISPATCHERS parameter is incorrect. 解决： Refer to the manual for correct syntax.
ORA-00102: network protocol string cannot be used by dispatchers
原因： The network specified in DISPATCHERS does not have the functionality required by the dispatchers.
解决： Refer to the manual on network protocols supported by the dispatchers. ORA-00103: invalid network protocol; reserved for use by dispatchers
原因： The network specified in the SQL*Net connect string is reserved for use by the dispatchers.
解决： Specify other network protocols in the connection string.
ORA-00104: deadlock detected; all public servers blocked waiting for resources
原因： 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. 解决： 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. ORA-00105: too many dispatcher configurations
原因： Too many dispatcher configurations have been specified. No more can be added. 解决： Consolidate the dispatcher configurations if possible.
ORA-00106: cannot startup/shutdown database when connected to a dispatcher
原因： An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.
解决： 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. ORA-00107: failed to connect to ORACLE listener process
原因： Most likely due to the fact that ORACLE listener has not been started.
解决： Start ORACLE listener if it has not been started. Or else contact your ORACLE representative.
ORA-00108: failed to set up dispatcher to accept connection asynchronously
原因： Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.
解决： Contact your ORACLE representative.
ORA-00109: invalid value for attribute string: string
原因： The value specified for the attribute was incorrect. 解决： Refer to the manual for the proper values.
ORA-00110: invalid value string for attribute string, must be between string and string 原因： The value specified for the attribute was incorrect. 解决： Specify a value within the range allowed. ORA-00111: invalid attribute string
第7页
原因： The specified attribute was not recognized.
解决： Refer to the manual for the proper keyword to use to specify a dispatcher attribute. ORA-00112: value of string is null
原因： The attribute was specified with no value. 解决： Specify a non-null value.
ORA-00113: protocol name string is too long
原因： A protocol name specified in the DISPATCHERS system parameter is too long. 解决： Use a valid protocol name for the DISPATCHERS value.
ORA-00114: missing value for system parameter SERVICE_NAMES
原因： No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.
解决： 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. ORA-00115: connection refused; dispatcher connection table is full
原因： A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.
解决： Connect to a different dispatcher, or use a dedicated server. ORA-00116: SERVICE_NAMES name is too long
原因： A service name specified in the SERVICE_NAMES system parameter is too long. 解决： Use a shorter name in the SERVICE_NAMES value (<= 255 chars). ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified 原因： PROTOCOL, ADDRESS or DESCRIPTION was not specified.
解决： Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified 原因： More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
解决： Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
ORA-00119: invalid specification for system parameter string 原因： The syntax for the specified parameter is incorrect.
解决： Refer to the Oracle Reference Manual for the correct syntax. ORA-00122: cannot initialize network configuration 原因： ORACLE could not initialize SQL*Net version 2. 解决： Check the error stack for detailed information. ORA-00123: idle public server terminating
原因： Too many idle servers were waiting on the common queue. 解决： This error is used internally, no action is required. ORA-00125: connection refused; invalid presentation
原因： The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
解决： Correct the PRESENTATION specified in the TNS address. ORA-00126: connection refused; invalid duplicity
原因： The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
第8页
解决： Correct the DUPLICITY specified in the TNS address. ORA-00127: dispatcher string does not exist
原因： There is currently no dispatcher running with the specified name.
解决： Retry with a name of the form \ORA-00128: this command requires a dispatcher name 原因： Wrong syntax for ALTER SYSTEM SHUTDOWN
解决： Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] \ORA-00129: listener address validation failed \
原因： An error was encountered while validating the listener address. 解决： Resolve error or contact your ORACLE representative. ORA-00130: invalid listener address \
原因： The listener address specification is not valid.
解决： Make sure that all fields in the listener address (protocol, port, host, key, ...) are correct. ORA-00131: network protocol does not support registration \ 原因： The specified protocol does not support async notification.
解决： Refer to the manual for information on supported network protocols. ORA-00132: syntax error or unresolved network name \ 原因： Listener address has syntax error or cannot be resolved.
解决： 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.
ORA-00133: value of string is too long
原因： The value specified for the attribute was too long.
解决： Use shorter names and keywords or remove unneeded blanks. ORA-00134: invalid DISPATCHERS specification #string
原因： The syntax for the n-th DISPATCHERS specification was incorrect. 解决： Refer to the Oracle Reference Manual for the correct syntax. ORA-00150: duplicate transaction ID
原因： Attempted to start a new transaction with an ID already in use by an existing transaction. 解决： Check your application. ORA-00151: invalid transaction ID
原因： The specified transaction ID does not correspond to an existing valid transaction. 解决： Check your application.
ORA-00152: current session does not match requested session
原因： The current session is not the same as the session that was passed into a upixado() call. 解决： Check your application.
ORA-00153: internal error in XA library
原因： The XA library could not access thread-specific pointers. 解决： Contact customer support.
ORA-00154: protocol error in transaction monitor
原因： The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.
解决： Contact the transaction monitor customer support.
ORA-00155: cannot perform work outside of global transaction
第9页
原因： 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.
解决： 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.
ORA-00160: global transaction length string is greater than maximum (string)
原因： An external global transaction ID with a too large length field was passed in. 解决： Report the problem to your external transaction coordinator vendor.
ORA-00161: transaction branch length string is illegal (maximum allowed string)
原因： An external transaction branch ID with a length either too large or 0 was passed in. 解决： Report the problem to your external transaction coordinator vendor. ORA-00162: external dbid length string is greater than maximum (string) 原因： An external database name with too large a length field was passed in. 解决： Report the problem to your external transaction coordinator vendor.
ORA-00163: internal database name length string is greater than maximum (string) 原因： An internal database name with a too large length field was passed in. 解决： Report the problem to your external transaction coordinator vendor.
ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction
原因： A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.
解决： Roll back or commit the current distributed transaction first.
ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed 原因： A request was made by the application to start a migratable distributed autonomous transaction with remote operation. 解决： none
ORA-00166: remote/local nesting level is too deep 原因： 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.
解决： Rearrange the query or co-locate the functions with the tables. ORA-00200: control file could not be created
原因： It was not possible to create the control file.
解决： Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
ORA-00201: control file version string incompatible with ORACLE version string 原因： The control file was created by incompatible software.
解决： Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release. ORA-00202: control file: \
原因： This message reports the name file involved in other messages. 解决： See associated error messages for a description of the problem. ORA-00203: using the wrong control files
原因： The mount ID in the control file is not the same as the mount ID in the control file used by
第10页