11g Release 2 Oracle Database Error Message 11.2 - E17766-03 解析与指南

需积分: 5 145 浏览量更新于2024-06-25 收藏 44.12MB PDF 举报

Oracle Database Error Messages 11g Release 2 (11.2) - E17766-03 是一份官方文档，发布于2013年7月，针对Oracle数据库11g Release 2版本提供了详细的错误代码和相应的解释。这份文档是Oracle公司的重要参考资料，包含了在数据库操作过程中可能遇到的错误代码列表，如E17766，这些错误代码代表了不同的问题状态，可能是数据一致性问题、性能瓶颈、系统配置异常或其他与数据库运行相关的故障。该文档强调了版权保护和使用限制，指出所有软件及相关文档都受许可证协议约束，用户只能在许可范围内使用，例如复制、修改或分发，除非法律另有规定。未经许可，禁止进行逆向工程、解体或反编译软件的行为，这是为了保护Oracle的技术知识产权。文档内容可能会随着技术更新而改变，并且不保证完全无误。如果用户发现任何错误，应通过正式渠道提交给Oracle以便修正。特别地，对于那些被美国政府或其代理机构授权使用该软件的用户，文档还附有适用的政府用户通知，表明Oracle程序在政府环境中可能受到特定的法律和规定约束。 Oracle Database Error Messages 11g Release 2 (11.2) - E17766-03是数据库管理员和开发人员在处理Oracle 11g数据库问题时的重要参考工具，它提供了实用的故障排除指南，帮助用户快速定位和解决各种技术难题。理解和掌握这些错误代码及其含义，对于确保数据库系统的稳定运行至关重要。

2-8 Oracle Database Error Messages

Cause: An invalid instance number was specified in a cluster database

ORADEBUG command.

Action: Reissue the command with valid instance numbers.

ORA-00090: failed to allocate memory for cluster database ORADEBUG command

Cause: Could not allocate memory needed to execute cluster database oradebug.

Action: Reissue the command on each instance with single-instance oradebug.

ORA-00091: LARGE_POOL_SIZE must be at least string

Cause: The value of LARGE_POOL_SIZE is below the minimum size.

Action: Increase the value of LARGE_POOL_SIZE past the minimum size.

ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_

ALLOC

Cause: The value of LARGE_POOL_SIZE is less than the value of LARGE_

POOL_MIN_ALLOC.

Action: Increase the value of LARGE_POOL_SIZE past the value of LARGE_

POOL_MIN_ALLOC.

ORA-00093: string must be between string and string

Cause: The parameter value is not in a valid range.

Action: Modify the parameter value to be within the specified range.

ORA-00094: string requires an integer value

Cause: The parameter value is not an integer.

Action: Modify the parameter value to be an integer.

ORA-00096: invalid value string for parameter string, must be from among string

Cause: The value for the initialization parameter is invalid.

Action: Choose a value as indicated by the message.

ORA-00097: use of Oracle SQL feature not in SQL92 string Level

Cause: Usage of Oracle's SQL extensions.

Action: None

ORA-00098: creating or mounting the database requires a parameter file

Cause: An attempt was made to create or mount the database when the instance

was started without a parameter file.

Action: Restart the instance with a parameter file.

ORA-00099: warning: no parameter file specified for string instance

Cause: Even though no parameter file was specified, the instance was started with

all default values.

Action: None

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.

ORA-00000 to ORA-00852 2-9

ORA-00101: invalid specification for system parameter DISPATCHERS

Cause: The syntax for the DISPATCHERS parameter is incorrect.

Action: Refer to the manual for correct syntax.

ORA-00102: network protocol string cannot be used by dispatchers

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.

ORA-00103: invalid network protocol; reserved for use by 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.

ORA-00104: deadlock detected; all public servers blocked waiting for resources

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.

ORA-00105: too many dispatcher configurations

Cause: Too many dispatcher configurations have been specified. No more can be

added.

Action: Consolidate the dispatcher configurations if possible.

ORA-00106: cannot startup/shutdown database when connected to a dispatcher

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.

ORA-00107: failed to connect to ORACLE listener process

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.

ORA-00108: failed to set up dispatcher to accept connection asynchronously

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.

ORA-00109: invalid value for attribute string: string

Cause: The value specified for the attribute was incorrect.

Action: Refer to the manual for the proper values.

ORA-00110: invalid value string for attribute string, must be between string and

string

Cause: The value specified for the attribute was incorrect.

Action: Specify a value within the range allowed.

2-10 Oracle Database Error Messages

ORA-00111: invalid attribute string

Cause: The specified attribute was not recognized.

Action: Refer to the manual for the proper keyword to use to specify a dispatcher

attribute.

