NNO-00074: downloading region from server string

NNO-00074: downloading region from server string

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00073: loading server config from region database

NNO-00073: loading server config from region database

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00072: loading from region database

NNO-00072: loading from region database

Cause: normal

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00071: cannot construct cache checkpoint file name

NNO-00071: cannot construct cache checkpoint file name

Cause: the server could not construct a system-dependent file name.

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00070: administrative region has changed, reloading domain data

NNO-00070: administrative region has changed, reloading domain data

Cause: An informational message written to the log file whenever the server s configuration has changed, and the server is reloading the new configuration from the configuration database.

Action: none

NNO-00069: warning: too many administrative region check failures, checking disabled

NNO-00069: warning: too many administrative region check failures, checking disabled

Cause: a warning issued whenever the server has continuously failed for three days in its attempts to connect to the configuration database. The server disables reload checking. Reload checking can later be re-enabled from the Oracle Network Manager or the Oracle Names control program.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down.

NNO-00068: warning: administrative region check failed, next check in number seconds

NNO-00068: warning: administrative region check failed, next check in number seconds

Cause: this warning is issued whenever the server fails to connect to the configuration database to see if any configuration data has changed. The server will automatically begin reissuing reload checks more frequently, and will eventually give up if connections fail continuously for three days.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database.

NNO-00067: server reload check countdown aborted

NNO-00067: server reload check countdown aborted

Cause: An informational message written to the log file whenever the Oracle Names control program halts a reload request previously sent to the server

Action: none

NNO-00066: server will perform reload check of administrative region in number seconds

NNO-00066: server will perform reload check of administrative region in number seconds

Cause: An informational message written to the log file whenever the Oracle Network Manager or the Oracle Names control program send a reload request to the server.

Action: none

NNO-00065: loading cached data from checkpoint file string

NNO-00065: loading cached data from checkpoint file string

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00064: loading domain data from checkpoint file string

NNO-00064: loading domain data from checkpoint file string

Cause: An informational message written to the log file when the server has been forced to load from its most recent domain checkpoint file, by setting the names.no_region_database parameter to TRUE.

Action: none

NNO-00063: cannot construct domain checkpoint file name

NNO-00063: cannot construct domain checkpoint file name

Cause: the server could not construct a system-dependent file name.

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00062: cannot load domain data from configuration database

NNO-00062: cannot load domain data from configuration database

Cause: An error was encountered while trying to load the server s domain data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down.

NNO-00061: loading data for domain string

NNO-00061: loading data for domain string

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00060: loading server topology from checkpoint file string

NNO-00060: loading server topology from checkpoint file string

Cause: An informational message written to the log file when the server has been forced to load from its most recent topology checkpoint file, by setting the names.no_region_database parameter to TRUE.

Action: none

NNO-00059: cannot construct topology checkpoint file name

NNO-00059: cannot construct topology checkpoint file name

Cause: the server could not construct a system-dependent file name.

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00058: cannot load topology data from configuration database

NNO-00058: cannot load topology data from configuration database

Cause: An error was encountered while trying to load the server s topology data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down.

NNO-00057: loading and verifying topology data

NNO-00057: loading and verifying topology data

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00056: warning: domain minimum TTL must be between number and number, set to number seconds

NNO-00056: warning: domain minimum TTL must be between number and number, set to number seconds

Cause: The server s configuration contains a domain description with an invalid minimum TTL. This error is not fatal; the server will automatically set the TTL to a default value which is suitable for most uses.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00055: invalid domain minimum TTL string

NNO-00055: invalid domain minimum TTL string

Cause: The server s configuration contains a domain description with an invalid minimum TTL.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00054: invalid domain name string

NNO-00054: invalid domain name string

Cause: The server s configuration contains a domain description with an invalid name.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00053: duplicate domain description for domain string

NNO-00053: duplicate domain description for domain string

Cause: The server s configuration contains duplicate domain descriptions in the domain description list.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00052: invalid domain description list

NNO-00052: invalid domain description list

Cause: The server s configuration contains an invalid domain description list.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00051: domain count number exceeds maximum of number, first number will be loaded

NNO-00051: domain count number exceeds maximum of number, first number will be loaded

Cause: The server s configuration contains more domains than the server can support.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00050: serious errors in configuration data, server cannot run

NNO-00050: serious errors in configuration data, server cannot run

Cause: The server s configuration data has a problem of some sort which prevents the server from starting.

Action: Previous error messages in the log file will specify the exact problems leading to the shutdown. The problem most frequently occurs when the network is broken up into multiple administrative regions and the delegation points are incorrect. Read the Oracle Names documentation sections on region delegation and ensure that their directions are being followed correctly.

NNC-00501: warning: string parameter value must be between number and number, setting to number

NNC-00501: warning: string parameter value must be between number and number, setting to number

Cause: The named parameter value is invalid or outside legal boundary values.

Action: Make sure the parameter value is a number, and falls between valid minimum and maximum values, as specified in the error text.

NNC-00500: warning: string parameter value is illegal, setting to string

NNC-00500: warning: string parameter value is illegal, setting to string

Cause: The named parameter value is invalid.

Action: Make sure the parameter value is formatted correctly. Valid choices for boolean parameter values are TRUE, FALSE, YES, NO, ON, and OFF.

NNC-00431: NS address does not match any of the current addresses

NNC-00431: NS address does not match any of the current addresses

Cause: When delegating a domain, the address of the Nameserver is provided by the client. If the nameserver already exists, then it already has address(es) associated with it. So, the address supplied by the client must match one of them. Otherwise, this error occurs.

Action: Not normally visible to the user, except when using name server control program. If the error occurs when using the control program, either provide an one of the existing addresses of the name server or delegate the domain to a new nameserver.

NNC-00430: Database not accessible

NNC-00430: Database not accessible

Cause: When a database is used for consistency between different nameservers, any modify operation should not only modify the cache but also the database. And if the database is not accessible, this error occurs.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, make sure database is available and then re-execute the operation. If error persists, contact Worldwide Customer Support.

