Oracle 12c R2 Error Codes and Solution Suggestions from ORA-12700 to ORA-12800
- ORA-12700: invalid NLS parameter value (string)
Cause: An invalid or unknown NLS configuration parameter was specified.
Action: n/a
Cause: The character set specified when creating the database is unknown.
Action: n/a
Cause: An unknown parameter name or invalid value is specified in a NLS parameter string.
Action: n/a
Cause: The requested conversion between two character sets in the CONVERT function is not implemented
Action: n/a
Cause: One of the following: – The string operands(other than an nlsparams argument) to an operator or built-in function do not have the same character set. – An nlsparams operand is not in the database character set. – String data with character set other than the database character set is passed to a built-in function not expecting it. – The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS. – A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted. – A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column. – An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.
Action: n/a
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/values in the environment variables.
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: n/a
Cause: Internal error
Action: n/a
Cause: Internal error
Action: n/a
Cause: Internal error
Action: n/a
Cause: The character set specified when creating the control file is unknown.
Action: n/a
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: n/a
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.
Cause: When character set conversion happened between CHAR and NCHAR either implicitly or explicitly, some characters were lost due to no mapping characters in the destination character set.
Action: Ensure that all the characters can be mapped to characters in the destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE.
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
Cause: The character set specified is not allowed for this operation or is invalid
Action: Ensure that the specified character set is valid
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/export
- 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/export.
Cause: This command can only be run when connecting as SYS
Action: Connect as SYS to run this command
Cause: This command can only be run when the database is in RESTRICTED mode
Action: Ensure that the system is in RESTRICTED mode
Cause: This command can only be run when the database is in EXCLUSIVE mode
Action: Ensure that the system is in EXCLUSIVE mode
Cause: This command can only be run when there are no other sessions active
Action: Ensure there are no other connections to the database
Cause: A regular expression internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The regular expression was too complex and could not be parsed.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The regular expression contained an incorrect sequence of metacharacters.
Action: Ensure the metacharacters are correctly positioned.
Cause: The regular expression did not have balanced parentheses.
Action: Ensure the parentheses are correctly balanced.
Cause: The regular expression did not have balanced brackets.
Action: Ensure the brackets are correctly balanced.
Cause: A back references was found before a sub-expression.
Action: Ensure a valid sub-expression is being referenced.
Cause: An invalid range was found in the regular expression.
Action: Ensure a valid range is being used.
Cause: An unknown character class was found in the regular expression.
Action: Ensure a valid characters class is being used.
Cause: An unknown equivalence class was found in the regular expression.
Action: Ensure a valid equivalence class is being used.
Cause: An unknown collation class was found in the regular expression.
Action: Ensure a valid collation class is being used.
Cause: An invalid interval value was found in the regular expression.
Action: Ensure a valid interval value is being used.
Cause: The operation failed because the regular expression it used exceeds the maximum supported size.
Action: Use a shorter regular expression.
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
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
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
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
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets.
Action: Do not use Express Instant Client for this character set
Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets.
Action: Do not use Express Instant Client for this character set
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets.
Action: Do not use Express Instant Client for this character set
Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets.
Action: Do not use Express Instant Light for this character set
Cause: The character argument of a collation-sensitive operator was too long or it had too many decomposable characters to create a collation key for it in the available buffer space.
Action: Shorten the argument value or, if using a UCA-based collation, increase the ratio of characters with short or no Unicode decomposition to characters with long Unicode decomposition in the value.
Cause: This is an internal error in a globalization support function.
Action: Contact Oracle Support Services.
Cause: An attempt was made to create or alter a database using a client-only or conversion-only character set.
Action: Specify a supported database character set.
Cause: The name of the collation that you specified was not recognized by the Oracle Database, because the name was misspelled, or the collation was user-defined but not installed in the Oracle Home of the database instance, or because the directory specified in the ORA_NLS10 environment setting, either explicitly or defaulting to $ORACLE_HOME/nls/data (%ORACLE_HOME%\nls\data on Microsoft Windows), did not contain valid NLS data files.
Action: Specify a valid collation name or fix your database software configuration.
Cause: The ID of the collation that you specified was not recognized by the Oracle Database, because it was incorrect, or the collation was user-defined but not installed in the Oracle Home of the database instance, or because the directory specified in the ORA_NLS10 environment setting, either explicitly or defaulting to $ORACLE_HOME/nls/data(%ORACLE_HOME%\nls\data on Microsoft Windows), did not contain valid NLS data files.
Action: Specify a valid collation ID or fix your database software configuration.
Cause: An unexpected error was encountered by an instance-critical process.
Action: Contact Oracle Support Services.
- ORA-12753: The Oracle home user ID does not match the effective user ID of the local client which connected to the Oracle instance.
Cause: The user ID that is the owner of the Oracle home directory was not the same as the effective user ID of the local client that connected to the Oracle instance.
Action: Run the local client that connects to Oracle instance with the same user ID as the owner of the Oracle home.
Cause: load on system is too high to perform parallel queries.
Action: re-execute serially or wait until system load is reduced.