ORA-00112: value of string is null

Cause: The attribute was specified with no value.

Action: Specify a non-null value.

ORA-00113: protocol name string is too long

Cause: A protocol name specified in the DISPATCHERS system parameter is too

long.

Action: Use a valid protocol name for the DISPATCHERS value.

ORA-00114: missing value for system parameter SERVICE_NAMES

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.

ORA-00115: connection refused; dispatcher connection table is full

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.

ORA-00116: SERVICE_NAMES name is too long

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).

ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified

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.

ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be

specified

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.

ORA-00119: invalid specification for system parameter string

Cause: The syntax for the specified parameter is incorrect.

Action: Refer to the Oracle Reference Manual for the correct syntax.

ORA-00122: cannot initialize network configuration

Cause: ORACLE could not initialize SQL*Net version 2.

Action: Check the error stack for detailed information.

ORA-00123: idle public server terminating

ORA-00000 to ORA-00852 2-11

Cause: Too many idle servers were waiting on the common queue.

Action: This error is used internally, no action is required.

ORA-00125: connection refused; invalid presentation

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.

ORA-00126: connection refused; invalid duplicity

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.

ORA-00127: dispatcher string does not exist

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.

ORA-00128: this command requires a dispatcher name

Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN

Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ]

'dispatcher name'

ORA-00129: listener address validation failed 'string'

Cause: An error was encountered while validating the listener address.

Action: Resolve error or contact your ORACLE representative.

ORA-00130: invalid listener address 'string'

Cause: The listener address specification is not valid.

Action: Make sure that all fields in the listener address (protocol, port, host, key,

...) are correct.

ORA-00131: network protocol does not support registration 'string'

Cause: The specified protocol does not support async notification.

Action: Refer to the manual for information on supported network protocols.

ORA-00132: syntax error or unresolved network name 'string'

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.

ORA-00133: value of string is too long

Cause: The value specified for the attribute was too long.

Action: Use shorter names and keywords or remove unneeded blanks.

ORA-00134: invalid DISPATCHERS specification #string

Cause: The syntax for the n-th DISPATCHERS specification was incorrect.

Action: Refer to the Oracle Reference Manual for the correct syntax.

ORA-00135: missing attribute string

Cause: The indicated mandatory attribute was not specified.

2-12 Oracle Database Error Messages

Action: Specify a non-null value for the attribute.

ORA-00136: invalid LISTENER_NETWORKS specification #string

Cause: The syntax for the nth LISTENER_NETWORKS specification was invalid.

Action: Refer to the Oracle Reference Manual for the correct syntax.

ORA-00137: invalid LISTENER_NETWORKS specification with NAME=string

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.

ORA-00138: all addresses specified for attribute string are invalid

Cause: All of the specified addresses or aliases for the attribute were invalid.

Action: Specify at least one valid address or alias.

ORA-00139: duplicate attribute string

Cause: The indicated attribute was specified more than once.

Action: Specify the attribute at most once.

ORA-00150: duplicate transaction ID

Cause: Attempted to start a new transaction with an ID already in use by an

existing transaction.

Action: Check your application.

ORA-00151: invalid transaction ID

Cause: The specified transaction ID does not correspond to an existing valid

transaction.

Action: Check your application.

ORA-00152: current session does not match requested session

Cause: The current session is not the same as the session that was passed into a

upixado() call.

Action: Check your application.

ORA-00153: internal error in XA library

Cause: The XA library could not access thread-specific pointers.

Action: Contact customer support.

ORA-00154: protocol error in transaction monitor

Cause: The transaction monitor returned TMJOIN on an AX_REG call but the

transaction was locally suspended.

Action: Contact the transaction monitor customer support.

ORA-00155: cannot perform work outside of global transaction

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.

剩余3101页未读，继续阅读

weixin_40191861_zj

粉丝: 86
资源: 1万+

11g Release 2 Oracle Database Error Message 11.2 - E17766-03 解析与...

最新资源

11g Release 2 Oracle Database Error Message 11.2 - E17766-03 解析与...

Oracle Database Error Messages 11g Release 2 11 2

ORACLE文档--Database Error Messages

Oracle Database Release Notes 11g Release 2 (11.2) for Linux-34.

Oracle Database Upgrade Guide 11g Release 2 (11.2-198

Oracle Database Reference 11g Release 2 (11.2)-1306

Oracle Database Concepts 11g Release 2 (11.2)-472

Oracle Database XStream Guide 11g Release 2 (11.2)-302

Oracle Database Security Guide 11g Release 2 (11.2)-444

Oracle Database Sample Schemas 11g Release 2 (11.2)-48.pdf

Oracle Database Installation Guide 11g Release 2 (11.2) for HP-U

最新资源