{"id":1645,"date":"2016-02-03T16:44:11","date_gmt":"2016-02-03T13:44:11","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1645"},"modified":"2016-10-17T13:13:25","modified_gmt":"2016-10-17T10:13:25","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-00101-to-ora-00200","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-00101-to-ora-00200\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-00101 to ORA-00200"},"content":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-00101 to ORA-00200<\/strong><\/p>\n

ORA-00101: invalid specification for system parameter DISPATCHERS<\/strong><\/p>\n

Cause:<\/strong> The syntax for the DISPATCHERS parameter is incorrect.<\/p>\n

Action:<\/strong> Refer to the manual for correct syntax.<\/p>\n

ORA-00102: network protocol string cannot be used by dispatchers<\/strong><\/p>\n

Cause:<\/strong> The network specified in DISPATCHERS does not have the functionality required by the dispatchers.<\/p>\n

Action:<\/strong> Refer to the manual on network protocols supported by the dispatchers.<\/p>\n

ORA-00103: invalid network protocol; reserved for use by dispatchers<\/strong><\/p>\n

Cause:<\/strong> The network specified in the SQL*Net connect string is reserved for use by the dispatchers.<\/p>\n

Action:<\/strong> Specify other network protocols in the connection string.<\/p>\n

ORA-00104: deadlock detected; all public servers blocked waiting for resources<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

Action:<\/strong> 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.
\n<\/p>\n

ORA-00105: too many dispatcher configurations<\/strong><\/p>\n

Cause:<\/strong> Too many dispatcher configurations have been specified. No more can be added.<\/p>\n

Action:<\/strong> Consolidate the dispatcher configurations if possible.<\/p>\n

ORA-00106: cannot startup\/shutdown database when connected to a dispatcher<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to startup\/shutdown database when connected to a shared server via a dispatcher.<\/p>\n

Action:<\/strong> 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.<\/p>\n

ORA-00107: failed to connect to ORACLE listener process<\/strong><\/p>\n

Cause:<\/strong> Most likely due to the fact that ORACLE listener has not been started.<\/p>\n

Action:<\/strong> Start ORACLE listener if it has not been started. Or else contact your ORACLE representative.<\/p>\n

ORA-00108: failed to set up dispatcher to accept connection asynchronously<\/strong><\/p>\n

Cause:<\/strong> Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.<\/p>\n

Action:<\/strong> Contact your ORACLE representative.<\/p>\n

ORA-00109: invalid value for attribute string: string<\/strong><\/p>\n

Cause:<\/strong> The value specified for the attribute was incorrect.<\/p>\n

Action:<\/strong> Refer to the manual for the proper values.<\/p>\n

ORA-00110: invalid value string for attribute string, must be between string and string<\/strong><\/p>\n

Cause:<\/strong> The value specified for the attribute was incorrect.<\/p>\n

Action:<\/strong> Specify a value within the range allowed.<\/p>\n

ORA-00111: invalid attribute string<\/strong><\/p>\n

Cause:<\/strong> The specified attribute was not recognized.<\/p>\n

Action:<\/strong> Refer to the manual for the proper keyword to use to specify a dispatcher attribute.<\/p>\n

ORA-00112: value of string is null<\/strong><\/p>\n

Cause:<\/strong> The attribute was specified with no value.<\/p>\n

Action:<\/strong> Specify a non-null value.<\/p>\n

ORA-00113: protocol name string is too long<\/strong><\/p>\n

Cause:<\/strong> A protocol name specified in the DISPATCHERS system parameter is too long.<\/p>\n

Action:<\/strong> Use a valid protocol name for the DISPATCHERS value.<\/p>\n

ORA-00114: missing value for system parameter SERVICE_NAMES<\/strong><\/p>\n

Cause:<\/strong> No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.<\/p>\n

Action:<\/strong> 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.<\/p>\n

ORA-00115: connection refused; dispatcher connection table is full<\/strong><\/p>\n

Cause:<\/strong> A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.<\/p>\n

Action:<\/strong> Connect to a different dispatcher, or use a dedicated server.<\/p>\n

ORA-00116: SERVICE_NAMES name is too long<\/strong><\/p>\n

Cause:<\/strong> A service name specified in the SERVICE_NAMES system parameter is too long.<\/p>\n

Action:<\/strong> Use a shorter name in the SERVICE_NAMES value (<= 255 chars).\n\nORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified<\/strong><\/p>\n

Cause:<\/strong> PROTOCOL, ADDRESS or DESCRIPTION was not specified.<\/p>\n

Action:<\/strong> Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.<\/p>\n

ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified<\/strong><\/p>\n

Cause:<\/strong> More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.<\/p>\n

Action:<\/strong> Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.<\/p>\n

ORA-00119: invalid specification for system parameter string<\/strong><\/p>\n

Cause:<\/strong> The syntax for the specified parameter is incorrect.<\/p>\n

Action:<\/strong> Refer to the Oracle Reference Manual for the correct syntax.<\/p>\n

ORA-00122: cannot initialize network configuration<\/strong><\/p>\n

Cause:<\/strong> ORACLE could not initialize SQL*Net version 2.<\/p>\n

Action:<\/strong> Check the error stack for detailed information.<\/p>\n

ORA-00123: idle public server terminating<\/strong><\/p>\n

Cause:<\/strong> Too many idle servers were waiting on the common queue.<\/p>\n

Action:<\/strong> This error is used internally, no action is required.<\/p>\n

ORA-00125: connection refused; invalid presentation<\/strong><\/p>\n

Cause:<\/strong> The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.<\/p>\n

Action:<\/strong> Correct the PRESENTATION specified in the TNS address.<\/p>\n

