72 ORA-00900 to ORA-01499
- ORA-00900: invalid SQL statement
-
Cause: The statement was not recognized as a valid SQL statement. This error can occurred if the Procedural Option was not installed and a SQL statement was issued that requires this option (for example, a CREATE PROCEDURE statement). You can determine if the Procedural Option was installed by starting SQL*Plus. If the PL/SQL banner was not displayed, then the option was not installed.
- ORA-00901: invalid CREATE command
-
Cause: The CREATE command was not followed by a valid CREATE option.
- ORA-00902: invalid datatype
-
Cause: The datatype entered in the CREATE or ALTER TABLE statement is not valid.
- ORA-00903: invalid table name
-
Cause: A table or cluster name was invalid or does not exist. This message was also issued if an invalid cluster name or no cluster name was specified in an ALTER CLUSTER or DROP CLUSTER statement.
- ORA-00904: string: invalid identifier
-
Cause: The column name entered was either missing or invalid.
- ORA-00905: missing keyword
-
Cause: A required keyword was missing.
- ORA-00906: missing left parenthesis
-
Cause: A required left parenthesis has been omitted. Certain commands, such as CREATE TABLE, CREATE CLUSTER, and INSERT, require a list of items enclosed in parentheses. Parentheses also are required around subqueries in WHERE clauses and in UPDATE table SET column = (SELECT...) statements.
- ORA-00907: missing right parenthesis
-
Cause: A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs.
- ORA-00908: missing NULL keyword
-
Cause: Either of the following: In a CREATE TABLE or ALTER TABLE statement, NOT was entered to specify that no null values are allowed in that column, but the keyword NULL was omitted. In the IS [NOT] NULL logical operator, the keyword NULL was not found. For example, the following statement generates this message: SELECT * FROM EMP WHERE DEPTNO IS NOT; The keyword NULL must follow the keywords IS NOT.
- ORA-00909: invalid number of arguments
-
Cause: An Oracle function was referenced with an incorrect number of arguments. All Oracle functions, except for SYSDATE, required at least one argument.
- ORA-00910: specified length too long for its datatype
-
Cause: for datatypes CHAR and RAW, the length specified was > 2000; otherwise, the length specified was > 4000.
- ORA-00911: invalid character
-
Cause: The identifier name started with an ASCII character other than a letter or a number. After the first character of the identifier name, ASCII characters are allowed including "$", "#" and "_". Identifiers enclosed in double quotation marks may contain any character other than a double quotation. Alternate quotation marks (q'#...#') cannot use spaces, tabs, or carriage returns as delimiters. For all other contexts, consult the SQL Language Reference Manual.
- ORA-00912: input parameter too long
-
Cause: one of your input strings was too long
- ORA-00913: too many values
-
Cause: The SQL statement requires two sets of values equal in number. This error occurs when the second set contains more items than the first set. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in the INSERT.
- ORA-00914: missing ADD keyword
-
Cause: The keyword ADD does not precede one of the following: - The keyword log file in an ALTER DATABASE statement - A column element or table constraint in an ALTER TABLE statement - The keyword DATAFILE in an ALTER TABLESPACE statement
- ORA-00915: network access of dictionary table not currently allowed
-
Cause: This is an internal error message not usually issued.
- ORA-00917: missing comma
-
Cause: A required comma has been omitted from a list of columns or values in an INSERT statement or a list of the form ((C,D),(E,F), ...).
- ORA-00918: column ambiguously defined
-
Cause: A column name used in a join exists in more than one table and was thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO.
- ORA-00919: invalid function
-
Cause: An entry was formatted like a function call, but it was not recognizable as an Oracle function.
- ORA-00920: invalid relational operator
-
Cause: A search condition was entered with an invalid or missing relational operator.
- ORA-00921: unexpected end of SQL command
-
Cause: The SQL command was not complete. Part of a valid command was entered, but at least one major component was omitted.
- ORA-00922: missing or invalid option
-
Cause: An invalid option was specified in defining a column or storage clause. The valid option in specifying a column was NOT NULL to specify that the column cannot contain any NULL values. Only constraints may follow the datatype. Specifying a maximum length on a DATE or LONG datatype also causes this error.
- ORA-00923: FROM keyword not found where expected
-
Cause: In a SELECT or REVOKE statement, the keyword FROM was either missing, misplaced, or misspelled. The keyword FROM must follow the last selected item in a SELECT statement or the privileges in a REVOKE statement.
- ORA-00924: missing BY keyword
-
Cause: The keyword BY was omitted in a GROUP BY, ORDER BY, or CONNECT BY clause. In a GRANT statement, the keyword IDENTIFIED must also be followed by the keyword BY.
- ORA-00925: missing INTO keyword
-
Cause: An INSERT statement has been entered without the keyword INTO.
- ORA-00926: missing VALUES keyword
-
Cause: An INSERT statement has been entered without the keyword VALUES or SELECT. Either a VALUES clause or a SELECT subquery must follow the INSERT INTO clause.
- ORA-00927: missing equal sign
-
Cause: An equal sign has been omitted in one of the following places: - In the SET clause of an UPDATE statement - Following "!" in a search condition to signify not equal
- ORA-00928: missing SELECT keyword
-
Cause: A SELECT subquery must be included in a CREATE VIEW statement.
- ORA-00929: missing period
-
Cause: This is an internal error message not usually issued.
- ORA-00930: missing asterisk
-
Cause: This is an internal error message not usually issued.
- ORA-00931: missing identifier
-
Cause: The specified string does not contain an identifier.
- ORA-00932: inconsistent datatypes: expected string got string
-
Cause: One of the following: - An attempt was made to perform an operation on incompatible datatypes. For example, adding a character field to a date field (dates may only be added to numeric fields) or concatenating a character field with a long field. - An attempt was made to perform an operation on a database object (such as a table or view) that was not intended for normal use. For example, system tables cannot be modified by a user. Note that on rare occasions this error occurs because a misspelled object name matched a restricted object's name. - An attempt was made to use an undocumented view.
- ORA-00933: SQL command not properly ended
-
Cause: The SQL statement ends with an inappropriate clause. For example, an ORDER BY clause may have been included in a CREATE VIEW or INSERT statement. ORDER BY cannot be used to create an ordered view or to insert in a certain order.
- ORA-00934: group function is not allowed here
-
Cause: One of the group functions, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used in a WHERE or GROUP BY clause.
- ORA-00935: group function is nested too deeply
-
Cause: This is an internal error message not usually issued.
- ORA-00936: missing expression
-
Cause: A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message was also issued in cases where a reserved word was misused, as in SELECT TABLE.
- ORA-00937: not a single-group group function
-
Cause: A SELECT list cannot include both a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, and an individual column expression, unless the individual column expression was included in a GROUP BY clause.
- ORA-00938: not enough arguments for function
-
Cause: The function was referenced with too few arguments.
- ORA-00939: too many arguments for function
-
Cause: The function was referenced with too many arguments.
- ORA-00940: invalid ALTER command
-
Cause: An invalid ALTER option was specified.
- ORA-00941: missing cluster name
-
Cause: The cluster name was either missing or invalid.
- ORA-00942: table or view does not exist
-
Cause: The table or view entered did not exist, a synonym that was not allowed here was used, or a view was referenced where a table was required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access did not exist in the database, or the application did not have access to it.
- ORA-00943: cluster does not exist
-
Cause: The current user owns no cluster by the specified name.
- ORA-00944: insufficient number of clustered columns
-
Cause: An attempt was made to create a table with fewer cluster columns than were specified in the CREATE CLUSTER statement. The CLUSTER clause of a CREATE TABLE statement must specify all cluster columns that were defined when the cluster was created.
- ORA-00945: specified clustered column does not exist
-
Cause: A column specified in the cluster clause of a CREATE TABLE statement was not a column in this table.
- ORA-00946: missing TO keyword
-
Cause: A GRANT statement was specified without the keyword TO, or an invalid form of the GRANT command was entered.
- ORA-00947: not enough values
-
Cause: This error occurs when a SQL statement requires two sets of values equal in number, but the second set contains fewer items than the first set. This can occur in a WHERE or HAVING clause in which a nested SELECT returns too few columns as in: WHERE (A,B) IN (SELECT C FROM ...) Another common cause of this error is an INSERT statement in which the VALUES or SELECT clause does not contain enough values needed for the INSERT, as in INSERT INTO EMP(EMPNO,ENAME) VALUES('JONES')
- ORA-00948: ALTER CLUSTER statement no longer supported
-
Cause: The ALTER CLUSTER statement has been withdrawn.
- ORA-00949: illegal reference to remote database
-
Cause: This was an internal error message not usually issued.
- ORA-00950: invalid DROP option
-
Cause: A DROP command was not followed by a valid DROP option, such as CLUSTER, DATABASE LINK, INDEX, ROLLBACK SEGMENT, SEQUENCE, SYNONYM, TABLE, TABLESPACE, or VIEW.
- ORA-00951: cluster not empty
-
Cause: A DROP CLUSTER statement specified a cluster that was not empty. A cluster may not be dropped if it contains any tables, unless the optional INCLUDING TABLES clause was specified. Tables may also be removed from a cluster by using the DROP TABLE command.
- ORA-00952: missing GROUP keyword
-
Cause: Groups were not implemented.
- ORA-00953: missing or invalid index name
-
Cause: An index name of the form [ identifier . ] identifier was expected but not present. If OIDINDEX clause, index name must be identifier.
- ORA-00954: missing IDENTIFIED keyword
-
Cause: A GRANT CONNECT statement was issued without the keyword IDENTIFIED.
- ORA-00955: name is already used by an existing object
-
Cause: An attempt was made to create a database object (such as a table, view, cluster, index, or synonym) that already existed. A user's database objects must have distinct names.
- ORA-00956: missing or invalid auditing option
-
Cause: AUDIT or NOAUDIT statement contains an invalid auditing option.
- ORA-00957: duplicate column name
-
Cause: A column name was specified twice in a CREATE or INSERT statement. Column names must be unique within a table, view, or cluster.
- ORA-00958: missing CHECK keyword
-
Cause: The keyword CHECK should follow the keyword WITH in the WITH OPTION clause of the CREATE VIEW statement.
- ORA-00959: tablespace 'string' does not exist
-
Cause: A statement specified the name of a tablespace that did not exist.
- ORA-00960: ambiguous column naming in select list
-
Cause: A column name in the order-by list matched more than one select list columns.
- ORA-00961: bad datetime/interval value
-
- ORA-00962: too many group-by / order-by expressions
-
Cause: The group-by or order-by column list contain more than 1000 expressions.
- ORA-00963: unsupported interval type
-
Cause: An unsupported interval type was encountered.
- ORA-00964: table name not in FROM list
-
Cause: The table name referred in the select list is not specified in the from list.
- ORA-00965: column aliases not allowed for '*'
-
Cause: The statement is trying to alias the * expression in the select list which is not legal.
- ORA-00966: missing TABLE keyword
-
Cause: A LOCK statement was specified and the keyword TABLE was missing, misspelled, or misplaced. A LOCK statement must begin with LOCK TABLE tablename.
- ORA-00967: missing WHERE keyword
-
Cause: The keyword WHERE in a SELECT statement was missing, misspelled, or misplaced.
- ORA-00968: missing INDEX keyword
-
Cause: The keyword INDEX in a CREATE UNIQUE INDEX or VALIDATE INDEX statement was missing, misspelled, or misplaced.
- ORA-00969: missing ON keyword
-
Cause: The keyword ON in a GRANT, REVOKE, or CREATE INDEX statement was missing, misspelled, or misplaced.
- ORA-00970: missing WITH keyword
-
Cause: The keyword START was specified without the keyword WITH. Both keywords were necessary if a START WITH clause is desired in a tree-structured query.
- ORA-00971: missing SET keyword
-
Cause: The keyword SET in an UPDATE statement is missing, misspelled, or misplaced.
- ORA-00972: identifier is too long
-
Cause: An identifier with more than 128 bytes was specified, or a password identifier longer than 30 bytes was specified.
- ORA-00973: invalid row count estimate
-
- ORA-00974: invalid PCTFREE value (percentage)
-
Cause: The percentage of free space specified in a CREATE INDEX statement was not between 0 and 100. A PCTFREE value of 0 means the entire block was available. The value 100 was not useful because it means that no data may be inserted. The default was 10.
- ORA-00975: date + date not allowed
-
Cause: An attempt was made to add two date fields together. Dates may be added only to numeric fields, not to other dates.
- ORA-00976: Specified pseudocolumn or operator not allowed here.
-
Cause: LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or CONNECT_BY_ISCYCLE was specified at an illegal location.
- ORA-00977: duplicate auditing option
-
Cause: AUDIT or NOAUDIT statement specifies an option more than once
- ORA-00978: nested group function without GROUP BY
-
Cause: A group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used within another group function, as in MAX(COUNT(*)), without a corresponding GROUP BY clause.
- ORA-00979: not a GROUP BY expression
-
Cause: The expression did not match any of the expressions in the GROUP BY clause and was not a constant or an aggregate function or an expression involving these elements.
- ORA-00980: synonym translation is no longer valid
-
Cause: A synonym did not translate to a legal target object. This could happen for one of the following reasons: 1. The target schema does not exist. 2. The target object does not exist. 3. The synonym specifies an incorrect database link. 4. The synonym is not versioned but specifies a versioned target object.
- ORA-00981: cannot mix table and system auditing options
-
Cause: Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement.
- ORA-00982: missing plus sign
-
Cause: A left parenthesis appeared in a join condition, but a plus sign (+) did not follow. A left parenthesis in a join condition usually signals an outer-join specification and so a plus sign was expected to follow. To specify an outer join on a column in a join operation, follow the column reference in the join condition with a plus sign (+) enclosed in parentheses.
- ORA-00983: cannot audit or noaudit SYS user actions
-
Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.
- ORA-00984: column not allowed here
-
Cause: A column name was used in an expression where it was not permitted, such as in the VALUES clause of an INSERT statement.
- ORA-00985: invalid program name
-
Cause: Probably a syntax error.
- ORA-00986: missing or invalid group name(s)
-
Cause: Probably a syntax error.
- ORA-00987: missing or invalid username(s)
-
Cause: No username was specified in a GRANT statement or one of the specified usernames was invalid. Valid usernames must be specified following the keyword TO in a GRANT statement to define a user. A username must begin with a letter, consisted only of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. If it contained other characters, it must be enclosed in double quotation marks. It may not be a reserved word.
- ORA-00988: missing or invalid password(s)
-
Cause: More usernames than passwords were specified in a GRANT statement. A valid password must be specified for each username listed in the GRANT statement.
- ORA-00989: too many passwords for usernames given
-
Cause: More passwords than usernames were specified in a GRANT statement. Only one password may be entered for each username listed in the GRANT statement.
- ORA-00990: missing or invalid privilege
-
Cause: No privileges were specified in a GRANT privilege statement, or one of the specified privileges is invalid.
- ORA-00991: only MAC privileges may be granted to procedures
-
Cause: Object privileges or non-MAC system privileges were granted to the procedure.
- ORA-00992: invalid format for REVOKE command
-
Cause: An invalid form of the REVOKE command was entered. There are two forms of the REVOKE command. The first form was used to revoke a user's database access privileges. The second form was used to revoke a user's object privileges.
- ORA-00993: missing GRANT keyword
-
Cause: The keyword WITH was specified at the end of a GRANT statement without the keyword GRANT. To grant privileges to a user and the permission to grant those privileges to another user, you must specify the keywords WITH GRANT OPTION at the end of the GRANT statement.
- ORA-00994: missing OPTION keyword
-
Cause: The keywords WITH GRANT were specified at the end of a GRANT statement without the keyword OPTION.
- ORA-00995: missing or invalid synonym identifier
-
Cause: In a CREATE or DROP SYNONYM statement, the synonym name was either missing or invalid.
- ORA-00996: the concatenate operator is ||, not |
-
Cause: A single bar (|) was interpreted as an attempt to specify concatenation, but the concatenation operator was a double bar (||).
- ORA-00997: illegal use of LONG datatype
-
Cause: A value of datatype LONG was used in a function or in a DISTINCT, WHERE, CONNECT BY, GROUP BY, or ORDER BY clause. A LONG value can only be used in a SELECT clause.
- ORA-00998: must name this expression with a column alias
-
Cause: An expression or function was used in a CREATE VIEW statement, but no corresponding column name was specified. When expressions or functions are used in a view, all column names for the view must be explicitly specified in the CREATE VIEW statement.
- ORA-00999: invalid view name
-
Cause: In a CREATE VIEW statement, the view name was missing or invalid.
- ORA-01000: maximum open cursors exceeded
-
Cause: A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determined the maximum number of cursors per user.
- ORA-01001: invalid cursor
-
Cause: Either a host language program call specified an invalid cursor or the value of the MAXOPENCURSORS option in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA was not defined, this message was issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF.
- ORA-01002: fetch out of sequence
-
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including: 1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error. 3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
- ORA-01003: no statement parsed
-
Cause: A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE, and FETCH.
- ORA-01004: default username feature not supported; logon denied
-
Cause: An attempt was made to use automatic logon on a system not supporting this feature.
- ORA-01005: null password given; logon denied
-
Cause: An invalid password was given when logging on.
- ORA-01006: bind variable does not exist
-
Cause: A program issued a BIND call for a variable not listed in the associated SQL statement. Only those variables prefixed by either a colon (:) or ampersand (&) in the SQL statement may be referenced in a BIND call, OBIND or OBINDN. This error may also be caused by a mismatch between a Precompiler program and the related library, SQLLIB.
- ORA-01007: variable not in select list
-
Cause: A reference was made to a variable not listed in the SELECT clause. In OCI, this can occur if the number passed for the position parameter was less than one or greater than the number of variables in the SELECT clause in any of the following calls: DESCRIBE, NAME, or DEFINE. In SQL*Forms or SQL*Report, specifying more variables in an INTO clause than in the SELECT clause also causes this error.
- ORA-01008: not all variables bound
-
Cause: A SQL statement containing substitution variables was executed without all variables bound. All substitution variables must have a substituted value before the SQL statement was executed.
- ORA-01009: missing mandatory parameter
-
Cause: A host language program call did not pass all required parameters.
- ORA-01010: invalid OCI operation
-
Cause: One of the following: 1) You attempted an invalid OCI operation. 2) You are using an Oracle client application linked with version 7.1 (or higher) libraries, the environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to connect to a version 7.0 (or lower) Oracle Server. 3) You are connected to a version 7.1 (or higher) Oracle Server, the initialization parameter DBLINK_ENCRYPT_LOGIN is set to TRUE, and you attempted to use a database link pointing to a version 7.0 (or lower) Oracle Server. 4) You are connected to a version 9.0.2(or higher) Oracle Server and you attempted to use a database link pointing to a version 9.0.1(or lower) Oracle Server for distributed autonomous transaction.
- ORA-01011: Cannot use v7 compatibility mode when talking to v6 server
-
Cause: An attempt was made to use Oracle7 compatibility mode when accessing Oracle version 6.
- ORA-01012: not logged on
-
Cause: A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle. This occurred when a user process attempts to access the database after the instance it was connected to terminates, forcing the process to disconnect.
- ORA-01013: user requested cancel of current operation
-
Cause: The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation. This forces the current operation to end. This is an informational message only.
- ORA-01014: ORACLE shutdown in progress
-
Cause: A user tried to log on to Oracle while an instance shutdown was in progress. Oracle logons were disabled while Oracle was being shut down.
- ORA-01015: logon called recursively
-
Cause: This is an internal error message not usually issued.
- ORA-01016: This function can be called only after a fetch
-
Cause: Cursor in an invalid state.
- ORA-01017: invalid username/password; logon denied
-
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password were entered together, the format was: username/password.
- ORA-01018: column does not have a LONG datatype
-
Cause: An attempt was made to fetch data using the LONG fetch option, but the specified column was not LONG.
- ORA-01019: unable to allocate memory in the user side
-
Cause: The user side memory allocator returned error.
- ORA-01020: unknown context state
-
Cause: This is an internal error message not usually issued.
- ORA-01021: invalid context size specified
-
Cause: This is an internal error message not usually issued.
- ORA-01022: database operation not supported in this configuration
-
Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating ORACLE servers.
- ORA-01023: Cursor context not found (Invalid cursor number)
-
Cause: The cursor number is not a valid open cursor.
- ORA-01024: invalid datatype in OCI call
-
Cause: An OCI program call specified an invalid datatype. In OCI calls, Oracle datatypes were specified as numbers between 1 and 7.
- ORA-01025: UPI parameter out of range
-
Cause: An integer parameter to a upi function is out of range.
- ORA-01026: multiple buffers of size > 4000 in the bind list
-
Cause: More than one long buffer in the bind list.
- ORA-01027: bind variables not allowed for data definition operations
-
Cause: An attempt was made to use a bind variable in a SQL data definition operation.
- ORA-01028: internal two task error
-
Cause: Received send long message but don't have the cursor context.
- ORA-01029: internal two task error
-
Cause: Received a request to send the long again when there is no long
- ORA-01030: SELECT ... INTO variable does not exist
-
Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.
- ORA-01031: insufficient privileges
-
Cause: An attempt was made to perform a database operation without the necessary privileges.
- ORA-01032: no such userid
-
Cause: This is an internal error message related to Export/Import.
- ORA-01033: ORACLE initialization or shutdown in progress
-
Cause: An attempt was made to log on while Oracle is being started up or shutdown.
- ORA-01034: ORACLE not available
-
Cause: Oracle was not started up. Possible causes include the following: - The SGA requires more space than was allocated for it. - The operating-system variable pointing to the instance is improperly defined.
- ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege
-
Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.
- ORA-01036: illegal variable name/number
-
Cause: Unable to find bind context on user side
- ORA-01037: maximum cursor memory exceeded
-
Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor.
- ORA-01038: cannot write database file version string with ORACLE version string
-
Cause: Attempting to write datafile headers in an old format. The new format can not be used until after the database has been verified as being compatible with this software version.
- ORA-01039: insufficient privileges on underlying objects of the view
-
Cause: Attempting to explain plan on other people's view without the necessary privileges on the underlying objects of the view.
- ORA-01040: invalid character in password; logon denied
-
Cause: There are multibyte characters in the password or some characters in the password are not in US7ASCII range.
- ORA-01041: internal error. hostdef extension doesn't exist
-
Cause: Pointer to hstdef extension in hstdef is null.
- ORA-01042: detaching a session with open cursors not allowed
-
Cause: An attempt was made to detach a seesio n which had open cursors.
- ORA-01043: user side memory corruption [string], [string], [string], [string]
-
Cause: The application code corrupted some of the usr memory used by oracle
- ORA-01044: size string of buffer bound to variable exceeds maximum string
-
Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as: (element_size)*(number of elements)
- ORA-01045: user string lacks CREATE SESSION privilege; logon denied
-
Cause: A connect was attempted to a userid which does not have create session privilege.
- ORA-01046: cannot acquire space to extend context area
-
Cause: Oracle could not extend the current area any further because the operating system would not supply any more space. A system-specific message should appear following this message.
- ORA-01047: The above error occurred in schema=string, package=string, procedure=string
-
Cause: This message was displayed after a previous message to provide more specific information.
- ORA-01048: Couldn't find the specified procedure in the given context
-
Cause: The procedure user specified in deferred RPC doesn't exist.
- ORA-01049: Bind by name is not spupportted in streamed RPC
-
Cause: A newer version of server is talking with this version requesting an operation not supported in this version.
- ORA-01050: cannot acquire space to open context area
-
Cause: Oracle could not open a new context area because the operating system would not supply any more space. A system-specific message should appear following this message.
- ORA-01051: deferred rpc buffer format invalid
-
Cause: The deferred rpc data in sys.def$_call is corrupted.
- ORA-01052: required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
-
Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two.
- ORA-01053: user storage address cannot be read
-
Cause: A bind variable or other user area could not be read by Oracle.
- ORA-01054: user storage address cannot be written
-
Cause: A define, FETCH... INTO or SELECT... INTO, variable or other user area could not be written to by Oracle.
- ORA-01055: Object datatypes not supported for bind or define in this mode
-
Cause: Bind or Define used for objects with an invalid mode
- ORA-01057: invalid or ambiguous block.field reference in user exit
-
Cause: The reference to a block.field identifier in a user exit was incorrect or ambiguous, probably because it was misspelled or incomplete.
- ORA-01058: internal New Upi interface error
-
Cause: Attempt to delete nonexistent hstdef extension.
- ORA-01059: parse expected before a bind or execute
-
Cause: The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed.
- ORA-01060: array binds or executes not allowed
-
Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor.
- ORA-01061: cannot start up a V8 server using a V7 client application
-
Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server.
- ORA-01062: unable to allocate memory for define buffer
-
Cause: Exceeded the maximum buffer size for current plaform
- ORA-01063: fetch row count exceeds MINSWORDMAXVAL
-
Cause: The total number of rows requested from the server exceeded the maximum specified in MINSWORDMAXVAL.
- ORA-01064: invalid value 'string' for parameter INSTANCE_TYPE in XE Edition
-
Cause: A value other than RDBMS was specified for the INSTANCE_TYPE parameter in Oracle Database Express Edition (XE).
- ORA-01070: Using an old version of Oracle for the server
-
Cause: Using pre 7.0.10.1 version of oracle for server
- ORA-01071: cannot perform operation without starting up ORACLE
-
Cause: An attempt was made to perform an operation before Oracle was started.
- ORA-01072: cannot stop ORACLE; ORACLE not running
-
Cause: An attempt was made to stop Oracle, but Oracle was not running.
- ORA-01073: fatal connection error: unrecognized call type
-
Cause: An illegal internal operation was attempted.
- ORA-01074: cannot shut down ORACLE; inside a login session - log off first
-
Cause: An attempt was made to shut down Oracle inside a logon session.
- ORA-01075: you are currently logged on
-
Cause: Attempt to login while logged in.
- ORA-01076: multiple logons per process not yet supported
-
Cause: Oracle did not support multiple logons per process.
- ORA-01077: background process initialization failure
-
Cause: Failure during initialization of ORACLE background processes.
- ORA-01078: failure in processing system parameters
-
Cause: Failure during processing of INIT.ORA parameters during system startup.
- ORA-01079: ORACLE database was not properly created, operation aborted
-
Cause: There was an error when the database or control file was created.
- ORA-01080: error in shutting down ORACLE
-
Cause: Failure during system shutdown.
- ORA-01081: cannot start already-running ORACLE - shut it down first
-
Cause: An attempt was made to start Oracle while it was already running.
- ORA-01082: 'row_locking = always' requires the transaction processing option
-
Cause: "row_locking = always" is specified in INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option.
- ORA-01083: value of parameter "string" is inconsistent with that of other instances
-
Cause: The value of the given parameter is required to be the same for all instances in the cluster database configuration. ROW_LOCKING and SERIALIZABLE are 2 examples.
- ORA-01084: invalid argument in OCI call
-
Cause: The failing OCI call contains an argument with an invalid value.
- ORA-01085: preceding errors in deferred rpc to "string.string.string"
-
Cause: Errors were encountered when the named procedure was executed as a deferred remoted procedure call.
- ORA-01086: savepoint 'string' never established in this session or is invalid
-
Cause: An attempt was made to roll back to a savepoint that was never established in this session, or was invalid.
- ORA-01087: cannot start up ORACLE - currently logged on
-
Cause: An attempt was made to start up Oracle by a user who was currently logged on.
- ORA-01088: shutdown in progress - operation not permitted until restart
-
Cause: The SHUTDOWN command was used to shut down a running Oracle instance but the shutdown operation was not complete.
- ORA-01089: immediate shutdown or close in progress - no operations are permitted
-
Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, or CLOSE IMMEDIATE was used to shut down a pluggable database, so your operations have been terminated.
- ORA-01090: shutdown in progress - connection is not permitted
-
Cause: The SHUTDOWN command was used to shut down a running ORACLE instance, so you cannot connect to ORACLE.
- ORA-01091: failure during startup force
-
Cause: Unable to destroy the old SGA.
- ORA-01092: ORACLE instance terminated. Disconnection forced
-
Cause: The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance.
- ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected
-
Cause: There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted.
- ORA-01094: ALTER DATABASE or ALTER PLUGGABLE DATABASE CLOSE in progress. Connections not permitted
-
Cause: An attempt was made to connect while the database was being closed with the ALTER DATABASE CLOSE statement.
- ORA-01095: DML statement processed zero rows
-
Cause: During a call to OTEX, an update, delete, or insert statement being executed processed zero rows. The execution of statements by OTEX was halted at this point.
- ORA-01096: program version (string) incompatible with instance (string)
-
Cause: A program is trying to connect to an instance using a different version of code than the database was started with. This is not allowed.
- ORA-01097: cannot shutdown while in a transaction - commit or rollback first
-
Cause: An attempt was made to shut down the database while a transaction was in progress.
- ORA-01098: program Interface error during Long Insert
-
Cause: The application program interface could not insert or update a LONG column because of an internal error when a TTCGETV call fails. For example, a network read error or one of the parameters passed to the call is invalid.
- ORA-01099: cannot mount database in SHARED mode if started in single process mode
-
Cause: An attempt was made to mount a database in parallel mode with the initialization parameter SINGLE_PROCESS set to TRUE.
- ORA-01100: database already mounted
-
Cause: A database is already mounted in this instance.
- ORA-01101: database being created currently mounted by some other instance
-
Cause: Some other instance has the database of same name currently mounted and you are trying to create it.
- ORA-01102: cannot mount database in EXCLUSIVE mode
-
Cause: Some other instance has the database mounted exclusive or shared.
- ORA-01103: database name 'string' in control file is not 'string'
-
Cause: The database name in the control file does not match your database name.
- ORA-01104: number of control files (string) does not equal string
-
Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance.
- ORA-01105: mount is incompatible with mounts by other instances
-
Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why.
- ORA-01106: database must be closed before dismounting
-
Cause: An attempt was made to dismount a database before it was closed.
- ORA-01107: database must be mounted for media recovery
-
Cause: An attempt to perform media recovery was made but the database is not mounted.
- ORA-01108: file string is in backup or media recovery
-
Cause: Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery.
- ORA-01109: database not open
-
Cause: A command was attempted that requires the database to be open.
- ORA-01110: data file string: 'string'
-
Cause: Reporting file name for details of another error. The reported name can be of the old file if a data file move operation is in progress.
- ORA-01111: name for data file string is unknown - rename to correct file
-
Cause: The data file was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created.
- ORA-01112: media recovery not started
-
Cause: An attempt to continue media recovery is being made but media recovery was not started.
- ORA-01113: file string needs media recovery
-
Cause: An attempt was made to online or open a database with a file that is in need of media recovery.
- ORA-01114: IO error writing block to file string (block # string)
-
Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.
- ORA-01115: IO error reading block from file string (block # string)
-
Cause: Device on which the file resides is probably offline
- ORA-01116: error in opening database file string
-
Cause: Usually the file is not accessible.
- ORA-01117: adding file 'string' with illegal block size: string; max limit is string; min limit is string
-
Cause: An attempt was made to add a database file with a block size that was greater than the maximum block size allowed or less than the minimum block size allowed or an invalid value (that is, not power of 2) in the allowed range.
- ORA-01118: cannot add any more database files: limit of string exceeded
-
Cause: There is no more room in the control file for adding database files.
- ORA-01119: error in creating database file 'string'
-
Cause: Usually due to not having enough space on the device.
- ORA-01120: cannot remove online database file string
-
Cause: Attempting to drop a datafile when it is online
- ORA-01121: cannot rename database file string - file is in use or recovery
-
Cause: Attempted to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered.
- ORA-01122: database file string failed verification check
-
Cause: The information in this file is inconsistent with information from the control file. See accompanying message for reason.
- ORA-01123: cannot start online backup; media recovery not enabled
-
Cause: An attempt to start backup of an on-line tablespace failed because media recovery is not enabled.
- ORA-01124: cannot recover data file string - file is in use or recovery
-
Cause: An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is curently doing media recovery on the file.
- ORA-01125: cannot disable media recovery - file string has online backup set
-
Cause: An attempt to disable media recovery found that an online backup is still in progress.
- ORA-01126: database must be mounted in this instance and not open in any instance
-
Cause: An operation failed because the database was not mounted in exclusive mode.
- ORA-01127: database name 'string' exceeds size limit of string characters
-
Cause: The specified database name was too long.
- ORA-01128: cannot start online backup - file string is offline
-
Cause: An attempt to start an online backup found that one of the files is offline.
- ORA-01129: user's default or temporary tablespace does not exist
-
Cause: The user's default or temporary tablespace was dropped.
- ORA-01130: database file version string incompatible with ORACLE version string
-
Cause: The named datafile was created under an incompatible version of Oracle, or the file was invalid or non-existent.
- ORA-01131: DB_FILES system parameter value string exceeds limit of string
-
Cause: The specified value of the initialization parameter DB_FILES was too large.
- ORA-01132: length of database file name 'string' exceeds limit of string characters
-
Cause: The specified datafile name was too long.
- ORA-01133: length of log file name 'string' exceeds limit of string characters
-
Cause: The specified redo log file name was too long.
- ORA-01134: database mounted exclusive by another instance
-
Cause: An attempt to access a database failed because it was mounted in exclusive mode by another instance.
- ORA-01135: file string accessed for DML/query is offline
-
Cause: Attempted to access a data file that was offline.
- ORA-01136: specified size of file string (string blocks) is less than original size of string blocks
-
Cause: A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller the the size needed
- ORA-01137: data file string is still in the middle of going offline
-
Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline.
- ORA-01138: database must either be open in this instance or not at all
-
Cause: The requested operation can not be done when the database is mounted but not open in this instance, and another instance has the database open.
- ORA-01139: RESETLOGS option only valid after an incomplete database recovery
-
Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session.
- ORA-01140: cannot end online backup - all files are offline or readonly
-
Cause: All the files were found to be offline or readonly when attempting to end an online backup.
- ORA-01141: error renaming data file string - new file 'string' not found
-
Cause: An attempt to change a data file's name in the control file failed because no file was found with the new name.
- ORA-01142: cannot end online backup - none of the files are in backup
-
Cause: None of the files were found to be in online backup when attempting to end an online backup.
- ORA-01143: cannot disable media recovery - file string needs media recovery
-
Cause: An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled.
- ORA-01144: File size (string blocks) exceeds maximum of string blocks
-
Cause: Specified file size is larger than maximum allowable size value.
- ORA-01145: offline immediate disallowed unless media recovery enabled
-
Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode.
- ORA-01146: cannot start online backup - file string is already in backup
-
Cause: When starting an online backup it was noticed that an online backup was already started for one of the data files.
- ORA-01147: SYSTEM tablespace file string is offline
-
Cause: A file belonging to the SYSTEM tablespace has been marked offline by the DBA. The database cannot be started until all SYSTEM tablespace files are online and openable.
- ORA-01148: cannot refresh file size for datafile string
-
Cause: An operating system or device error occurred when retrieving the file's size. The device on which the file resides may have been offline.
- ORA-01149: cannot shutdown - file string has online backup set
-
Cause: An attempt to shutdown normally found that an online backup is still in progress.
- ORA-01150: cannot prevent writes - file string has online backup set
-
Cause: An attempt to make a tablespace read only or offline normal found that an online backup is still in progress. It will be necessary to write the file header to end the backup, but that would not be allowed if this command succeeded.
- ORA-01151: use media recovery to recover block, restore backup if needed
-
Cause: Error 1172 occurred.
- ORA-01152: file string was not restored from a sufficiently old backup
-
Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent. This file is still in the future of the last log applied. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery.
- ORA-01153: an incompatible media recovery is active
-
Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs
- ORA-01154: database busy. Open, close, mount, and dismount not allowed now
-
Cause: Some operation is in progress that expects the opened/mounted state of this instance to remain the same.
- ORA-01155: the database is being opened, closed, mounted or dismounted
-
Cause: The requested operation needs the instance to be in a particular state but the state is being changed.
- ORA-01156: recovery or flashback in progress may need access to files
-
Cause: Either media recovery, instance recovery, or flashback was in progress. The recovery or flashback in progress may need the files to which this operation is being applied.
- ORA-01157: cannot identify/lock data file string - see DBWR trace file
-
Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified.
- ORA-01158: database string already mounted
-
Cause: Another instance has a database by this name mounted.
- ORA-01159: file is not from same database as previous files - wrong database id
-
Cause: Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified.
- ORA-01160: file is not a string
-
Cause: The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated.
- ORA-01161: Database name string in the file header does not match string in the DATABASE clause.
-
Cause: The database name provided in the DATABASE clause did not match the database name found in the file header.
- ORA-01162: block size string in file header does not match configured block sizes
-
Cause: CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the INIT.ORA file.
- ORA-01163: SIZE clause indicates string (blocks), but should match header string
-
Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header.
- ORA-01164: MAXLOGFILES may not exceed string
-
Cause: MAXLOGFILES specified on the command line too large.
- ORA-01165: MAXDATAFILES may not exceed string
-
Cause: MAXDATAFILES specified on the command line too large.
- ORA-01166: file number string is larger than string (string)
-
Cause: File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES.
- ORA-01167: two files are the same file/group number or the same file
-
Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file spec. This message will also appear if the same control file appears more than once in the control_files parameter in the init.ora file. If this happens, check for additional error messages.
- ORA-01168: physical block size string does not match size string of other members
-
Cause: The file is located on a device with a different physical block size than the other members in the group
- ORA-01169: DATAFILE number 1 not found. Must be present
-
Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command.
- ORA-01170: file not found 'string'
-
Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the process for CREATE CONTROLFILE.
- ORA-01171: datafile string going offline due to error advancing checkpoint
-
Cause: The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block.
- ORA-01172: recovery of thread string stuck at block string of file string
-
Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.
- ORA-01173: data dictionary indicates missing data file from system tablespace
-
Cause: Either the database has been recovered to a point in time in the future of the control file or a datafile from the system tablespace was omitted from the create control file command previously issued.
- ORA-01174: DB_FILES is string buts needs to be string to be compatible
-
Cause: The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.
- ORA-01175: data dictionary has more than the string files allowed by the instance
-
Cause: The data dictionary is found to have more files than that which can be supported by this instance.
- ORA-01176: data dictionary has more than the string files allowed by the controlfile
-
Cause: After a CREATE CONTROLFILE, the data dictionary was found to have more data files than that supported by the control file.
- ORA-01177: data file does not match dictionary - probably old incarnation
-
Cause: When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.
- ORA-01178: file string created before last CREATE CONTROLFILE, cannot recreate
-
Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed at the last CREATE CONTROLFILE command. The information needed to recreate the file was lost with the control file that existed when the file was added to the database.
- ORA-01179: file string does not exist
-
Cause: During datafile recovery, a file was listed which was not part for the database.
- ORA-01180: can not create datafile 1
-
Cause: Attempting to create datafile 1 using ALTER DATABASE CREATE DATAFILE.
- ORA-01181: file string created before last known RESETLOGS, cannot recreate
-
Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed before the last known RESETLOGS.
- ORA-01182: cannot create database file string - file is in use or recovery
-
Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that is online in an open instance or is being recovered.
- ORA-01183: cannot mount database in SHARED mode
-
Cause: Some other instance has the database mounted exclusive.
- ORA-01184: logfile group string already exists
-
Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is already in use.
- ORA-01185: logfile group number string is invalid
-
Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is too large.
- ORA-01186: file string failed verification tests
-
Cause: The data file did not pass the checks to insure it is part of the database. See the accompanying error messages for the reason the verification failed.
- ORA-01187: cannot read from file string because it failed verification tests
-
Cause: The data file did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified.
- ORA-01188: The block size specified string does not match header block size string
-
Cause: The block size specified in the BLOCKSIZE clause of the CREATE CONTROLFILE statement does not equate to the block size recorded in the log file header.
- ORA-01189: file is from a different RESETLOGS than previous files
-
Cause: In a CREATE CONTROLFILE command either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS.
- ORA-01190: control file or data file string is from before the last RESETLOGS
-
Cause: Attempting to use a data file when the log reset information in the file does not match the control file. Either the data file or the control file is a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS.
- ORA-01191: file string is already offline - cannot do a normal offline
-
Cause: When attempting to do a normal tablespace offline it was discovered that one of the files in the tablespace was already offline.
- ORA-01192: must have at least one enabled thread
-
Cause: You must specify at least two logfiles from at least one thread at the create contolfile command line.
- ORA-01193: file string is not the same file seen at start of recovery
-
Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.
- ORA-01194: file string needs more recovery to be consistent
-
Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery.
- ORA-01195: online backup of file string needs more recovery to be consistent
-
Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file is an online backup which must be recovered to the time the backup ended.
- ORA-01196: file string is inconsistent due to a failed media recovery session
-
Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file.
- ORA-01197: thread string only contains one log
-
Cause: During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs.
- ORA-01198: must specify size for log file if RESETLOGS
-
Cause: File sizes must be given for all logfiles if doing a CREATE CONTROLFILE with the RESETLOGS option.
- ORA-01199: file string is not in online backup mode
-
Cause: Attempting to end an online backup for a file that is not in online backup.
- ORA-01200: actual file size of string is smaller than correct size of string blocks
-
Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated. Maybe it is the result of a half completed copy.
- ORA-01201: file string header failed to write correctly
-
Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made.
- ORA-01202: wrong incarnation of this file - wrong creation time
-
Cause: The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped.
- ORA-01203: wrong incarnation of this file - wrong creation SCN
-
Cause: The creation SCN in the file header is not the same as the creation SCN in the control file. This is probably a copy of a file that was dropped.
- ORA-01204: file number is string rather than string - wrong file
-
Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database.
- ORA-01205: not a data file - type number in header is string
-
Cause: The file type in the header is not correct for a data file. This is probably a log file or control file. If the type is not a small non-zero positive number then the header is corrupted.
- ORA-01206: file is not part of this database - wrong database id
-
Cause: The database ID in the file header does not match the database id in the control file. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected.
- ORA-01207: file is more recent than control file - old control file
-
Cause: The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.
- ORA-01208: data file is an old version - not accessing current version
-
Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.
- ORA-01209: data file is from before the last RESETLOGS
-
Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.
- ORA-01210: data file header is media corrupt
-
Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistancy of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database.
- ORA-01211: Oracle7 data file is not from migration to Oracle8
-
Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8.
- ORA-01212: MAXLOGMEMBERS may not exceed string
-
Cause: MAXLOGMEMBERS specified on the command line too large.
- ORA-01213: MAXINSTANCES may not exceed string
-
Cause: MAXINSTANCES specified on the command line too large.
- ORA-01214: MAXLOGHISTORY may not exceed string
-
Cause: MAXLOGHISTORY specified on the command line too large.
- ORA-01215: enabled thread string is missing after CREATE CONTROLFILE
-
Cause: A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database.
- ORA-01216: thread string is expected to be disabled after CREATE CONTROLFILE
-
Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread).
- ORA-01217: logfile member belongs to a different logfile group
-
Cause: A member of a multiple-member logfile group specified in a CREATE CONTROLFILE is not part of the same group as previous members.
- ORA-01218: logfile member is not from the same point-in-time
-
Cause: A member of a multiple-member logfile group is from a different point in time. One of the members specified may be an older (backup) copy of the log.
- ORA-01219: database or pluggable database not open: queries allowed on fixed tables or views only
-
Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database or pluggable database has been opened.
- ORA-01220: file based sort illegal before database is open
-
Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.
- ORA-01221: data file string is not the same file to a background process
-
Cause: When the database writer opens the data file, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.
- ORA-01222: MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
-
Cause: Attemping to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.
- ORA-01223: RESETLOGS must be specified to set a new database name
-
Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.
- ORA-01224: group number in header string does not match GROUP string
-
Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.
- ORA-01225: thread number string is greater than MAXINSTANCES string
-
Cause: The log is for a thread greater than the MAXINSTANCES argument.
- ORA-01226: file header of log member is inconsistent with other members
-
Cause: The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log.
- ORA-01227: log string is inconsistent with other logs
-
Cause: The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistancy. All log files listed in the command must be the current versions of the online logs.
- ORA-01228: SET DATABASE option required to install seed database
-
Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database.
- ORA-01229: data file string is inconsistent with logs
-
Cause: The data file in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs.
- ORA-01230: cannot make read only - file string is offline
-
Cause: An attempt to make a tablespace read only found that one of its files is offline.
- ORA-01231: cannot make read write - file string is offline
-
Cause: An attempt to make a tablespace read write found that one of its files is offline.
- ORA-01232: cannot start online backup - file string is being made read-only
-
Cause: An attempt to start an online backup found that one of the files is in transition to read-only mode.
- ORA-01233: file string is read only - cannot recover using backup control file
-
Cause: An attempt to do media recovery using a backup control file found that one of the files is marked read only. Read only files do not normally need to be recovered, but recovery with a backup control file must recover all online files.
- ORA-01234: cannot end backup of file string - file is in use or recovery
-
Cause: Attempted to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online.
- ORA-01235: END BACKUP failed for string file(s) and succeeded for string
-
Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.
- ORA-01236: Error string occurred during initialization of file header access
-
Cause: The indicated error occurred while doing initialization processing of file headers.
- ORA-01237: cannot extend datafile string
-
Cause: An operating system error occurred during the resize.
- ORA-01238: cannot shrink datafile string
-
Cause: An operating system error occurred during the resize.
- ORA-01239: database must be in ARCHIVELOG mode to use external cache
-
Cause: An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this can not be allowed.
- ORA-01240: too many data files to add in one command
-
Cause: The command specifies adding more data files than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large.
- ORA-01241: an external cache has died
-
Cause: The external cache may have been restarted.
- ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
-
Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.
- ORA-01243: system tablespace file suffered media failure
-
Cause: A system tablespace file was detected as inaccessible due to media failure.
- ORA-01244: unnamed datafile(s) added to control file by media recovery
-
Cause: Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files.
- ORA-01245: offline file string will be lost if RESETLOGS is done
-
Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option.
- ORA-01246: recovering files through TSPITR of tablespace string
-
Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery.
- ORA-01247: database recovery through TSPITR of tablespace string
-
Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done.
- ORA-01248: file string was created in the future of incomplete recovery
-
Cause: Attempting to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed.
- ORA-01249: archiving not allowed in a clone database
-
Cause: Attempting to archive an online redo log or enable archiving for a clone database.
- ORA-01250: Error string occurred during termination of file header access
-
Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a write error.
- ORA-01251: Unknown File Header Version read for file number string
-
Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file.
- ORA-01252: cannot prevent writes - file string in recovery manager backup
-
Cause: An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read-only, then the file header cannot be updated when the backup is complete.
- ORA-01253: cannot start online backup - file string in recovery manager backup
-
Cause: The specified file is being backed up by Recovery Manager.
- ORA-01254: cannot end online backup - file string in recovery manager backup
-
Cause: The specified file is being backed up by Recovery Manager.
- ORA-01255: cannot shutdown - file string in recovery manager backup
-
Cause: An attempt to shutdown normally found that a Recovery Manager backup is still in progress.
- ORA-01256: error in locking database file string
-
Cause: The file is in use by another database instance.
- ORA-01257: cannot reuse database file string, unknown file size
-
Cause: The size of the raw partion cannot be determined
- ORA-01258: unable to delete temporary file string
-
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not able to delete a temporary file in the database.
- ORA-01259: unable to delete datafile string
-
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace.
- ORA-01260: warning: END BACKUP succeeded but some files found not to be in backup mode
-
Cause: END BACKUP completed successfully for all files that were in online backup mode. However one or more modifiable files were found not to be in online backup mode. Backup of those files (if it was done) can be invalid and, if restored, can result in an inconsistent database.
- ORA-01261: Parameter string destination string cannot be translated
-
Cause: The value for the specified parameter contained a destination string that could not be translated.
- ORA-01262: Stat failed on a file destination directory
-
Cause: Unable to get information about an Oracle managed files destination directory.
- ORA-01263: Name given for file destination directory is invalid
-
Cause: The name given for an Oracle managed files destination does not correspond to a directory.
- ORA-01264: Unable to create string file name
-
Cause: Unable to create an Oracle managed file name.
- ORA-01265: Unable to delete string string
-
Cause: An error prevented the file from being deleted.
- ORA-01266: Unable to create unique file name
-
Cause: Unable to create a unique file name for an Oracle managed file. Oracle tried several names but each file name was already in use in the default destination directory for the file type.
- ORA-01267: Failure getting date/time
-
Cause: Could not get date/time when trying to create unique file name.
- ORA-01268: invalid TEMPFILE clause for alter of permanent TABLESPACE
-
Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a permanent tablespace.
- ORA-01269: Destination parameter string is too long
-
Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter was too long.
- ORA-01270: string operation is not allowed if STANDBY_PRESERVES_NAMES is true
-
Cause: An operation that renames or adds/drops a file was attempted at a standby database and STANDBY_PRESERVES_NAMES is true.
- ORA-01271: Unable to create new file name for file string
-
Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file.
- ORA-01272: REUSE only allowed when a file name is provided.
-
Cause: The REUSE parameter was specified in a command without a file name.
- ORA-01273: STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
-
Cause: Automated standby file management was disabled, so an added file
- ORA-01274: cannot add data file that was originally created as 'string'
-
Cause: The recovery failed to add the specified data file either because the recovery tried to create the specified data file but automated standby file management was disabled, or the recovery tried to look for the specified data file but the data file did not exist. In the former case, the recovery added a control file entry as 'UNNAMEDnnnnn'.
- ORA-01275: Operation string is not allowed if standby file management is automatic.
-
Cause: An operation that renames, adds, or drops a file was attempted at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO.
- ORA-01276: Cannot add file string. File has an Oracle Managed Files file name.
-
Cause: An attempt was made to add to the database a datafile, log file, control file, snapshot control file, backup control file, datafile copy, control file copy or backuppiece with an Oracle Managed Files file name.
- ORA-01277: file 'string' already exists
-
Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' command specified a file name which is already in use.
- ORA-01278: error creating file 'string'
-
Cause: An operating system error occurred while attempting to create a trace file specified in the command ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename'.
- ORA-01279: db_files too large
-
Cause: db_files has been set too high to be supported by the system.
- ORA-01280: Fatal LogMiner error.
-
Cause: An internal error occurred inside LogMiner.
- ORA-01281: SCN range specified is invalid
-
Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid.
- ORA-01282: date range specified is invalid
-
Cause: startTime may be greater than endTime. startTime or endTime may be greater than year 2110. startTime may be less than year 1988.
- ORA-01283: Options specified is invalid
-
Cause: The specified options parameter is invalid for the procedure.
- ORA-01284: file string cannot be opened
-
Cause: The file or directory may not exist or may be inaccessible. Pathname exceeds 256 characters.
- ORA-01285: error reading file string
-
Cause: The file or directory may not exist or is inaccessible.
- ORA-01286: start interval required
-
Cause: Options were supplied which require a starting time or starting SCN
- ORA-01287: file string is from a different database incarnation
-
Cause: The logfile is produced by a different incarnation of the database.
- ORA-01288: cannot apply this DDL to the Logminer Dictionary
-
Cause: A command that is not supported by Logminer was present in a logfile. Commands that change the character set of the database are not supported by Logminer. "ALTER DATABASE SET TIME_ZONE" is not supported by Logminer.
- ORA-01289: cannot add duplicate logfile string
-
Cause: The logfile specified has already been added to the list of logfiles.
- ORA-01290: cannot remove unlisted logfile string
-
Cause: The user attempted to remove a logfile that is not present in the list.
- ORA-01291: missing log file
-
Cause: Not all log files corresponding to the time or SCN range specified had been added to the LogMiner session.
- ORA-01292: LogMiner for upstream capture cannot find log file
-
Cause: A log file needed by LogMiner could not be found in v$archived_log.
- ORA-01293: mounted database required for specified LogMiner options
-
Cause: Options were specified which required the database to be mounted
- ORA-01294: error occurred while processing information in dictionary file string, possible corruption
-
Cause: The dictionary file is corrupt.
- ORA-01295: DB_ID mismatch between dictionary string and logfiles
-
Cause: The dictionary file is produced by a database that is different from that produced the logfiles.
- ORA-01296: character set mismatch between dictionary string and logfiles
-
Cause: The character set of the database that produced the dictionary file is different from the charatcter set of the database that produced the logfiles.
- ORA-01297: redo version mismatch between dictionary string and logfiles
-
Cause: The redo version of the database generating the dictionary is different from the one generating the logfiles.
- ORA-01298: conflicting dictionary option
-
Cause: More than one dictionary source was specified or DDL_DICT_TRACKING was specified with DICT_FROM_ONLINE_CATALOG.
- ORA-01299: dictionary string corresponds to a different database incarnation
-
Cause: The dictionary file was extracted from a different incarnation of the database.
- ORA-01300: writable database required for specified LogMiner options
-
Cause: Options were specified which required the database to be writable.
- ORA-01301: error writing to file during flat file build
-
Cause: Error writing to file during flat file build
- ORA-01302: dictionary build options missing or incorrect
-
Cause: Missing dictionary build options or incorrectly specified options
- ORA-01303: subordinate process error: string. Check alert and trace logs
-
Cause: A process subordinate to this Logminer process has exited with this error status.
- ORA-01304: subordinate process error. Check alert and trace logs
-
Cause: A process subordinate to this Logminer process has exited with an error condition.
- ORA-01305: incompatible database character set
-
Cause: The database character set of the mining database was not a superset of the source database character set.
- ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
-
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure.
- ORA-01307: no LogMiner session is currently active
-
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Otherwise, dbms_logmnr.end_logmnr() was called without a prior call to dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile()
- ORA-01308: dictionary directory is not set
-
Cause: The dictionary directory was not valid.
- ORA-01309: invalid session
-
Cause: The specified Logminer session ID or session handle is invalid.
- ORA-01310: requested return type not supported by the lcr_mine function
-
Cause: The return type requested by the user is not supported by lcr_mine"
- ORA-01311: Illegal invocation of the mine_value function
-
Cause: An attempt was made to use mine_value function on a column other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V$LOGMNR_CONTENTS fixed table/view.
- ORA-01312: Specified table/column does not exist
-
Cause: The table/column specified in the lcr_mine call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly.
- ORA-01313: LogMiner dictionary column type different from specified type
-
Cause: The return type specified for the column in lcr_mine call is different from the actual type of the column.
- ORA-01314: Name of the column to be mined should be a string literal
-
Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.
- ORA-01315: Log file has been added or removed during select
-
Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.
- ORA-01316: Already attached to a Logminer session
-
Cause: A Logminer attach session was issued while already attached to a Logminer session.
- ORA-01317: Not attached to a Logminer session
-
Cause: A command or procedure was issued which requires an attached Logminer session.
- ORA-01318: incompatible national character set
-
Cause: The national character set of the mining database was not a superset of the source database national character set.
- ORA-01319: Invalid Logminer session attribute
-
Cause: A session attribute was supplied which is invalid.
- ORA-01320: Invalid Logminer dictionar attribute
-
Cause: A Logminer dictionary attribute was supplied which is invalid.
- ORA-01321: No Logminer Dictionary for requested start SCN
-
Cause: The requested session start SCN is less than the SCN of any available Logminer Dictionary build. It is not possible to unwind a Logminer Dictionary to the requested start SCN.
- ORA-01322: No such table
-
Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().
- ORA-01323: Invalid state
-
Cause: A Logminer routine was called from the wrong state.
- ORA-01324: cannot add file string due to DB_ID mismatch
-
Cause: The logfile is produced by a different database than other logfiles already added to the list.
- ORA-01325: archive log mode must be enabled to build into the logstream
-
Cause: Database does not have archivelog mode enabled.
- ORA-01326: compatability of 9.0 or greater required to build into the logstream
-
Cause: Compatibility mode set to some value less than 9.0
- ORA-01327: failed to exclusively lock system dictionary as required by build
-
Cause: Other users are performing DDL operations.
- ORA-01328: only one build operation may occur at one time
-
Cause: Another processes is simultaneously attempting to run build();
- ORA-01329: unable to truncate required build table
-
Cause: The table may be missing, or locked by another user.
- ORA-01330: problem loading a required build table
-
- ORA-01331: general error while running build
-
- ORA-01332: internal Logminer Dictionary error
-
Cause: Unexpected error condition
- ORA-01333: failed to establish Logminer Dictionary
-
Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictiony. Or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary.
- ORA-01334: invalid or missing logminer dictionary processes context
-
Cause: Unexpected internal error condition
- ORA-01335: feature not yet implemented
-
- ORA-01336: specified dictionary file cannot be opened
-
Cause: The dictionary file or directory does not exist or is inaccessible.
- ORA-01337: log file has a different compatibility version
-
Cause: The logfile has a different compatibility version then the rest of the logfile in the session"
- ORA-01338: Other process is attached to LogMiner session
-
Cause: Can not do this when other process is attached to LogMiner session.
- ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary
-
Cause: Unexpected result while accessing system catalog metadata.
- ORA-01340: NLS error
-
Cause: Could not load NLS package.
- ORA-01341: LogMiner out-of-memory
-
Cause: The LogMiner session requires more system resources than is currently available.
- ORA-01342: LogMiner can not resume session due to inability of staging checkpointed data
-
Cause: Logmnr can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery.
- ORA-01343: LogMiner encountered corruption in the logstream
-
Cause: Log file is missing a range of scn values.
- ORA-01344: LogMiner coordinator already attached
-
Cause: A coordinator process is already attached to the specified logminer context.
- ORA-01345: Must be a LogMiner coordinator process
-
Cause: A LogMiner client attempted to perform a privileged operation.
- ORA-01346: Oracle LogMiner processed redo beyond primary reset log SCN string
-
Cause: Oracle LogMiner detected a new branch with reset log SCN information prior to redo already mined.
- ORA-01347: Supplemental log data no longer found
-
Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.
- ORA-01348: LogMiner testing event
-
- ORA-01349: LogMiner tracing event
-
- ORA-01350: must specify a tablespace name
-
Cause: Invocation failed to specify a valid tablespace
- ORA-01351: tablespace given for Logminer dictionary does not exist
-
Cause: The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
- ORA-01352: tablespace given for Logminer spill does not exist
-
Cause: The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
- ORA-01353: existing Logminer session
-
Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active.
- ORA-01354: Supplemental log data must be added to run this command
-
Cause: An attempt was made to perform an operation that required that supplemental log data be enabled.
- ORA-01355: logminer tablespace change in progress
-
Cause: The tables used by logminer are in the process of being moved to another tablespace.
- ORA-01356: active logminer sessions found
-
Cause: Logminer sessions are currently active.
- ORA-01357: LogMiner transaction queue is full
-
Cause: LogMiner ran out of space in the transaction queue.
- ORA-01358: LogMiner version is less than mined dictionary version
-
Cause: An attempt was made to mine a LogMiner dictionary from redo logs. The version of the Oracle database that created the logs was higher than the Oracle database version that attempted to mine the logs.
- ORA-01360: invalid token
-
- ORA-01361: global name mismatch
-
Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process.
- ORA-01362: Specified SQL_REDO_UNDO parameter is invalid
-
Cause: The specified input value for the parameter was not a valid number.
- ORA-01363: Specified COLUMN_NAME parameter is NULL
-
Cause: NULL was specified for input value of parameter.
- ORA-01364: waiting for branch at SCN string
-
Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. LogMiner reader is now waiting for logs from the new branch.
- ORA-01365: waiting for new branch registration
-
Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. The builder process is now waiting for logs from the new branch to be registered before continuing.
- ORA-01366: failed to find redo logs required for terminal apply
-
Cause: LogMiner failed to find all the expected log files required to complete the terminal apply, requested using the FINISH APPLY clause. During terminal apply, LogMiner does not wait for logs to be registered. It expects all logs between the starting point and the last log on any redo branch that it will or could mine through, to be present at the mining site.
- ORA-01370: Specified restart SCN is too old
-
Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.
- ORA-01371: Complete LogMiner dictionary not found
-
Cause: One or more log files containing the LogMiner dictionary was not found.
- ORA-01372: Insufficient processes for specified LogMiner operation
-
Cause: The number of processes requested by the caller can not be allocated
- ORA-01373: insufficient memory for staging persistent LogMiner session
-
Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.
- ORA-01374: _log_parallelism_max greater than 1 not supported in this release
-
Cause: LogMiner does not mine redo records generated with _log_parallelism_max set to a value greater than 1.
- ORA-01375: Corrupt logfile string recovered
-
Cause: A corrupt logfile has been recovered by RFS
- ORA-01376: cannot add file string due to unsupported redo compatibility setting
-
Cause: The redo compatibility setting of the log file was unsupported by LogMiner.
- ORA-01377: Invalid log file block size
-
Cause: An invalid value was specified in the BLOCKSIZE clause.
- ORA-01378: The logical block size (string) of file string is not compatible with the disk sector size (media sector size is string and host sector size is string)
-
Cause: One of the following occurred: (1) An attempt was made to create a file. (2) A file was moved to disks with different sector size.
- ORA-01379: LogMiner testing event
-
- ORA-01380: Instance string (thread string) has less than two string block size log files
-
Cause: One of the following occurred: (1) An attempt was made to switch to specified block size logs for all threads. (2) An attemp was made to open a thread.
- ORA-01381: Dropping log string would leave less than two log files with block size string for instance string (thread string)
-
Cause: The database was migrated to use a specified log block size. Dropping all the logs specified would leave fewer than the required two log files with the specified block size per enabled thread.
- ORA-01382: Thread string failed to open log file string. The log file's block size (string) is larger than the disk sector size (string)
-
Cause: Log file was created on bigger sector disks, and moved to smaller sector disks.
- ORA-01383: Thread string failed to open string block size log file 'string' on string sector native-mode disks
-
Cause: Log file was copied from smaller sector disks to larger sector native-mode disks.
- ORA-01397: file name too long to shrink without truncation
-
Cause: An attempt was made to automatically convert the control file created with maximum file name size value of 512 to 256. This could result in truncation of file names leading to loss of uniqueness among file names.
- ORA-01398: LogMiner public event
-
- ORA-01399: LogMiner public event
-
- ORA-01400: cannot insert NULL into (string)
-
Cause: An attempt was made to insert NULL into previously listed objects.
- ORA-01401: inserted value too large for column
-
Cause: The value inserted was too large for the given column.
- ORA-01402: view WITH CHECK OPTION where-clause violation
-
Cause: An INSERT or UPDATE statement was attempted on a view created with the CHECK OPTION. This would have resulted in the creation of a row that would not satisfy the view's WHERE clause.
- ORA-01403: no data found
-
Cause: No data was found from the objects.
- ORA-01404: ALTER COLUMN will make an index too large
-
Cause: Increasing the length of a column would cause the combined length of the columns specified in a previous CREATE INDEX statement to exceed the maximum index length (255). The total index length was computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields were calculated as a length of 7, character fields were calculated at their defined width, and numeric fields were length 22.
- ORA-01405: fetched column value is NULL
-
Cause: The INTO clause of a FETCH operation contained a NULL value, and no indicator was used. The column buffer in the program remained unchanged, and the cursor return code was +2. This was an error unless you are running Oracle with DBMS=6, emulating version 6, in which case it was only a warning.
- ORA-01406: fetched column value was truncated
-
Cause: The fetched column values were truncated.
- ORA-01407: cannot update (string) to NULL
-
Cause: An attempt was made to update a table column "USER"."TABLE"."COLUMN" with a NULL value. For example, if you enter: connect scott/tiger update table a (a1 number not null); insert into a values (null); Oracle returns: ORA-01407 cannot update ("SCOTT"."A"."A1") to NULL which means you cannot update the column "SCOTT"."A"."A1" to NULL.
- ORA-01408: such column list already indexed
-
Cause: A CREATE INDEX statement specified a column that was already indexed. A single column may be indexed only once. Additional indexes may be created on the column if it was used as a portion of a concatenated index, that was, if the index consists of multiple columns.
- ORA-01409: NOSORT option may not be used; rows are not in ascending order
-
Cause: Creation of index with NOSORT option when rows were not ascending. For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split accross two extents where the dba of the first block in the second extent is less than the dba of the last block in the first extent, then the create index nosort may fail.
- ORA-01410: invalid ROWID
-
Cause: A ROWID was entered incorrectly. ROWIDs must be entered as formatted hexadecimal strings using only numbers and the characters A through F. A typical ROWID format is '000001F8.0001.0006'.
- ORA-01411: cannot store the length of column in the indicator
-
Cause: Tried to fetch a column of size more than 64K and couldn't store the length of the column in the given indicator of size 2 bytes.
- ORA-01412: zero length not allowed for this datatype
-
Cause: The length for type 97 is 0
- ORA-01413: illegal value in packed decimal number buffer
-
Cause: The user buffer bound by the user as packed decimal number contained an illegal value.
- ORA-01414: invalid array length when trying to bind array
-
Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length.
- ORA-01415: too many distinct aggregate functions
-
Cause: The query contains more distinct aggregates than can be processed. The current limit is 255.
- ORA-01416: two tables cannot be outer-joined to each other
-
Cause: Two tables in a join operation specified an outer join with respect to each other. If an outer join was specified on one of the tables in a join condition, it may not be specified on the other table.
- ORA-01417: a table may be outer joined to at most one other table
-
Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed
- ORA-01418: specified index does not exist
-
Cause: An ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement specified the name of an index that did not exist. Only existing indexes can be altered, dropped, or validated. Existing indexes may be listed by querying the data dictionary.
- ORA-01419: datdts: illegal format code
-
Cause: An attempt was made to use an incorrect format.
- ORA-01420: datstd: illegal format code
-
Cause: An attempt was made to use an invalid format.
- ORA-01421: datrnd/dattrn: illegal precision specifier
-
Cause: An attempt was made to use an invalid precision specifier.
- ORA-01422: exact fetch returns more than requested number of rows
-
Cause: The number specified in exact fetch is less than the rows returned.
- ORA-01423: error encountered while checking for extra rows in exact fetch
-
Cause: An error was encountered during the execution of an exact fetch. This message will be followed by more descriptive messages.
- ORA-01424: missing or illegal character following the escape character
-
Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, '%', or '_'.
- ORA-01425: escape character must be character string of length 1
-
Cause: Given escape character for LIKE is not a character string of length 1.
- ORA-01426: numeric overflow
-
Cause: Evaluation of an value expression causes an overflow/underflow.
- ORA-01427: single-row subquery returns more than one row
-
Cause: The outer query must use one of the keywords ANY, ALL, IN, or NOT IN to specify values to compare because the subquery returned more than one row.
- ORA-01428: argument 'string' is out of range
-
Cause: An illegal value for a mathematical function argument was specified. For example: SELECT SQRT(-1) "Square Root" FROM DUAL;
- ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces
-
Cause: No overflow segment defined.
- ORA-01430: column being added already exists in table
-
Cause: An ALTER TABLE ADD statement specified the name of a column that was already in the table. All column names must be unique within a table.
- ORA-01431: internal inconsistency in GRANT command
-
Cause: An internal error occurred while attempting to execute a GRANT statement.
- ORA-01432: public synonym to be dropped does not exist
-
Cause: The synonym specified in DROP PUBLIC SYNONYM was not a valid public synonym. It may be a private synonym.
- ORA-01433: synonym to be created is already defined
-
Cause: A CREATE SYNONYM statement specified a synonym name that was the same as an existing synonym, table, view, or cluster. Synonyms may not have the same name as any other synonym, table, view, or cluster available to the user creating the synonym.
- ORA-01434: private synonym to be dropped does not exist
-
Cause: A DROP SYNONYM statement specified a synonym that did not exist. Existing synonym names may be listed by querying the data dictionary.
- ORA-01435: user does not exist
-
Cause: This message is caused by any reference to a non-existent user. For example, it occurs if a SELECT, GRANT, or REVOKE statement specifies a username that did not exist. Only a GRANT CONNECT statement may specify a new username. All other GRANT and REVOKE statements must specify existing usernames. If specified in a SELECT statement, usernames must already exist.
- ORA-01436: CONNECT BY loop in user data
-
Cause: The condition specified in a CONNECT BY clause caused a loop in the query, where the next record to be selected was a descendent of itself. When this happens, there could be no end to the query.
- ORA-01437: cannot have join with CONNECT BY
-
Cause: A join operation was specified with a CONNECT BY clause. If a CONNECT BY clause was used in a SELECT statement for a tree-structured query, only one table may be referenced in the query.
- ORA-01438: value larger than specified precision allowed for this column
-
Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.
- ORA-01439: column to be modified must be empty to change datatype
-
Cause: An ALTER TABLE MODIFY statement attempted to change the datatype of a column containing data. A column whose datatype was to be altered must contain only NULL values.
- ORA-01440: column to be modified must be empty to decrease precision or scale
-
Cause: An ALTER TABLE MODIFY statement attempted to decrease the scale or precision of a numeric column containing data. In order to decrease either of these values, the column must contain only NULL values. An attempt to increase the scale without also increasing the precision caused this message.
- ORA-01441: cannot decrease column length because some value is too big
-
Cause: An ALTER TABLE MODIFY statement attempted to decrease the size of a character field containing data. A column whose maximum size was decreased must contain only NULL values.
- ORA-01442: column to be modified to NOT NULL is already NOT NULL
-
Cause: An ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NOT NULL to NOT NULL.
- ORA-01443: internal inconsistency; illegal datatype in resultant view column
-
Cause: An internal error occurred in referencing a view.
- ORA-01444: internal inconsistency; internal datatype maps to invalid external type
-
Cause: This is an internal error message not normally issued.
- ORA-01445: cannot select ROWID from, or sample, a join view without a key-preserved table
-
Cause: A SELECT statement attempted to select ROWIDs from a view derived from a join operation. Because the rows selected in the view did not correspond to underlying physical records, no ROWIDs can be returned.
- ORA-01446: cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc.
-
Cause: A SELECT statement attempted to select ROWIDs from a view containing columns derived from functions or expressions. Because the rows selected in the view did not correspond to underlying physical records, no ROWIDs can be returned.
- ORA-01447: ALTER TABLE does not operate on clustered columns
-
Cause: An ALTER TABLE MODIFY statement specified a column used to cluster the table. Clustered columns may not be altered.
- ORA-01448: index must be dropped before changing to desired type
-
Cause: An ALTER TABLE MODIFY statement attempted to change an indexed character column to a LONG column. Columns with the datatype LONG may not be indexed, so the index must be dropped before the modification.
- ORA-01449: column contains NULL values; cannot alter to NOT NULL
-
Cause: An ALTER TABLE MODIFY statement attempted to change the definition of a column containing NULL values to NOT NULL. The column may not currently contain any NULL values if it was to be altered to NOT NULL.
- ORA-01450: maximum key length (string) exceeded
-
Cause: The combined length of all the columns specified in a CREATE INDEX statement exceeded the maximum index length. The maximum index length varies by operating system. The total index length was computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields have a length of 7, character fields have their defined length, and numeric fields have a length of 22. Numeric length = (precision/2) + 1. If negative, add +1.
- ORA-01451: column to be modified to NULL cannot be modified to NULL
-
Cause: the column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint.
- ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
-
Cause: A CREATE UNIQUE INDEX statement specified one or more columns that currently contained duplicate values. All values in the indexed columns must be unique by row to create a UNIQUE INDEX.
- ORA-01453: SET TRANSACTION must be first statement of transaction
-
Cause: self-evident
- ORA-01454: cannot convert column into numeric datatype
-
Cause: A non-numeric value could not be converted into a number value.
- ORA-01455: converting column overflows integer datatype
-
Cause: The converted form of the specified expression was too large for the specified datatype.
- ORA-01456: may not perform insert/delete/update operation inside a READ ONLY transaction
-
Cause: A non-DDL insert, delete, update or select for update operation was attempted.
- ORA-01457: converting column overflows decimal datatype
-
Cause: The converted form of the specified expression was too large for the specified type. The problem also occurred in COBOL programs when using COMP-3 in the picture clause, which was acceptable to the Pro*COBOL Precompiler and to COBOL but results in this error.
- ORA-01458: invalid length inside variable character string
-
Cause: An attempt was made to bind or define a variable character string with a buffer length less than the minimum requirement.
- ORA-01459: invalid length for variable character string
-
Cause: The buffer length was less than the minimum required or greater than its length at bind time minus two bytes.
- ORA-01460: unimplemented or unreasonable conversion requested
-
Cause: The requested format conversion was not supported.
- ORA-01461: can bind a LONG value only for insert into a LONG column
-
Cause: An attempt was made to insert a value from a LONG datatype into another datatype. This is not allowed.
- ORA-01462: cannot insert string literals longer than 4000 characters
-
Cause: The longest literal supported by Oracle consisted of 4000 characters.
- ORA-01463: cannot modify column datatype with current constraint(s)
-
Cause: An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa.
- ORA-01464: circular grant (granting to grant ancestor) of table or view
-
Cause: The user in the TO clause of the GRANT statement had already been GRANTed privileges on this table.
- ORA-01465: invalid hex number
-
Cause: In an UPDATE statement following a SELECT FOR UPDATE, part of the ROWID contained invalid characters. ROWID must be expressed in the proper and expected format for ROWID and within quotes.
- ORA-01466: unable to read data - table definition has changed
-
Cause: Query parsed after tbl (or index) change, and executed w/old snapshot
- ORA-01467: sort key too long
-
Cause: A DISTINCT, GROUP BY, ORDER BY, or SET operation requires a sort key longer than that supported by Oracle. Either too many columns or too many group functions were specified in the SELECT statement.
- ORA-01468: a predicate may reference only one outer-joined table
-
Cause: A predicate in the WHERE clause had two columns from different tables with "(+)".
- ORA-01469: PRIOR can only be followed by a column name
-
Cause: Attempting to specify "PRIOR something" where something is not a column name.
- ORA-01470: In-list iteration does not support mixed operators
-
Cause: Constants of different types are specified in an in-list.
- ORA-01471: cannot create a synonym with same name as object
-
Cause: An attempt was made to create a private synonym with the same name as the object to which it refers. This error typically occurred when a user attempts to create a private synonym with the same name as one of their objects.
- ORA-01472: cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc.
-
Cause: CONNECT BY could not be used on a view where there was not a correspondence between output rows and rows of the underlying table.
- ORA-01473: cannot have subqueries in CONNECT BY clause
-
Cause: Subqueries could not be used in a CONNECT BY clause.
- ORA-01474: cannot have START WITH or PRIOR without CONNECT BY
-
Cause: START WITH and PRIOR are meaningful only in connection with CONNECT BY.
- ORA-01475: must reparse cursor to change bind variable datatype
-
Cause: After executing a statement, an attempt was made to rebind a bind variable with a datatype different from that of the original bind.
- ORA-01476: divisor is equal to zero
-
Cause: An expression attempted to divide by zero.
- ORA-01477: user data area descriptor is too large
-
Cause: This is an internal error message not normally issued.
- ORA-01478: array bind may not include any LONG columns
-
Cause: User is performing an array bind with a bind variable whose maximum size is greater than 2000 bytes.
- ORA-01479: last character in the buffer is not Null
-
Cause: A bind variable of type 97 does not contain null at the last position
- ORA-01480: trailing null missing from STR bind value
-
Cause: A bind variable of type 5 (null-terminated string) does not contain the terminating null in its buffer.
- ORA-01481: invalid number format model
-
Cause: The user is attempting to either convert a number to a string via TO_CHAR or a string to a number via TO_NUMBER and has supplied an invalid number format model parameter.
- ORA-01482: unsupported character set
-
Cause: The character set used to perform the operation, such as the CONVERT function, is not a supported character set.
- ORA-01483: invalid length for DATE or NUMBER bind variable
-
Cause: A bind variable of type DATE or NUMBER is too long.
- ORA-01484: arrays can only be bound to PL/SQL statements
-
Cause: You tried to bind an array to a non-PL/SQL statement.
- ORA-01485: compile bind length different from execute bind length
-
Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length (given in the bind call). The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array.
- ORA-01486: size of array element is too large
-
Cause: You tried to bind a data value which was either too large for the datatype (for example, NUMBER) or was greater than 4000 bytes (for example, VARCHAR or LONG).
- ORA-01487: packed decimal number too large for supplied buffer
-
Cause: An impossible request for decimal to oracle number conversion was made
- ORA-01488: invalid nibble or byte in the input data
-
Cause: An impossible request for decimal to oracle number conversion was made
- ORA-01489: result of string concatenation is too long
-
Cause: String concatenation result is more than the maximum size.
- ORA-01490: invalid ANALYZE command
-
Cause: Incorrect syntax specified
- ORA-01491: CASCADE option not valid
-
Cause: The CASCADE option is only valid for tables or clusters.
- ORA-01492: LIST option not valid
-
Cause: The LIST option is only valid for tables or clusters.
- ORA-01493: invalid SAMPLE size specified
-
Cause: The specified SAMPLE size is out of range
- ORA-01494: invalid SIZE specified
-
Cause: The specified histogram SIZE value was out of range.
- ORA-01495: specified chain row table not found
-
Cause: The specified table either does not exist or user does not have the proper privleges.
- ORA-01496: specified chain row table form incorrect
-
Cause: The specified table does not have the proper field definitions.
- ORA-01497: illegal option for ANALYZE CLUSTER
-
Cause: The FOR COLUMNS column-list clause may not be used with ANALYZE CLUSTER.
- ORA-01498: block check failure - see trace file
-
Cause: An error occurred while checking a block with the ANALYZE command.
- ORA-01499: table/index cross reference failure - see trace file
-
Cause: An error occurred when validating an index or a table using the ANALYZE command. One or more entries did not point to the appropriate cross-reference.