ORA-12737: Instant Client Light: unsupported server character set string

ORA-12737: Instant Client Light: unsupported server character set string

Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets.

Action: Do not use Instant Client Light for this character set

ORA-12736: Instant Client Light: unsupported server national character set string

ORA-12736: Instant Client Light: unsupported server national character set string

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets.

Action: Do not use Instant Client Light for this character set

ORA-12735: Instant Client Light: unsupported client character set string

ORA-12735: Instant Client Light: unsupported client character set string

Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets.

Action: Do not use Instant Client Light for this character set

ORA-12734: Instant Client Light: unsupported client national character set string

ORA-12734: Instant Client Light: unsupported client national character set string

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets.

Action: Do not use Instant Client Light for this character set

ORA-12733: regular expression too long

ORA-12733: regular expression too long

Cause: The operation failed because the regular expression it used exceeds the maximum supported size.

Action: Use a shorter regular expression.

ORA-12732: invalid interval value in regular expression

ORA-12732: invalid interval value in regular expression

Cause: An invalid interval value was found in the regular expression.

Action: Ensure a valid interval value is being used.

ORA-12731: invalid collation class in regular expression

ORA-12731: invalid collation class in regular expression

Cause: An unknown collation class was found in the regular expression.

Action: Ensure a valid collation class is being used.

ORA-12730: invalid equivalence class in regular expression

ORA-12730: invalid equivalence class in regular expression

Cause: An unknown equivalence class was found in the regular expression.

Action: Ensure a valid equivalence class is being used.

ORA-12729: invalid character class in regular expression

ORA-12729: invalid character class in regular expression

Cause: An unknown character class was found in the regular expression.

Action: Ensure a valid characters class is being used.

ORA-12728: invalid range in regular expression

ORA-12728: invalid range in regular expression

Cause: An invalid range was found in the regular expression.

Action: Ensure a valid range is being used.

ORA-12727: invalid back reference in regular expression

ORA-12727: invalid back reference in regular expression

Cause: A back references was found before a sub-expression.

Action: Ensure a valid sub-expression is being referenced.

ORA-12726: unmatched bracket in regular expression

ORA-12726: unmatched bracket in regular expression

Cause: The regular expression did not have balanced brackets.

Action: Ensure the brackets are correctly balanced.

ORA-12725: unmatched parentheses in regular expression

ORA-12725: unmatched parentheses in regular expression

Cause: The regular expression did not have balanced parentheses.

Action: Ensure the parentheses are correctly balanced.

ORA-12724: regular expression corrupt

ORA-12724: regular expression corrupt

Cause: The regular expression contained an incorrect sequence of metacharacters.

Action: Ensure the metacharacters are correctly positioned.

ORA-12723: regular expression too complex

ORA-12723: regular expression too complex

Cause: The regular expression was too complex and could not be parsed.

Action: This is an internal error. Contact Oracle Support Services.

ORA-12722: regular expression internal error

ORA-12722: regular expression internal error

Cause: A regular expression internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.

ORA-12721: operation cannot execute when other sessions are active

ORA-12721: operation cannot execute when other sessions are active

Cause: This command can only be run when there are no other sessions active

Action: Ensure there are no other connections to the database

ORA-12720: operation requires database is in EXCLUSIVE mode

ORA-12720: operation requires database is in EXCLUSIVE mode

Cause: This command can only be run when the database is in EXCLUSIVE mode

Action: Ensure that the system is in EXCLUSIVE mode

ORA-12719: operation requires database is in RESTRICTED mode

ORA-12719: operation requires database is in RESTRICTED mode

Cause: This command can only be run when the database is in RESTRICTED mode

Action: Ensure that the system is in RESTRICTED mode

ORA-12718: operation requires connection as SYS

ORA-12718: operation requires connection as SYS

Cause: This command can only be run when connecting as SYS

Action: Connect as SYS to run this command

ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists

ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists

Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode when converting to a multibyte character set and must be migrated.

Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file. The above type data can be migrated by methods such as import or export.

ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists

ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists

Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated

Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as import or export

ORA-12715: invalid character set specified

ORA-12715: invalid character set specified

Cause: The character set specified is not allowed for this operation or is invalid

Action: Ensure that the specified character set is valid

ORA-12714: invalid national character set specified

ORA-12714: invalid national character set specified

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set

Action: Ensure that the specified national character set is valid

ORA-12713: Character data loss in NCHAR or CHAR conversion

ORA-12713: Character data loss in NCHAR or CHAR conversion

Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.

Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE.

ORA-12712: new character set must be a superset of old character set

ORA-12712: new character set must be a superset of old character set

Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC.

Action: Specify a superset character set.

ORA-12711: this CREATE CONTROLFILE character set is not allowed

ORA-12711: this CREATE CONTROLFILE character set is not allowed

Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.

Action: none

ORA-12710: CREATE CONTROLFILE character set is not known

ORA-12710: CREATE CONTROLFILE character set is not known

Cause: The character set specified when creating the control file is unknown.

Action: none

ORA-12709: error while loading create database character set

ORA-12709: error while loading create database character set

Cause: Internal error

Action: none

ORA-12708: error while loading create database NLS parameter string

ORA-12708: error while loading create database NLS parameter string

Cause: Internal error

Action: none

ORA-12707: error while getting create database NLS parameter string

ORA-12707: error while getting create database NLS parameter string

Cause: Internal error

Action: none

ORA-12706: this CREATE DATABASE character set is not allowed

ORA-12706: this CREATE DATABASE character set is not allowed

Cause: It is not allowed to create a database on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.

Action: none

ORA-12705: Cannot access NLS data files or invalid environment specified

ORA-12705: Cannot access NLS data files or invalid environment specified

Cause: Either an attempt was made to issue an ALTER SESSION command with an invalid NLS parameter or value; or the environment variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data files cannot be located.

Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify the correct directory path or values in the environment variables.

ORA-12704: character set mismatch

ORA-12704: character set mismatch

Cause: One of the following: built-in function do not have the same character set. built-in function not expecting it. CS. clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted. same character set as declared for the column. requirements of the corresponding parameter.

Action: none

ORA-12703: this character set conversion is not supported

ORA-12703: this character set conversion is not supported

Cause: The requested conversion between two character sets in the CONVERT function is not implemented

Action: none

ORA-12702: invalid NLS parameter string used in SQL function

ORA-12702: invalid NLS parameter string used in SQL function

Cause: An unknown parameter name or invalid value is specified in a NLS parameter string.

Action: none

ORA-12701: CREATE DATABASE character set is not known

ORA-12701: CREATE DATABASE character set is not known

Cause: The character set specified when creating the database is unknown.

Action: none

ORA-12700: invalid NLS parameter value (string)

ORA-12700: invalid NLS parameter value (string)

Cause: An invalid or unknown NLS configuration parameter was specified.

Action: none

ORA-12699: Native service internal error

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

ORA-12696: Double Encryption Turned On, login disallowed

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

ORA-12690: Server Authentication failed, login cancelled

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

ORA-12689: Server Authentication required, but not supported

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

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

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

ORA-12687: Credentials expired.

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

ORA-12686: Invalid command specified for a service

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

ORA-12685: Native service required remotely but disabled locally

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

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

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

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

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

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

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

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

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

ORA-12680: Native services disabled but required

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

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

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

ORA-12678: Authentication disabled but required

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

ORA-12677: Authentication service not supported by database link

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

ORA-12676: Server received internal error from client

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

ORA-12675: External user name not available yet

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

ORA-12674: Shared server: proxy context not saved

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

ORA-12673: Dedicated server: context not saved

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

ORA-12672: Database logon failure

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

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

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