NNC-00429: invalid octet string literal string

NNC-00429: invalid octet string literal string

Cause: A caller provided the name server program interface with an invalid octet string string value.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid octet string argument. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00427: server does not support this version of the protocol

NNC-00427: server does not support this version of the protocol

Cause: A name server message with an incompatible protocol version was received by a name server or the name server program interface. This problem will occur when there are clients and servers with widely varying protocol versions that are trying to communicate.

Action: upgrade older client and server software so it is compatible with newer software.

NNC-00426: no such data type

NNC-00426: no such data type

Cause: A caller attempted to create a data item, and could not because the data item s type does not exist.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the operation with an existent data type. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00425: meta-data violation

NNC-00425: meta-data violation

Cause: A caller issued a name server modification request and that request cannot be processed because it would violate data type meta-data constraints.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, examine the

NNC-00424: invalid address string

NNC-00424: invalid address string

Cause: A caller provided the name server program interface with an invalid address value.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid address argument. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00423: invalid data item syntax code string

NNC-00423: invalid data item syntax code string

Cause: A caller has provided an invalid data type code to the name server program interface.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid type name. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00422: invalid data type name string

NNC-00422: invalid data type name string

Cause: A caller has provided an invalid data type name to the name server program interface.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid type name. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00421: invalid modification directive string, must be between string and string

NNC-00421: invalid modification directive string, must be between string and string

Cause: An internal function has called the name server program interface with illegal arguments.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00420: operation not allowed

NNC-00420: operation not allowed

Cause: A name server request cannot be processed because the server which received the operation is not allowed to process it. The problem typically occurs when an administrator has disabled request processing at a particular server for some reason.

Action: Contact your name server administrator to determine why server request processing has been disabled.

NNC-00419: authoritative server is unreachable

NNC-00419: authoritative server is unreachable

Cause: A name server request cannot be processed because the server which received the operation does not own the name specified in the request and cannot locate the server which does own the name. The error is almost always transient, and occurs either because the path between the server receiving the request and the request s final destination has been interrupted, or because the final destination is down.

Action: Not normally visible to the user, except when using the name server control program. Because the error is typically a transient one, retrying the failing operation will usually work. If the failure persists, the name server which is allowed to process the failing operation is probably shut down or unreachable. Contact your name server administrator to make sure that your site s name servers are running, and are properly configured.

NNC-00418: name string cannot be modified because it has children

NNC-00418: name string cannot be modified because it has children

Cause: A caller has attempted to delete or rename a global name, and that name cannot be modified because it has child names underneath it in the name space.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a name that is a leaf node. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00417: name string already exists

NNC-00417: name string already exists

Cause: A caller has attempted to create a new global name, and that name already exists.

Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a name that does not already exist. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00416: user callback function returned error number string

NNC-00416: user callback function returned error number string

Cause: An internal function has called the name server program interface with illegal arguments.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00415: section identifier string is invalid, must be between string and string

NNC-00415: section identifier string is invalid, must be between string and string

Cause: An internal function has called the name server program interface with illegal arguments.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00413: general failure

NNC-00413: general failure

Cause: A name server program interface error occured which did not fall under the heading of any other more specific error condition. The error will usually be followed by more specific lower-level information.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00412: invalid name string

NNC-00412: invalid name string

Cause: The name server program interface was given an invalid global name to process.

Action: Supply a valid domain name. If the error is caused by an internal function, contact Worldwide Customer Support.

NNC-00411: invalid default domain name string

NNC-00411: invalid default domain name string

Cause: The names.default_domain parameter in sqlnet.ora is invalid.

Action: Make sure the parameter value is a valid global name. See your documentation for the characters which may be used in a global name.

NNC-00410: invalid preferred server address list

NNC-00410: invalid preferred server address list

Cause: The names.preferred_servers parameter in sqlnet.ora is malformed.

Action: Make sure the address list is properly formatted.

NNC-00409: temporary name service failure

NNC-00409: temporary name service failure

Cause: There are no name servers available to handle a client request, or a name server was temporarily unable to handle a client request. This situation is almost always temporary, and occurs when the program interface has issued a name server request and not received a timely response from any of its preferred servers. Such delays can occur due to transient network or name server outages or heavy load.

Action: Re-try the failing operation. If the error persists, make sure there is network connectivity between the client and its preferred name servers, and contact your name server administrator to make sure that those name servers are running.

NNC-00408: name string exists but desired data does not

NNC-00408: name string exists but desired data does not

Cause: The user asked for information associated with a global name. The name in question exists, but does not contain the desired type of information.

Action: Re-try the failing operation with a type which the desired name does contain.

NNC-00407: alias loop in name request

NNC-00407: alias loop in name request

Cause: The name service detected an alias loop when trying to retrieve information associated with a global name. An alias loop occurs when an alias name X points to another alias name Y, which in turn points back to X, rather than eventually to a global name which contains data.

Action: Contact your name server administrator to have the alias loop investigated and fixed.

NNC-00406: name string does not exist

NNC-00406: name string does not exist

Cause: The user asked for information associated with a global name that does not exist.

Action: Re-try the failing operation with a global name that exists.

NNC-00405: network failure

NNC-00405: network failure

Cause: The network connection between the client program and the name server has failed, either because the server has shut down, or because the network path to the server has stopped working. This error is usually displayed underneath an error which describes the problem in more detail.

Action: Contact your name server administrator to make sure that the server being connected to is running and listening on the address used, and that there is network connectivity between the two end-points.

NNC-00404: supplied buffer of size string is smaller than minimum size string

NNC-00404: supplied buffer of size string is smaller than minimum size string

Cause: A caller supplied the name server program interface with a memory buffer too small for the interface s requirements. This error is usually displayed underneath an error which describes the problem in more detail.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00403: program interface has not been initialised

NNC-00403: program interface has not been initialised

Cause: An internal function has attempted to de-initialise the name service program interface when it has not yet been initialised.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00402: program interface de-initialization failed

NNC-00402: program interface de-initialization failed