ORA-00126: connection refused; invalid duplicity<\/strong><\/p>\n

Cause:<\/strong> The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.<\/p>\n

Action:<\/strong> Correct the DUPLICITY specified in the TNS address.<\/p>\n

ORA-00127: dispatcher string does not exist<\/strong><\/p>\n

Cause:<\/strong> There is currently no dispatcher running with the specified name.<\/p>\n

Action:<\/strong> Retry with a name of the form “D###” denoting an existing dispatcher process.<\/p>\n

ORA-00128: this command requires a dispatcher name<\/strong><\/p>\n

Cause:<\/strong> Wrong syntax for ALTER SYSTEM SHUTDOWN<\/p>\n

Action:<\/strong> Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] ‘dispatcher name’<\/p>\n

ORA-00129: listener address validation failed ‘string’<\/strong><\/p>\n

Cause:<\/strong> An error was encountered while validating the listener address.<\/p>\n

Action:<\/strong> Resolve error or contact your ORACLE representative.<\/p>\n

ORA-00130: invalid listener address ‘string’<\/strong><\/p>\n

Cause:<\/strong> The listener address specification is not valid.<\/p>\n

Action:<\/strong> Make sure that all fields in the listener address (protocol, port, host, key, …) are correct.<\/p>\n

ORA-00131: network protocol does not support registration ‘string’<\/strong><\/p>\n

Cause:<\/strong> The specified protocol does not support async notification.<\/p>\n

Action:<\/strong> Refer to the manual for information on supported network protocols.<\/p>\n

ORA-00132: syntax error or unresolved network name ‘string’<\/strong><\/p>\n

Cause:<\/strong> Listener address has syntax error or cannot be resolved.<\/p>\n

Action:<\/strong> 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.<\/p>\n

ORA-00133: value of string is too long<\/strong><\/p>\n

Cause:<\/strong> The value specified for the attribute was too long.<\/p>\n

Action:<\/strong> Use shorter names and keywords or remove unneeded blanks.<\/p>\n

ORA-00134: invalid DISPATCHERS specification #string<\/strong><\/p>\n

Cause:<\/strong> The syntax for the n-th DISPATCHERS specification was incorrect.<\/p>\n

Action:<\/strong> Refer to the Oracle Reference Manual for the correct syntax.<\/p>\n

ORA-00150: duplicate transaction ID<\/strong><\/p>\n

Cause:<\/strong> Attempted to start a new transaction with an ID already in use by an existing transaction.<\/p>\n

Action:<\/strong> Check your application.<\/p>\n

ORA-00151: invalid transaction ID<\/strong><\/p>\n

Cause:<\/strong> The specified transaction ID does not correspond to an existing valid transaction.<\/p>\n

Action:<\/strong> Check your application.<\/p>\n

ORA-00152: current session does not match requested session<\/strong><\/p>\n

Cause:<\/strong> The current session is not the same as the session that was passed into a upixado() call.<\/p>\n

Action:<\/strong> Check your application.<\/p>\n

ORA-00153: internal error in XA library<\/strong><\/p>\n

Cause:<\/strong> The XA library could not access thread-specific pointers.<\/p>\n

Action:<\/strong> Contact customer support.<\/p>\n

ORA-00154: protocol error in transaction monitor<\/strong><\/p>\n

Cause:<\/strong> The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.<\/p>\n

Action:<\/strong> Contact the transaction monitor customer support.<\/p>\n

ORA-00155: cannot perform work outside of global transaction<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

Action:<\/strong> 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.<\/p>\n

ORA-00160: global transaction length string is greater than maximum (string)<\/strong><\/p>\n

Cause:<\/strong> An external global transaction ID with a too large length field was passed in.<\/p>\n

Action:<\/strong> Report the problem to your external transaction coordinator vendor.<\/p>\n

ORA-00161: transaction branch length string is illegal (maximum allowed string)<\/strong><\/p>\n

Cause:<\/strong> An external transaction branch ID with a length either too large or 0 was passed in.<\/p>\n

Action:<\/strong> Report the problem to your external transaction coordinator vendor.<\/p>\n

ORA-00162: external dbid length string is greater than maximum (string)<\/strong><\/p>\n

Cause:<\/strong> An external database name with too large a length field was passed in.<\/p>\n

Action:<\/strong> Report the problem to your external transaction coordinator vendor.<\/p>\n

ORA-00163: internal database name length string is greater than maximum (string)<\/strong><\/p>\n

Cause:<\/strong> An internal database name with a too large length field was passed in.<\/p>\n

Action:<\/strong> Report the problem to your external transaction coordinator vendor.<\/p>\n

ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction<\/strong><\/p>\n

Cause:<\/strong> A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.<\/p>\n

Action:<\/strong> Roll back or commit the current distributed transaction first.<\/p>\n

ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed<\/strong><\/p>\n

Cause:<\/strong> A request was made by the application to start a migratable distributed autonomous transaction with remote operation.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-00166: remote\/local nesting level is too deep<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

Action:<\/strong> Rearrange the query or co-locate the functions with the tables.<\/p>\n

ORA-00200: control file could not be created<\/strong><\/p>\n

Cause:<\/strong> It was not possible to create the control file.<\/p>\n

Action:<\/strong> Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.<\/p>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-00101 to ORA-00200 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…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[14,32,54],"class_list":["post-1645","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-database-administration","tag-oracle-administration","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-qx","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1645","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=1645"}],"version-history":[{"count":6,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1645\/revisions"}],"predecessor-version":[{"id":1655,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1645\/revisions\/1655"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1645"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1645"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1645"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}