ORA-12700 to ORA-19399
ORA-12700 invalid NLS parameter value (string)
Cause: An invalid NLS initialization parameter was specified.
Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
ORA-12701 CREATE DATABASE character set is not known
Cause: The character set specified in the CREATE DATABASE command does not exist on the system.
Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.
ORA-12702 invalid NLS parameter string used in SQL function
Cause: An invalid parameter or value was entered in the NLS parameter string in a SQL function.
Action: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.
ORA-12703 this character set conversion is not supported
Cause: An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.
Action: Use character sets available on the system in the CONVERT function.
ORA-12704 character set mismatch
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: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.
ORA-12705 invalid or unknown NLS parameter value specified
Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.
Action: Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION statement, see the Oracle9i SQL Reference.
ORA-12706 this CREATE DATABASE character set is not allowed
Cause: An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.
Action: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.
ORA-12707 error while getting create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12708 error while loading create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12709 error while loading create database character set
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12710 CREATE CONTROLFILE character set is not known
Cause: The character set specified when creating the control file is unknown.
Action: Specify a known character set.
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: Create the correct control file for machine and 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-12713 Character data loss in NCHAR/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 false.
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-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-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 export/import.
ORA-12717 Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists
Cause: NCLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.
Action: Remove NCLOB data as listed in the alert file. NCLOB data can be migrated by methods such as export/import.
ORA-12718 operation requires connection as SYS
Cause: This command can only be run when connecting as user SYS.
Action: Connect as user SYS to run this command.
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-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-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-12800 system appears too busy for parallel query execution
Cause: Load on the system is too high to perform parallel queries.
Action: Re-execute serially or wait until the system load is reduced.
ORA-12801 error signaled in parallel query server string
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause.
ORA-12802 parallel query server lost contact with coordinator
Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12803 parallel query server lost contact with another server
Cause: A parallel query server lost contact with another server.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12804 parallel query server appears to have died
Cause: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12805 parallel query server died unexpectedly
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services. See trace file for more details.
ORA-12806 could not get background process to hold enqueue
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12807 process queue could not receive parallel query message
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12808 cannot set string_INSTANCES greater than number of instances string
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement to a value larger than the number of available instances.
Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809 cannot set string_INSTANCES when mounted in exclusive mode
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement while the database was mounted in exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle9i Real Application Clusters mounted in CLUSTER_DATABASE mode.
ORA-12810 PARALLEL_MAX_SERVERS must be less than or equal to string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.
ORA-12811 PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
ORA-12812 only one PARALLEL or NOPARALLEL clause may be specified
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.
ORA-12813 value for PARALLEL or DEGREE must be greater than 0
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
ORA-12814 only one CACHE or NOCACHE clause may be specified
Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.
ORA-12815 value for INSTANCES must be greater than 0
Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
ORA-12816 parallel create index fastpath operation
Cause: The parallel create index fastpath operation event has been set.
Action: Set this event only under the supervision Oracle development.
ORA-12817 parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not been enabled.
Action: Enable the parallel query option.
ORA-12818 invalid option in PARALLEL clause
Cause: An unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12819 missing options in PARALLEL clause
Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12820 invalid value for DEGREE
Cause: Invalid value for DEGREE was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.
ORA-12821 invalid value for INSTANCES
Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.
ORA-12822 duplicate option in PARALLEL clause
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action: Specify each desired PARALLEL clause option only once.
ORA-12823 default degree of parallelism may not be specified here
Cause: The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER statement.
Action: Respecify with an explicit degree of parallelism.
ORA-12824 INSTANCES DEFAULT may not be specified here
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
ORA-12825 explicit degree of parallelism must be specified here
Cause: The DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit degree of parallelism.
ORA-12700 invalid NLS parameter value (string)
Cause: An invalid NLS initialization parameter was specified.
Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
ORA-12701 CREATE DATABASE character set is not known
Cause: The character set specified in the CREATE DATABASE command does not exist on the system.
Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.
ORA-12702 invalid NLS parameter string used in SQL function
Cause: An invalid parameter or value was entered in the NLS parameter string in a SQL function.
Action: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.
ORA-12703 this character set conversion is not supported
Cause: An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.
Action: Use character sets available on the system in the CONVERT function.
ORA-12704 character set mismatch
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: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.
ORA-12705 invalid or unknown NLS parameter value specified
Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.
Action: Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION statement, see the Oracle9i SQL Reference.
ORA-12706 this CREATE DATABASE character set is not allowed
Cause: An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.
Action: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.
ORA-12707 error while getting create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12708 error while loading create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12709 error while loading create database character set
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12710 CREATE CONTROLFILE character set is not known
Cause: The character set specified when creating the control file is unknown.
Action: Specify a known character set.
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: Create the correct control file for machine and 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-12713 Character data loss in NCHAR/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 false.
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-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-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 export/import.
ORA-12717 Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists
Cause: NCLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.
Action: Remove NCLOB data as listed in the alert file. NCLOB data can be migrated by methods such as export/import.
ORA-12718 operation requires connection as SYS
Cause: This command can only be run when connecting as user SYS.
Action: Connect as user SYS to run this command.
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-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-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-12800 system appears too busy for parallel query execution
Cause: Load on the system is too high to perform parallel queries.
Action: Re-execute serially or wait until the system load is reduced.
ORA-12801 error signaled in parallel query server string
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause.
ORA-12802 parallel query server lost contact with coordinator
Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12803 parallel query server lost contact with another server
Cause: A parallel query server lost contact with another server.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12804 parallel query server appears to have died
Cause: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12805 parallel query server died unexpectedly
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services. See trace file for more details.
ORA-12806 could not get background process to hold enqueue
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12807 process queue could not receive parallel query message
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12808 cannot set string_INSTANCES greater than number of instances string
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement to a value larger than the number of available instances.
Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809 cannot set string_INSTANCES when mounted in exclusive mode
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement while the database was mounted in exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle9i Real Application Clusters mounted in CLUSTER_DATABASE mode.
ORA-12810 PARALLEL_MAX_SERVERS must be less than or equal to string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.
ORA-12811 PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
ORA-12812 only one PARALLEL or NOPARALLEL clause may be specified
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.
ORA-12813 value for PARALLEL or DEGREE must be greater than 0
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
ORA-12814 only one CACHE or NOCACHE clause may be specified
Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.
ORA-12815 value for INSTANCES must be greater than 0
Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
ORA-12816 parallel create index fastpath operation
Cause: The parallel create index fastpath operation event has been set.
Action: Set this event only under the supervision Oracle development.
ORA-12817 parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not been enabled.
Action: Enable the parallel query option.
ORA-12818 invalid option in PARALLEL clause
Cause: An unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12819 missing options in PARALLEL clause
Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12820 invalid value for DEGREE
Cause: Invalid value for DEGREE was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.
ORA-12821 invalid value for INSTANCES
Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.
ORA-12822 duplicate option in PARALLEL clause
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action: Specify each desired PARALLEL clause option only once.
ORA-12823 default degree of parallelism may not be specified here
Cause: The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER statement.
Action: Respecify with an explicit degree of parallelism.
ORA-12824 INSTANCES DEFAULT may not be specified here
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
ORA-12825 explicit degree of parallelism must be specified here
Cause: The DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit degree of parallelism.
No comments:
Post a Comment