Cause: An internal error occurred while the name server program interface was being de-initialised by an internal function.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00401: program interface initialization failed

NNC-00401: program interface initialization failed

Cause: The name server program interface could not be initialised, probably because of a missing TNS or name server error message file.

Action: Check that SQL*Net has been installed properly and that all message files are in their proper locations.

NNC-00400: memory exhausted

NNC-00400: memory exhausted

Cause: The program interface has run out of memory.

Action: Add more memory or run fewer processes.

NNC-00053: ASN.1 error encountered while sending or receiving message

NNC-00053: ASN.1 error encountered while sending or receiving message

Cause: The name server or the name server program interface attempted to send or receive a message and failed because of an ASN.1 error.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00052: client and server protocol versions are incompatible

NNC-00052: client and server protocol versions are incompatible

Cause: A name server message with an incompatible protocol version was received by a name server or the name server program interface. This problem will occur when there are clients and servers with widely varying protocol versions that are trying to communicate.

Action: upgrade older client and server software so it is compatible with newer software.

NNC-00051: message content error

NNC-00051: message content error

Cause: A corrupted name server message was received by a name server or the name server program interface.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNC-00050: message format error

NNC-00050: message format error

Cause: A corrupted name server message was received by a name server or the name server program interface.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

end-points. NNC-00005: cannot initialization stream subsystem

end-points. NNC-00005: cannot initialization stream subsystem

Cause: The name service stream subsystem could not be started, probably because of a missing TNS error message file.

Action: Check that SQL*Net has been installed properly and that all message files are in their proper locations.

NNC-00004: connection is broken

NNC-00004: connection is broken

Cause: The connection from a name server or client program to another server has been broken, either because that server has shut down, or because the network path to the server has stopped working. This error is usually displayed underneath an error which describes the problem in more detail.

Action: Make sure that the server being connected to is running and listening on the address used, and that there is network connectivity between the two

NNC-00003: error opening stream string

NNC-00003: error opening stream string

Cause: A name server or client program attempted to open a connection to another server and failed, either because the server is down, or because the network path to that server is not working. This error is usually displayed underneath an error which describes the problem in more detail.

Action: Make sure that the server being connected to is listening on the address used, and that there is network connectivity between the two end-points.

NNC-00002: error listening on stream string

NNC-00002: error listening on stream string

Cause: The name server was asked to listen on the specified address, and failed, probably because the address is malformed, or because it uses a SQL*Net protocol adaptor which has not been installed.

Action: Make sure the address is properly formed, and that it uses a protocol adaptor which has been installed on your system.

NNC-00001: maximum number of connections already open

NNC-00001: maximum number of connections already open

Cause: All available name service connections are handling requests.

Action: If the problem occurs when running a name server, increase the values of names.max_open_connections. If the problem occurs in a client program, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

TNS-12699: Native service internal error

TNS-12699: Native service internal error

Cause: An internal error occurred in the native services component.

Action: Enable tracing to determine the exact error. Contact Oracle Customer Support.

TNS-12696: Double Encryption Turned On, login disallowed

TNS-12696: Double Encryption Turned On, login disallowed

Cause: The user is using a Secure Protocol Adapter that has Encryption turned ON as well as ANO Encryption.

Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if possible. Refer to Oracle Advanced Security Administrator s Guide on how to do this.

TNS-12690: Server Authentication failed, login cancelled

TNS-12690: Server Authentication failed, login cancelled

Cause: Server Authentication is required, but the server s credentials were found invalid by the client.

Action: Make sure that the server has a valid set of credentials. Refer to your authentication adapter specific documentation on how to do this.

TNS-12689: Server Authentication required, but not supported

TNS-12689: Server Authentication required, but not supported

Cause: Server Authentication is required for this connection, but not supported by both sides of the connection.

Action: Make sure both sides of the connection have the correct version of Advanced Networking Option, and that the Authentication Adapter supports Server Authentication.

TNS-12688: Login failed: the SecurID server rejected the new pincode

TNS-12688: Login failed: the SecurID server rejected the new pincode

Cause: There are a number of reasons why the SecurID server would refuse a pincode: four, but no more than eight characters.

Action: Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error.

TNS-12687: Credentials expired.

TNS-12687: Credentials expired.

Cause: The credentials that are used to authenticate the user for the requested connection have expired.

Action: Renew your credentials. Refer to the documentation specific for your Network Authentication Adapter on how to do this.

TNS-12686: Invalid command specified for a service

TNS-12686: Invalid command specified for a service

Cause: An operation which does not exist was specified for a native service.

Action: This is a programming error and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support.

TNS-12685: Native service required remotely but disabled locally

TNS-12685: Native service required remotely but disabled locally

Cause: A native service is required by the remote process but native services have been disabled locally.

Action: Enable native services locally or change the configuration parameters on the remote host so that no native services are required.

TNS-12684: encryption or crypto-checksumming: Diffie-Hellman seed too small

TNS-12684: encryption or crypto-checksumming: Diffie-Hellman seed too small

Cause: The sqlnet.crypto_seed parameter in the SQLNET.ORA parameter file for Oracle Advanced Security is too small.

Action: Add more randomly-chosen text to it, perhaps using Network Manager.

TNS-12683: encryption or crypto-checksumming: no Diffie-Hellman seed

TNS-12683: encryption or crypto-checksumming: no Diffie-Hellman seed

Cause: The sqlnet.crypto_seed parameter is missing from the SQLNET.ORA parameters file for Oracle Advanced Security.

Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = randomly-chosen text

TNS-12682: Login failed: the SecurID card is in next PRN mode

TNS-12682: Login failed: the SecurID card is in next PRN mode

Cause: The SecurID card and the SecurID server are out of sync and the server requires the next cardcode to resynchronize the card.

Action: Use one of the programs supplied by Security Dynamics to resynchronize the SecurID card.

TNS-12681: Login failed: the SecurID card does not have a pincode yet

TNS-12681: Login failed: the SecurID card does not have a pincode yet

Cause: The SecurID card that is used to logon to Oracle, does not have a pincode assigned to it.

