12c Release 1 Oracle Database Error Messages解决方案概览

需积分: 5 114 浏览量更新于2024-06-13 收藏 56.23MB PDF 举报

Oracle Database Error Messages 12c Release 1 (12.1) 是一份详细的文档，包含了Oracle数据库在12.1版本中可能遇到的错误消息列表和解决方案。这份文档是Oracle官方发布的重要参考资料，版权归属Oracle及其关联公司，强调了用户在使用时必须遵守许可证协议中的使用和保密限制，禁止未经授权的复制、修改或分发软件及文档。文档提供了对各种错误代码（如E49325-06）的解释，帮助数据库管理员理解和解决运行过程中可能出现的问题。错误代码E49325-06的具体含义和处理方法会在文档中详细阐述，包括但不限于错误的原因分析、故障排查步骤以及可能的修复策略。用户在遇到这些错误时，可以直接参考文档寻找对应解决方案，提高了问题解决的效率。值得注意的是，文档强调信息可能会随时更改，且不保证无误，因此在使用时建议定期更新。对于政府用户或代理政府购买该软件的用户，文档还提到了特定的法律义务，比如可能需要遵守美国政府的使用规定。 Oracle Database Error Messages 12c Release 1 (12.1) E49325-06 是一个实用的工具，对于任何从事Oracle数据库管理和维护的专业人士来说，都是不可或缺的学习和参考资源，能够帮助他们快速定位和解决数据库运行中的技术难题。

2-8 Oracle Database Error Messages

Cause: An invalid attempt was made to dump the current call heap.

Action: Wait until the process starts a call.

ORA-00086: user call does not exist

Cause: An invalid attempt was made to dump the user call heap.

Action: Wait until the process starts a call.

ORA-00087: command cannot be executed on remote instance

Cause: Cluster database command issued for non cluster database ORADEBUG

command.

Action: Issue the command without the cluster database syntax.

ORA-00088: command cannot be executed by shared server

Cause: Debug command issued on shared server.

Action: Reissue the command using a dedicated server.

ORA-00089: invalid instance number in ORADEBUG command

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-00000 to ORA-00877 2-9

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

2-10 Oracle Database Error Messages

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.

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-00000 to ORA-00877 2-11

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-00120: invalid 'shared_servers' value for the PDB

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

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

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'

2-12 Oracle Database Error Messages

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.

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.

剩余3921页未读，继续阅读

yybbccddtt

粉丝: 1
资源: 536

12c Release 1 Oracle Database Error Messages解决方案概览

oa常见问题解决方法共11页.pdf.zip

OA系统解决方案.pdf

OA客户端常见问题及解决方案汇总.pdf

数据库坏块(ORA-01578)的解决方法.pdf

Oracle11g在实践教学中的常见问题及解决办法.pdf

congos常见问题解答.pdf

如何解决Oracle 常见错误 ORA-04031(PDF)

oracle开发初期的几个棘手问题的解决方法.pdf

ORA_ROWSCN伪列在Oracle历史数据迁移中的应用研究.pdf

BLOG_【故障处理】Oracle_lhr_ORA-01565 告警日志报“ORA-01565 Unable To open Spfile”.pdf

最新资源