ORA-01912: ROW keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
Thursday 19 January 2012
ORA-01911: CONTENTS keyword expected
ORA-01911: CONTENTS keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01910: TABLES keyword expected
ORA-01910: TABLES keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01909: REUSE keyword expected
ORA-01909: REUSE keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01908: EXISTS keyword expected
ORA-01908: EXISTS keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01907: TABLESPACE keyword expected
ORA-01907: TABLESPACE keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01906: BACKUP keyword expected
ORA-01906: BACKUP keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01905: STORAGE keyword expected
ORA-01905: STORAGE keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01904: DATAFILE keyword expected
ORA-01904: DATAFILE keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01903: EVENTS keyword expected
ORA-01903: EVENTS keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01902: SEGMENT keyword expected
ORA-01902: SEGMENT keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01901: ROLLBACK keyword expected
ORA-01901: ROLLBACK keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01900: LOGFILE keyword expected
ORA-01900: LOGFILE keyword expected
Cause: keyword missing
Action: supply missing keyword
Cause: keyword missing
Action: supply missing keyword
ORA-01898: too many precision specifiers
ORA-01898: too many precision specifiers
Cause: While trying to truncate or round dates, extra data was found in the date format picture
Action: Check the syntax of the date format picture and retry.
Cause: While trying to truncate or round dates, extra data was found in the date format picture
Action: Check the syntax of the date format picture and retry.
ORA-01891: Datetime or Interval internal error
ORA-01891: Datetime or Interval internal error
Cause: Internal error.
Action: Please contact Oracle Worldwide Support.
Cause: Internal error.
Action: Please contact Oracle Worldwide Support.
ORA-01890: NLS error detected
ORA-01890: NLS error detected
Cause: An NLS error was detected.
Action: Look for additional error messages and take appropriate action. If there are no additional errors, call Oracle Worldwide Support.
Cause: An NLS error was detected.
Action: Look for additional error messages and take appropriate action. If there are no additional errors, call Oracle Worldwide Support.
ORA-01883: overlap was disabled during a region transition
ORA-01883: overlap was disabled during a region transition
Cause: The region was changing state and the overlap flag was disabled.
Action: Please contact Oracle Customer Support.
Cause: The region was changing state and the overlap flag was disabled.
Action: Please contact Oracle Customer Support.
ORA-01882: timezone region string not found
ORA-01882: timezone region string not found
Cause: The specified region name was not found.
Action: Please contact Oracle Customer Support.
Cause: The specified region name was not found.
Action: Please contact Oracle Customer Support.
ORA-01881: timezone region id number is invalid
ORA-01881: timezone region id number is invalid
Cause: The region id referenced an invalid region.
Action: Please contact Oracle Customer Support.
Cause: The region id referenced an invalid region.
Action: Please contact Oracle Customer Support.
ORA-01880: the fractional seconds must be between 0 and 999999999
ORA-01880: the fractional seconds must be between 0 and 999999999
Cause: The specified fractional seconds were not in the valid range.
Action: Specify a value for fractional seconds between 0 and 999999999.
Cause: The specified fractional seconds were not in the valid range.
Action: Specify a value for fractional seconds between 0 and 999999999.
ORA-01879: the hh25 field must be between 0 and 24
ORA-01879: the hh25 field must be between 0 and 24
Cause: The specified hh25 field was not in the valid range.
Action: Specify an hh25 field between 0 and 24.
Cause: The specified hh25 field was not in the valid range.
Action: Specify an hh25 field between 0 and 24.
ORA-01878: specified field not found in datetime or interval
ORA-01878: specified field not found in datetime or interval
Cause: The specified field was not found in the datetime or interval.
Action: Make sure that the specified field is in the datetime or interval.
Cause: The specified field was not found in the datetime or interval.
Action: Make sure that the specified field is in the datetime or interval.
ORA-01877: string is too long for internal buffer
ORA-01877: string is too long for internal buffer
Cause: This is an internal error.
Action: Please contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Please contact Oracle Worldwide Support.
ORA-01876: year must be at least -4713
ORA-01876: year must be at least -4713
Cause: The specified year was not in range.
Action: Specify a year that is greater than or equal to -4713.
Cause: The specified year was not in range.
Action: Specify a year that is greater than or equal to -4713.
ORA-01875: time zone minute must be between -59 and 59
ORA-01875: time zone minute must be between -59 and 59
Cause: The time zone minute specified was not in the valid range.
Action: Specify a time zone minute between -59 and 59.
Cause: The time zone minute specified was not in the valid range.
Action: Specify a time zone minute between -59 and 59.
ORA-01874: time zone hour must be between -12 and 14
ORA-01874: time zone hour must be between -12 and 14
Cause: The time zone hour specified was not in the valid range.
Action: Specify a time zone hour between -12 and 14.
Cause: The time zone hour specified was not in the valid range.
Action: Specify a time zone hour between -12 and 14.
ORA-01873: the leading precision of the interval is too small
ORA-01873: the leading precision of the interval is too small
Cause: The leading precision of the interval is too small to store the specified interval.
Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision.
Cause: The leading precision of the interval is too small to store the specified interval.
Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision.
ORA-01871: the number of seconds must be less than 60
ORA-01871: the number of seconds must be less than 60
Cause: The number of seconds specified was greater than 59.
Action: Specify a value for seconds that is 59 or smaller.
Cause: The number of seconds specified was greater than 59.
Action: Specify a value for seconds that is 59 or smaller.
ORA-01870: the intervals or datetimes are not mutually comparable
ORA-01870: the intervals or datetimes are not mutually comparable
Cause: The intervals or datetimes are not mutually comparable.
Action: Specify a pair of intervals or datetimes that are mutually comparable.
Cause: The intervals or datetimes are not mutually comparable.
Action: Specify a pair of intervals or datetimes that are mutually comparable.
ORA-01868: the leading precision of the interval is too small
ORA-01868: the leading precision of the interval is too small
Cause: The leading precision of the interval is too small to store the specified interval.
Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision.
Cause: The leading precision of the interval is too small to store the specified interval.
Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision.
ORA-01867: the interval is invalid
ORA-01867: the interval is invalid
Cause: The character string you specified is not a valid interval.
Action: Please specify a valid interval.
Cause: The character string you specified is not a valid interval.
Action: Please specify a valid interval.
ORA-01866: the datetime class is invalid
ORA-01866: the datetime class is invalid
Cause: This is an internal error.
Action: Please contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Please contact Oracle Worldwide Support.
ORA-01865: not a valid era
ORA-01865: not a valid era
Cause: Era input does not match a known era.
Action: Provide a valid era on input.
Cause: Era input does not match a known era.
Action: Provide a valid era on input.
ORA-01864: the date is out of range for the current calendar
ORA-01864: the date is out of range for the current calendar
Cause: Your calendar doesn t extend to the specified date.
Action: Specify a date which is legal for this calendar.
Cause: Your calendar doesn t extend to the specified date.
Action: Specify a date which is legal for this calendar.
ORA-01863: the year is not supported for the current calendar
ORA-01863: the year is not supported for the current calendar
Cause: The year is not supported for the current calendar.
Action: Please check the documentation to find out what years are supported for the current calendar.
Cause: The year is not supported for the current calendar.
Action: Please check the documentation to find out what years are supported for the current calendar.
ORA-01862: the numeric value does not match the length of the format item
ORA-01862: the numeric value does not match the length of the format item
Cause: When the FX and FM format codes are specified for an input date, then the number of digits must be exactly the number specified by the format code. For example, 9 will not match the format specifier DD but 09 will.
Action: Correct the input date or turn off the FX or FM format specifier in the format string.
Cause: When the FX and FM format codes are specified for an input date, then the number of digits must be exactly the number specified by the format code. For example, 9 will not match the format specifier DD but 09 will.
Action: Correct the input date or turn off the FX or FM format specifier in the format string.
ORA-01861: literal does not match format string
ORA-01861: literal does not match format string
Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the FX modifier has been toggled on, the literal must match exactly, with no extra whitespace.
Action: Correct the format string to match the literal.
Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the FX modifier has been toggled on, the literal must match exactly, with no extra whitespace.
Action: Correct the format string to match the literal.
ORA-01859: a non-alphabetic character was found where an alphabetic was expected
ORA-01859: a non-alphabetic character was found where an alphabetic was expected
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model.
Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model.
Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.
ORA-01858: a non-numeric character was found where a numeric was expected
ORA-01858: a non-numeric character was found where a numeric was expected
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.
Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.
Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.
ORA-01854: julian date must be between 1 and 5373484
ORA-01854: julian date must be between 1 and 5373484
Cause: An invalid Julian date was entered.
Action: Enter a valid Julian date between 1 and 5373484.
Cause: An invalid Julian date was entered.
Action: Enter a valid Julian date between 1 and 5373484.
ORA-01841: (full) year must be between -4713 and +9999, and not be 0
ORA-01841: (full) year must be between -4713 and +9999, and not be 0
Cause: Illegal year entered
Action: Input year in the specified range
Cause: Illegal year entered
Action: Input year in the specified range
ORA-01804: failure to initialize timezone information
ORA-01804: failure to initialize timezone information
Cause: The timezone information file was not properly read.
Action: Please contact Oracle Customer Support.
Cause: The timezone information file was not properly read.
Action: Please contact Oracle Customer Support.
ORA-01799: a column may not be outer-joined to a subquery
ORA-01799: a column may not be outer-joined to a subquery
Cause: lamp;lt;lamp;nbsp;expressionlamp;gt;(+) lamp;lt;lamp;nbsp;reloplamp;gt; (lamp;lt;lamp;nbsp;subquerylamp;gt;) is not allowed.
Action: Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case.
Cause: lamp;lt;lamp;nbsp;expressionlamp;gt;(+) lamp;lt;lamp;nbsp;reloplamp;gt; (lamp;lt;lamp;nbsp;subquerylamp;gt;) is not allowed.
Action: Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case.
ORA-01792: maximum number of columns in a table or view is 1000
ORA-01792: maximum number of columns in a table or view is 1000
Cause: An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.
Action: If the error is a result of a CREATE command, then reduce the number of columns in the command and resubmit. If the error is a result of an ALTER TABLE command, then there are two options: 1) If the table contained unused columns, remove them by executing ALTER TABLE DROP UNUSED COLUMNS before adding new columns; 2) Reduce the number of columns in the command and resubmit.
Cause: An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.
Action: If the error is a result of a CREATE command, then reduce the number of columns in the command and resubmit. If the error is a result of an ALTER TABLE command, then there are two options: 1) If the table contained unused columns, remove them by executing ALTER TABLE DROP UNUSED COLUMNS before adding new columns; 2) Reduce the number of columns in the command and resubmit.
ORA-01784: RECOVERABLE cannot be specified with database media recovery disabled
ORA-01784: RECOVERABLE cannot be specified with database media recovery disabled
Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.
Action: Do not specify RECOVERABLE, or restart the database with media recovery enabled.
Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.
Action: Do not specify RECOVERABLE, or restart the database with media recovery enabled.
ORA-01783: only one RECOVERABLE or UNRECOVERABLE clause may be specified
ORA-01783: only one RECOVERABLE or UNRECOVERABLE clause may be specified
Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.
Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement.
Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.
Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement.
ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table
ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table
Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.
Action: Do not specify UNRECOVERABLE.
Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.
Action: Do not specify UNRECOVERABLE.
ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT
ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT
Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.
Action: Do not specify UNRECOVERABLE.
Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.
Action: Do not specify UNRECOVERABLE.
ORA-01779: cannot modify a column which maps to a non key-preserved table
ORA-01779: cannot modify a column which maps to a non key-preserved table
Cause: An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.
Action: Modify the underlying base tables directly.
Cause: An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.
Action: Modify the underlying base tables directly.
ORA-01776: cannot modify more than one base table through a join view
ORA-01776: cannot modify more than one base table through a join view
Cause: Columns belonging to more than one underlying table were either inserted into or updated.
Action: Phrase the statement as two or more separate statements.
Cause: Columns belonging to more than one underlying table were either inserted into or updated.
Action: Phrase the statement as two or more separate statements.
ORA-01774: Dump undo option specified more than once
ORA-01774: Dump undo option specified more than once
Cause: The same option for ALTER DUMP UNDO was specified twice.
Action: Remove the redundant options and reissue the command.
Cause: The same option for ALTER DUMP UNDO was specified twice.
Action: Remove the redundant options and reissue the command.
ORA-01772: Must specify a value for LEVEL
ORA-01772: Must specify a value for LEVEL
Cause: Expecting the value of LEVEL but something else was specified.
Action: Correct the error and reissue the command.
Cause: Expecting the value of LEVEL but something else was specified.
Action: Correct the error and reissue the command.
ORA-01771: illegal option for a clustered table
ORA-01771: illegal option for a clustered table
Cause: During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. These options may only be specified for the cluster itself.
Action: Remove the illegal option(s).
Cause: During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. These options may only be specified for the cluster itself.
Action: Remove the illegal option(s).
ORA-01769: duplicate CLUSTER option specifications
ORA-01769: duplicate CLUSTER option specifications
Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.
Action: Remove the extra CLUSTER option.
Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.
Action: Remove the extra CLUSTER option.
ORA-01764: new update value of join is not guaranteed to be unique
ORA-01764: new update value of join is not guaranteed to be unique
Cause: A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated.
Action: Change the join specification.
Cause: A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated.
Action: Change the join specification.
ORA-01763: update or delete involves outer joined table
ORA-01763: update or delete involves outer joined table
Cause: For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer-joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table.
Action: Change the join specification.
Cause: For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer-joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table.
Action: Change the join specification.
ORA-01761: DML operation does not map to a unique table in the join
ORA-01761: DML operation does not map to a unique table in the join
Cause: The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table.
Action: Change the join specification.
Cause: The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table.
Action: Change the join specification.
ORA-01757: Must specify an object number
ORA-01757: Must specify an object number
Cause: Expecting an object number but something else was specified.
Action: Correct the error and reissue the command.
Cause: Expecting an object number but something else was specified.
Action: Correct the error and reissue the command.
ORA-01755: Must specify an extent number or block number
ORA-01755: Must specify an extent number or block number
Cause: Expecting an extent or block number but something else was specified.
Action: Correct the error and reissue the command.
Cause: Expecting an extent or block number but something else was specified.
Action: Correct the error and reissue the command.
ORA-01754: a table may contain only one column of type LONG
ORA-01754: a table may contain only one column of type LONG
Cause: An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped.
Action: Remove the LONG column currently in the table by using the ALTER TABLE command.
Cause: An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped.
Action: Remove the LONG column currently in the table by using the ALTER TABLE command.
Subscribe to:
Posts (Atom)