Action: Use one of the programs supplied by Security Dynamics to assign a pincode to the card.

TNS-12680: Native services disabled but required

TNS-12680: Native services disabled but required

Cause: The process has disabled native services but at least one service is required.

Action: Enable native services or change the configuration file so that none of the available services are required.

TNS-12679: Native services disabled by other process but required

TNS-12679: Native services disabled by other process but required

Cause: The remote process has disabled native services but the local process requires them.

Action: Enable native services on the remote process or disable them locally.

TNS-12678: Authentication disabled but required

TNS-12678: Authentication disabled but required

Cause: The configuration parameters that control whether Oracle Advanced Security authentication is disabled or required were both set to TRUE.

Action: Set one or both of the parameters to FALSE.

TNS-12677: Authentication service not supported by database link

TNS-12677: Authentication service not supported by database link

Cause: The authentication service used by the proxy process (database link) was unable to find the adapter being used by the client in its list of authentication mechanisms.

Action: Specify an authentication adapter that is shared by the client and the server being used for the database link.

TNS-12676: Server received internal error from client

TNS-12676: Server received internal error from client

Cause: The server process received an error from the client which indicated that an internal Oracle Net native services error had occurred.

Action: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Oracle Customer Support.

TNS-12675: External user name not available yet

TNS-12675: External user name not available yet

Cause: The authentication service in use was not able to return the external name of a user of the ORACLE server because it is not available to the service yet.

Action: This is just an informational message and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support.

TNS-12674: Shared server: proxy context not saved

TNS-12674: Shared server: proxy context not saved

Cause: A connection was marked as being a proxy connection (database link) from a shared server but no inbound context was present.

Action: This error should not normally be visible to the user. Contact Oracle Customer Support.

TNS-12673: Dedicated server: context not saved

TNS-12673: Dedicated server: context not saved

Cause: A connection was marked as being a proxy connection (database link) from a dedicated server but no inbound context was present.

Action: This error should not normally be visible to the user. Contact Oracle Customer Support.

TNS-12672: Database logon failure

TNS-12672: Database logon failure

Cause: The authentication service adapter in use encountered an error it attempted to validate the logon attempt of a user.

Action: Enable tracing to determine the exact error encountered by the adapter.

TNS-12671: Shared server: adapter failed to save context

TNS-12671: Shared server: adapter failed to save context

Cause: The adapter for the authentication service failed when it tried to save the data needed for proxy connections (database links) through the shared server.

Action: Enable tracing to determine the exact error. Contact Oracle Customer Support if the reason is not obvious.

TNS-12670: Incorrect role password

TNS-12670: Incorrect role password

Cause: A password supplied for a role could not be validated by the authentication service.

Action: Supply the correct password.

TNS-12669: Shared server: outbound protocol does not support proxies

TNS-12669: Shared server: outbound protocol does not support proxies

Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a shared server does not support proxy connections.

Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.

TNS-12668: Dedicated server: outbound protocol does not support proxies

TNS-12668: Dedicated server: outbound protocol does not support proxies

Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a dedicated server does not support proxy connections.

Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.

TNS-12667: Shared server: outbound transport protocol different from inbound

TNS-12667: Shared server: outbound transport protocol different from inbound

Cause: The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same as as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the shared server.

Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection

TNS-12666: Dedicated server: outbound transport protocol different from inbound

TNS-12666: Dedicated server: outbound transport protocol different from inbound

Cause: The protocol specified for an externally-identified outbound connection from a dedicated server (database link) was not the same as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the dedicated server.

Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection.

TNS-12665: NLS string open failed

TNS-12665: NLS string open failed

Cause: A native service was unable to make a string available for use by the National Language Support component.

Action: Make sure the National Language Support component has been properly. If it has, enable tracing and report the problem to Customer Support.

TNS-12664: Services required by server not available on the client

TNS-12664: Services required by server not available on the client

Cause: Service(s) that was (were) required by the server process were not available on the client process.

Action: Configure the client with the services required by the server (best solution) or delete the requirement from the configuration file of the server (least secure).

TNS-12663: Services required by client not available on the server

TNS-12663: Services required by client not available on the server

Cause: Service(s) that was (were) required by the client process were not available on the server process.

Action: Configure the server with the services required by the client (best solution) or delete the requirement from the configuration file of the client (least secure).

TNS-12662: proxy ticket retrieval failed

TNS-12662: proxy ticket retrieval failed

Cause: The authentication adapter used by Oracle Net failed to retrieve the credentials needed to authenticate a database link.

Action: Enable tracing to determine the exact error.

TNS-12661: Protocol authentication to be used

TNS-12661: Protocol authentication to be used

Cause: The Oracle Advanced Security authentication service has determined that the Oracle Net transport protocol in use is to be utilized to authenticate a user s identity.

Action: This error is used solely to communicate information between the authentication service and the Oracle Net session layer and should not normally be visible. If the error is seen, contact Oracle Worldwide Support.

TNS-12660: Encryption or crypto-checksumming parameters incompatible

TNS-12660: Encryption or crypto-checksumming parameters incompatible

Cause: One side of the connection specified REQUIRED for encryption or crypto-checksumming, while the other side specified REJECTED .

Action: Change the REQUIRED side to REQUESTED if the you want encryption or crypto-checksumming to be optional, or change the REJECTED side to ACCEPTED if you do not want the service to be optional.

TNS-12659: Error received from other process

TNS-12659: Error received from other process

Cause: An error was received by one or more services from the process on the other side of the connection.

Action: Enable tracing to determine the exact error(s). The error(s) is (are) not returned directly because an error generated by a server may not make sense on the client side and vice-versa.

TNS-12658: ANO service required but TNS version is incompatible

TNS-12658: ANO service required but TNS version is incompatible

Cause: A client process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that an ANO service (authentication, encryption, etc.) be used.

Action: Relink the calling executable and retry the connection or eliminate the requirement that the service be used on the server side.

TNS-12657: No algorithms installed

TNS-12657: No algorithms installed

Cause: The near side of the connection required the use of a service (either encryption or checksumming) when no algorithms for that service were installed.

Action: Remove the ON requirement for that service.

TNS-12656: Cryptographic checksum mismatch

TNS-12656: Cryptographic checksum mismatch

Cause: The cryptographic checksum received with a packet of incoming data didn t match the checksum computed by the receiving end. This indicates that the packet was tampered with or otherwise corrupted in transit.

Action: Look for sources of data corruption, perhaps including deliberate tampering.

TNS-12655: Password check failed

TNS-12655: Password check failed

Cause: The authentication service being used was unable to verify the provided password.

Action: Enable tracing to determine the exact error.

TNS-12654: Authentication conversion failed

TNS-12654: Authentication conversion failed

Cause: The authentication service was unable to convert the credentials of a user from the format specific to the format into the ORACLE format.

Action: Enable tracing to determine the exact error.

TNS-12653: Authentication control function failed

TNS-12653: Authentication control function failed

Cause: The control function utilized by the authentication service driver failed.

Action: Enable tracing to determine the exact error.

TNS-12652: String truncated

TNS-12652: String truncated

Cause: Not enough memory was allocated for a string so it had to be truncated

Action: If it is OK that the string is truncated, then it is not an error. Otherwise, call the routine that reported the error again with a larger string buffer.

TNS-12651: Encryption or data integrity algorithm unacceptable

TNS-12651: Encryption or data integrity algorithm unacceptable

Cause: The algorithm the server chose to use for encryption or data integrity was not one of the choices acceptable to the client. This is either the result of an internal error, of a network data transmission error, or of deliberate tampering with the transmitted data.

Action: For further details, turn on tracing, re-execute the operation, and contact Oracle Customer Support.

TNS-12650: No common encryption or data integrity algorithm

TNS-12650: No common encryption or data integrity algorithm

Cause: The client and server have no algorithm in common for either encryption or data integrity or both.

Action: Choose sets of algorithms that overlap. In other words, add one of the client s algorithm choices to the server s list or vice versa.

TNS-12649: Unknown encryption or data integrity algorithm

TNS-12649: Unknown encryption or data integrity algorithm

Cause: An Oracle Advanced Security list-of-algorithms parameter included an algorithm name that was not recognized.

Action: Either remove that algorithm name, correct it if it was misspelled, or install the driver for the missing algorithm.

TNS-12648: Encryption or data integrity algorithm list empty

TNS-12648: Encryption or data integrity algorithm list empty

Cause: An Oracle Advanced Security list-of-algorithms parameter was empty, e.g. ().

Action: Change the list to contain the name of at least one installed algorithm, or remove the list entirely if every installed algorithm is acceptable.

TNS-12647: Authentication required

TNS-12647: Authentication required

Cause: The parameter that controls whether authentication is required was set to true, but the executable does not have an authentication service linked in.

Action: Either re-link the executable with an authentication service adapter or disable the parameter.

TNS-12646: Invalid value specified for boolean parameter

TNS-12646: Invalid value specified for boolean parameter

Cause: The value specified for a parameter was set to a value other than true or false or on or off.

Action: Correct the value of the parameter.

TNS-12645: Parameter does not exist.

TNS-12645: Parameter does not exist.

Cause: A sqlnet.ora parameter from which a value was needed does not exist.

Action: Set the parameter in the parameter file.

TNS-12643: Client received internal error from server

TNS-12643: Client received internal error from server

Cause: The client process received an error from the server that indicated that an internal Oracle Net native services error had occurred.

Action: Enable tracing on both processes and attempt to recreate the problem. If successful in recreating the problem, contact Oracle Customer Support.

TNS-12642: No session key

TNS-12642: No session key

Cause: A process has no session key associated with it because the authentication service being used does not use one.

Action: If a session key is required, use another authentication service.

TNS-12641: Authentication service failed to initialize

TNS-12641: Authentication service failed to initialize

Cause: The authentication service failed during initialization.

Action: Enable tracing to determine the exact error.

TNS-12640: Authentication adapter initialization failed

TNS-12640: Authentication adapter initialization failed

Cause: The function specified in the authentication table entry for the service failed.

Action: Enable tracing to determine the exact error.

TNS-12639: Authentication service negotiation failed

TNS-12639: Authentication service negotiation failed

Cause: No match was found between the types of authentication services that the client supports and those that the server is using.

Action: Possible solutions: 1. Change the entry in sqlnet.ora that determines which services are to be used. 2. Relink the client with at least one of the authentication service adapters that the server supports. 3. Relink the server with at least one of the authentication service adapters that the client supports. 4. Disable authentication on both the client and server.

TNS-12638: Credential retrieval failed

TNS-12638: Credential retrieval failed

Cause: The authentication service failed to retrieve the credentials of a user.

Action: Enable tracing to determine the exact error.

TNS-12637: Packet receive failed

TNS-12637: Packet receive failed

Cause: A process was unable to receive a packet from another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred.

Action: If the cause is not obvious, contact Oracle Customer Support.

TNS-12636: Packet send failed

TNS-12636: Packet send failed

Cause: A process was unable to send a packet to another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred.

Action: If the cause is not obvious, contact Oracle Customer Support.

TNS-12635: No authentication adapters available

TNS-12635: No authentication adapters available

Cause: The executable was not linked with any authentication service adapters but the sqlnet.ora parameter that determines whether or not authentication is required was set to true.

Action: Either disable the parameter or relink the executable with service adapters.

TNS-12634: Memory allocation failed

TNS-12634: Memory allocation failed

Cause: Process was unable to allocate memory.

Action: Terminate other processes in order to reclaim needed memory.

TNS-12633: No shared authentication services

TNS-12633: No shared authentication services

Cause: The list of authentication services specified by the user does not match those supported by the process.

Action: Either specify another list or relink the executable with the desired services.

TNS-12632: Role fetch failed

TNS-12632: Role fetch failed

Cause: The authentication service failed to retrieve one of the user s roles.

Action: Enable tracing to determine which routine is failing.

TNS-12631: Username retrieval failed

TNS-12631: Username retrieval failed

Cause: The authentication service failed to retrieve the name of a user.

Action: Enable tracing to determine which routine is failing.

TNS-12630: Native service operation not supported

TNS-12630: Native service operation not supported

Cause: An operation requested by a user is not supported by the native services component.

Action: This may be an internal error if the operation should have been supported.

TNS-12629: TNS:no event test

TNS-12629: TNS:no event test

Cause: An attempt to register a connection for event notification failed because the ability to test for events is not available.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

TNS-12628: TNS:no event callbacks

TNS-12628: TNS:no event callbacks

Cause: An attempt to register a connection for event notification failed because asynchronous callbacks are not available.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

TNS-12626: TNS:bad event type

TNS-12626: TNS:bad event type

Cause: An attempt to register a connection for event notification failed because the event type is unknown.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

TNS-12625: TNS:missing argument

TNS-12625: TNS:missing argument

Cause: An operation failed because an argument was missing

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

TNS-12624: TNS:connection is already registered

TNS-12624: TNS:connection is already registered

Cause: An attempt to register a connection for event notification failed because the connection is already registered.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

TNS-12623: TNS:operation is illegal in this state

TNS-12623: TNS:operation is illegal in this state

Cause: Connection is half-duplex and a full-duplex operation was attempted.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12622: TNS:event notifications are not homogeneous

TNS-12622: TNS:event notifications are not homogeneous

Cause: An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

TNS-12620: TNS:requested characteristic not available

TNS-12620: TNS:requested characteristic not available

Cause: The connect request failed because a requested transport characteristic could not be supported by the remote TNS software.

Action: If appropriate, reexecute with reduced requirements.

TNS-12619: TNS:unable to grant requested service

TNS-12619: TNS:unable to grant requested service

Cause: The connect request failed because requested service could not be provided by the local TNS software.

Action: If appropriate, reexecute with reduced service requirements.

TNS-12618: TNS:versions are incompatible

TNS-12618: TNS:versions are incompatible

Cause: The two machines are running incompatible versions of TNS.

Action: Check the version numbers, and upgrade the machine with the smaller one.

TNS-12616: TNS:no event signals

TNS-12616: TNS:no event signals

Cause: The operation failed because the type of data specified is unknown.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12615: TNS:preempt error

TNS-12615: TNS:preempt error

Cause: A request to service an event failed because no event notification has yet been posted.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12612: TNS:connection is busy

TNS-12612: TNS:connection is busy

Cause: Attempted operation failed because it conflicts with an ongoing

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12611: TNS:operation is not portable

TNS-12611: TNS:operation is not portable

Cause: Attempted operation is not portable.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12609: TNS: Receive timeout occurred

TNS-12609: TNS: Receive timeout occurred

Cause: The receive or read operation did not complete within the allowed time interval.

Action: Check if the peer host is available. Increase the receive timeout value if necessary.

TNS-12608: TNS: Send timeout occurred

TNS-12608: TNS: Send timeout occurred

Cause: The send or write operation did not complete within the allowed time interval.

Action: Check if the peer host is available. Increase the send timeout value if necessary.

TNS-12607: TNS: Connect timeout occurred

TNS-12607: TNS: Connect timeout occurred

Cause: A network session did not reach a predefined connect stage within the allowed time interval.

Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description.

TNS-12606: TNS: Application timeout occurred

TNS-12606: TNS: Application timeout occurred

Cause: A network session did not reach an application-defined stage within the allowed time interval.

Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description.

TNS-12602: TNS: Connection Pooling limit reached

TNS-12602: TNS: Connection Pooling limit reached

Cause: The operation failed because maximum active current connections has been reached. It may not be a real error when the Connection Pooling feature is enabled. It is possible that the application later reissues the operation and successfully grabs the connection pool slot and proceeds.

Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.

TNS-12601: TNS:information flags check failed

TNS-12601: TNS:information flags check failed

Cause: The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished.

Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.

TNS-12600: TNS: string open failed

TNS-12600: TNS: string open failed

Cause: The creation of a string in ORACLE NLS format failed.

Action: This is an internal error, enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.

TNS-12599: TNS:cryptographic checksum mismatch

TNS-12599: TNS:cryptographic checksum mismatch

Cause: The data received is not the same as the data sent.

Action: Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection.

TNS-12598: TNS:banner registration failed

TNS-12598: TNS:banner registration failed

Cause: The registration of a product banner with the Oracle server failed.

Action: This is an error which is not normally visible externally. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.

TNS-12597: TNS:connect descriptor already in use

TNS-12597: TNS:connect descriptor already in use

Cause: Internal error - illegal use of connect descriptor.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12596: TNS:internal inconsistency

TNS-12596: TNS:internal inconsistency

Cause: TNS has detected an internal inconsistency.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

TNS-12595: TNS:no confirmation

TNS-12595: TNS:no confirmation

Cause: TNS is unable to get requested confirmation acknowledgment from remote partner.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12593: TNS:no registered connection

TNS-12593: TNS:no registered connection

Cause: An attempt to solicit network event activity has failed because no connections are registered for event notification.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12592: TNS:bad packet

TNS-12592: TNS:bad packet

Cause: An ill-formed packet has been detected by the TNS software.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12591: TNS:event signal failure

TNS-12591: TNS:event signal failure

Cause: The TNS software is unable to signal an event occurrence.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12590: TNS:no I or O buffer

TNS-12590: TNS:no I or O buffer

Cause: An attempt to perform an I or O operation failed because no buffer was available.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12589: TNS:connection not bequeathable

TNS-12589: TNS:connection not bequeathable

Cause: An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12585: TNS:data truncation

TNS-12585: TNS:data truncation

Cause: A receive operation has completed with insufficient data to satisfy the user s request.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12583: TNS:no reader

TNS-12583: TNS:no reader

Cause: A send operation has been requested but partner has already disconnected.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12582: TNS:invalid operation

TNS-12582: TNS:invalid operation

Cause: An internal function received an invalid request.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12574: TNS:redirection denied

TNS-12574: TNS:redirection denied

Cause: The connect request failed because it would have required redirection and the caller has requested no redirections.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12571: TNS:packet writer failure

TNS-12571: TNS:packet writer failure

Cause: An error occurred during a data send.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12570: TNS:packet reader failure

TNS-12570: TNS:packet reader failure

Cause: An error occurred during a data receive.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12569: TNS:packet checksum failure

TNS-12569: TNS:packet checksum failure

Cause: The data received is not the same as the data sent.

Action: Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation.

TNS-12566: TNS:protocol error

TNS-12566: TNS:protocol error

Cause: An unexpected TNS protocol error has occurred.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12564: TNS:connection refused

TNS-12564: TNS:connection refused

Cause: The connect request was denied by the remote user (or TNS software).

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation.

TNS-12562: TNS:bad global handle

TNS-12562: TNS:bad global handle

Cause: Internal error - bad gbh argument passed to TNS from caller. System may have been linked with old libraries.

Action: Not normally visible to the user, contact Oracle Customer Support.

TNS-12561: TNS:unknown error

TNS-12561: TNS:unknown error

Cause: A generic protocol error occurred.

Action: For further details, turn on tracing and reexecute the operation.

TNS-12560: TNS:protocol adapter error

TNS-12560: TNS:protocol adapter error

Cause: A generic protocol adapter error occurred.

Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete.

TNS-12556: TNS:no caller

TNS-12556: TNS:no caller

Cause: TNS detected an incoming connect request but there was no caller.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12555: TNS:permission denied

TNS-12555: TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.

TNS-12554: TNS:current operation is still in progress

TNS-12554: TNS:current operation is still in progress

Cause: An internal operation is still in progress.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12552: TNS:operation was interrupted

TNS-12552: TNS:operation was interrupted

Cause: An internal operation was interrupted and could not complete.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12551: TNS:missing keyword

TNS-12551: TNS:missing keyword

Cause: The supplied connect descriptor is missing one or more TNS keywords.

Action: Check the syntax, and ensure all required keywords are present.

TNS-12550: TNS:syntax error

TNS-12550: TNS:syntax error

Cause: The supplied connect descriptor contains illegal syntax.

Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.

TNS-12549: TNS:operating system resource quota exceeded

TNS-12549: TNS:operating system resource quota exceeded

Cause: The current user has exceeded the allotted resource assigned in the operating system.

Action: Acquire more operating system resource, or perform a different function.

TNS-12548: TNS:incomplete read or write

TNS-12548: TNS:incomplete read or write

Cause: A data send or receive failed.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12547: TNS:lost contact

TNS-12547: TNS:lost contact

Cause: Partner has unexpectedly gone away, usually during process startup.

Action: Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded.

TNS-12546: TNS:permission denied

TNS-12546: TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.

TNS-12545: Connect failed because target host or object does not exist

TNS-12545: Connect failed because target host or object does not exist

Cause: The address specified is not valid, or the program being connected to does not exist.

Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps oracle is missing.) If the protocol is TCP or IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.

TNS-12544: TNS:contexts have different wait or test functions

TNS-12544: TNS:contexts have different wait or test functions

Cause: Two protocol adapters have conflicting wait or test functions.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12543: TNS:destination host unreachable

TNS-12543: TNS:destination host unreachable

Cause: Contact can not be made with remote party.

Action: Make sure the network driver is functioning and the network is up.

TNS-12542: TNS:address already in use

TNS-12542: TNS:address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with a unique address.

TNS-12541: TNS:no listener

TNS-12541: TNS:no listener

Cause: The connection request could not be completed because the listener is not running.

Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.

TNS-12540: TNS:internal limit restriction exceeded

TNS-12540: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

Action: Wait for connections to close and re-try.

TNS-12539: TNS:buffer over- or under-flow

TNS-12539: TNS:buffer over- or under-flow

Cause: Buffer too small for incoming data or too large for outgoing data.

Action: This restriction (which is associated with CONNECT DATA) is not normally visible to the user. For further details, turn on tracing and reexecute the operation; contact Oracle Customer Support.

TNS-12538: TNS:no such protocol adapter

TNS-12538: TNS:no such protocol adapter

Cause: The protocol adapter requested (by way of the (PROTOCOL=..) keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adapter is not installed.

Action: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA).

TNS-12537: TNS:connection closed

TNS-12537: TNS:connection closed

Cause: End of file condition has been reached; partner has disconnected.

Action: None needed; this is an information message.

TNS-12536: TNS:operation would block

TNS-12536: TNS:operation would block

Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking.

Action: None needed; this is an information message.

TNS-12535: TNS:operation timed out

TNS-12535: TNS:operation timed out

Cause: The requested operation could not be completed within the time out period.

Action: Look at the documentation on the secondary errors for possible remedy. See SQLNET.LOG to find secondary error if not provided explicitly. Turn on tracing to gather more information.

TNS-12534: TNS:operation not supported

TNS-12534: TNS:operation not supported

Cause: An internal function received a request to perform an operation that is not supported (on this machine).

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12533: TNS:illegal ADDRESS parameters

TNS-12533: TNS:illegal ADDRESS parameters

Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport.

Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.

TNS-12532: TNS:invalid argument

TNS-12532: TNS:invalid argument

Cause: An internal function received an invalid parameter.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

TNS-12531: TNS:cannot allocate memory

TNS-12531: TNS:cannot allocate memory

Cause: Sufficient memory could not be allocated to perform the desired activity.

Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation.

TNS-12529: TNS:connect request rejected based on current filtering rules

TNS-12529: TNS:connect request rejected based on current filtering rules

Cause: Connection Manager and its listener were configured with filtering rules specifying that the connect request be rejected.

Action: If this connect request should be allowed, then contact the administrator to modify the filtering rules.

TNS-12528: TNS:listener: all appropriate instances are blocking new connections

TNS-12528: TNS:listener: all appropriate instances are blocking new connections

Cause: All instances supporting the service requested by the client reported that they were blocking the new connections. This condition may be temporary, such as at instance startup.

Action: Attempt the connection again. If error persists, then contact the administrator to check the status of the instances.

TNS-12527: TNS:listener: all instances are in restricted mode or blocking new connections

TNS-12527: TNS:listener: all instances are in restricted mode or blocking new connections

Cause: All appropriate database instances supporting the service requested by the client reported that they either were in restricted mode or were blocking the new connections. The Listener does not allow connections to such instances. This condition may be temporary, such as at instance startup.

Action: Attempt the connection again. If error persists, then contact the database administrator to check the status of the instances.

TNS-12526: TNS:listener: all appropriate instances are in restricted mode

TNS-12526: TNS:listener: all appropriate instances are in restricted mode

Cause: Database instances supporting the service requested by the client were in restricted mode. The Listener does not allow connections to instances in restricted mode. This condition may be temporary, such as during periods when database administration is performed.

Action: Attempt the connection again. If error persists, then contact the database administrator to change the mode of the instance, if appropriate.

TNS-12525: TNS:listener has not received client s request in time allowed

TNS-12525: TNS:listener has not received client s request in time allowed

Cause: The listener disconnected the client because the client failed to provide the necessary connect information within the allowed time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the listener.

Action: If the error occurred because of a slow network or system, reconfigure INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious client is suspected, use the address in listener.log to identify the source and restrict access. Turn on tracing for more information.

TNS-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

TNS-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener s tables for the specified SERVICE_NAME and INSTANCE_NAME.

Action: Check to make sure that the HANDLER_NAME specified is correct.

TNS-12523: TNS:listener could not find instance appropriate for the client connection

TNS-12523: TNS:listener could not find instance appropriate for the client connection

Cause: The listener could not find any available (database) instances, that are appropriate for the client connection.

Action: Run lsnrctl services to ensure that the instance(s) are registered with the listener, and have status READY.

TNS-12522: TNS:listener could not find available instance with given INSTANCE_ ROLE

TNS-12522: TNS:listener could not find available instance with given INSTANCE_ ROLE

Cause: There are not any available and appropriate database instances registered with the listener, that are part of the service identified by SERVICE_NAME given in the connect descriptor and that have the specified INSTANCE_ROLE (and INSTANCE_NAME, if specified).

Action: Check to make sure that the INSTANCE_ROLE specified is correct. Run lsnrctl services to ensure that the instance(s) have registered with the listener and that they are ready to accept connections.

TNS-12521: TNS:listener does not currently know of instance requested in connect descriptor

TNS-12521: TNS:listener does not currently know of instance requested in connect descriptor

Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified in addition to the service name an instance name for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action: services lamp;lt;lamp;nbsp;listener namelamp;gt; an instance name known by the listener.

TNS-12520: TNS:listener could not find available handler for requested type of server

TNS-12520: TNS:listener could not find available handler for requested type of server

Cause: None of the known and available service handlers for requested type of server (dedicated or shared) are appropriate for the client connection.

Action: Run lsnrctl services to ensure that the instance(s) have registered with the listener and that the appropriate handlers are accepting connections.

TNS-12519: TNS:no appropriate service handler found

TNS-12519: TNS:no appropriate service handler found

Cause: The listener could not find any available service handlers that are appropriate for the client connection.

Action: Run lsnrctl services to ensure that the instance(s) have registered with the listener, and are accepting connections.

TNS-12518: TNS:listener could not hand off client connection

TNS-12518: TNS:listener could not hand off client connection

Cause: The process of handing off a client connection to another process failed.

Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If problem persists, call Oracle Support.

TNS-12516: TNS:listener could not find available handler with matching protocol stack

TNS-12516: TNS:listener could not find available handler with matching protocol stack

Cause: None of the known and available service handlers for the given SERVICE_ NAME support the client s protocol stack: transport, session, and presentation protocols.

Action: Check to make sure that the service handlers (e.g. dispatchers) for the given SERVICE_NAME are registered with the listener, are accepting connections, and that they are properly configured to support the desired protocols.

TNS-12515: TNS:listener could not find a handler for this presentation

TNS-12515: TNS:listener could not find a handler for this presentation

Cause: None of the listener s known service handlers are registered as supporting the presentation protocol required by the connecting client.

Action: Check that the destination service is configured to accept the presentation protocol.

TNS-12514: TNS:listener does not currently know of service requested in connect descriptor

TNS-12514: TNS:listener does not currently know of service requested in connect descriptor

Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action: services lamp;lt;lamp;nbsp;listener namelamp;gt; service name used specifies a service known by the listener. name specified is a service known by the listener.

TNS-12513: TNS:service handler found but it has registered for a different protocol

TNS-12513: TNS:service handler found but it has registered for a different protocol

Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client.

Action: Contact the DBA to register a dispatcher on your protocol.

TNS-12511: TNS:service handler found but it is not accepting connections

TNS-12511: TNS:service handler found but it is not accepting connections

Cause: The dispatchers notified the listener that they temporarily do not accept new connections.

Action: Attempt the connection again. If error persists, contact the DBA to check the state of the dispatchers and or or ask him to increase the number of dispatchers.

TNS-12510: TNS:database temporarily lacks resources to handle the request

TNS-12510: TNS:database temporarily lacks resources to handle the request

Cause: The dispatchers appear to be busy handling other requests.

Action: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers and or or dispatchers limit on number of connections or sessions that they can accept.

TNS-12509: TNS:listener failed to redirect client to service handler

TNS-12509: TNS:listener failed to redirect client to service handler

Cause: The dispatcher terminated unexpectedly

Action: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect.

TNS-12508: TNS:listener could not resolve the COMMAND given

TNS-12508: TNS:listener could not resolve the COMMAND given

Cause: d by incompatible Oracle Net or Net8 versions. Do not include in error manual.

Action: This is not seen in normal use of Oracle Net.

TNS-12505: TNS:listener does not currently know of SID given in connect descriptor

TNS-12505: TNS:listener does not currently know of SID given in connect descriptor

Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action: services lamp;lt;lamp;nbsp;listener namelamp;gt; known by the listener.