ORA-01531: a database already open by the instance

ORA-01531: a database already open by the instance

Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database.

Action: If you wish to open a new database on the instance, first shutdown the instance and then startup the instance and retry the operation.

ORA-01530: a database already mounted by the instance

ORA-01530: a database already mounted by the instance

Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance in which a database is or has previously been mounted.

Action: If you wish to mount the database, shutdown the instance and then startup the instance and retry the operation.

ORA-01529: error closing file string

ORA-01529: error closing file string

Cause: CREATE DATABASE was not able to close the specified file.

Action: Retry your system installation procedure or contact your customer support representative.

ORA-01528: EOF while processing SQL statement

ORA-01528: EOF while processing SQL statement

Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file. The sql.bsq file is bad.

Action: Retry your system installation procedure or contact your customer support representative.

ORA-01527: error while reading file

ORA-01527: error while reading file

Cause: CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error.

Action: Retry your system installation procedure or contact your customer support representative.

ORA-01526: error in opening file string

ORA-01526: error in opening file string

Cause: CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error.

Action: Retry your system installation procedure or contact your customer support representative.

ORA-01525: error in renaming data files

ORA-01525: error in renaming data files

Cause: An error occurred when renaming files as part of ALTER TABLESPACE.

Action: Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack.

ORA-01524: cannot create data file as string - file already part of database

ORA-01524: cannot create data file as string - file already part of database

Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.

Action: Create the file as a name not already being used as part of the database.

ORA-01523: cannot rename data file to string - file already part of database

ORA-01523: cannot rename data file to string - file already part of database

Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.

Action: Rename the file to a name not already being used as part of the database.

ORA-01522: file string to be renamed does not exist

ORA-01522: file string to be renamed does not exist

Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.

Action: Specify the correct file name.

ORA-01521: error in adding data files

ORA-01521: error in adding data files

Cause: During CREATE or ALTER TABLESPACE, an error was detected while adding data files.

Action: Check the error stack for detailed error information.

ORA-01520: number of data files to add (string) exceeds limit of string

ORA-01520: number of data files to add (string) exceeds limit of string

Cause: CREATE TABLESPACE statement specifies more files than is permitted for this database.

Action: Use fewer files or re-create the database with a larger value of MAXDATAFILES.

ORA-01519: error while processing file string near line string

ORA-01519: error while processing file string near line string

Cause: CREATE DATABASE encountered a problem while processing specified file. The specified file is bad.

Action: Retry your system installation procedure or contact your customer support representative.

ORA-01518: CREATE DATABASE must specify more than one log file

ORA-01518: CREATE DATABASE must specify more than one log file

Cause: Only one log file was specified in the CREATE DATABASE statement.

Action: Specify at least two log files.

ORA-01517: log member: string

ORA-01517: log member: string

Cause: Used to print member names

Action: See top level error for information

ORA-01516: nonexistent log file, datafile, or tempfile string

ORA-01516: nonexistent log file, datafile, or tempfile string

Cause: An attempt was made to use ALTER DATABASE to rename a log file, datafile, or tempfile; or to change attributes of a datafile or tempfile (e.g., resize, autoextend, online or offline, etc.); or to re-create a datafile. The attempt failed because the specified file is not known to the database s control file or is not of a type supported by the request.

Action: Specify the name or number of an existing file of the correct type, as appropriate. Check the relevant V$ table for a list of possible files.

ORA-01515: error dropping log group string: no such log

ORA-01515: error dropping log group string: no such log

Cause: ALTER DATABASE is attempting to drop a log file which is not known to the database control file.

Action: Specify the name of an existing log file.

ORA-01514: error in log specification: no such log

ORA-01514: error in log specification: no such log

Cause: A log file name, or list of member names, did not correspond to an existing log.

Action: Specify an existing log file.

ORA-01513: invalid current time returned by operating system

ORA-01513: invalid current time returned by operating system

Cause: The operating system returned a time that was not between 1988 and 2121.

Action: Correct the time kept by the operating system.

ORA-01512: error renaming log file string - new file string not found

ORA-01512: error renaming log file string - new file string not found

Cause: An attempt to change a log file s name in the control file failed because no file was found with the new name.

Action: Make sure that the log file has been properly renamed by the operating system and retry.

ORA-01511: error in renaming log or data files

ORA-01511: error in renaming log or data files

Cause: An error occurred during the ALTER DATABASE RENAME FILE command.

Action: Check the error stack for detailed error information.

ORA-01510: error in deleting log files

ORA-01510: error in deleting log files

Cause: During ALTER DATABASE, an error occurred while dropping log files.

Action: Check the error stack for detailed error information.

ORA-01509: specified name string does not match actual string

ORA-01509: specified name string does not match actual string

Cause: The database name specified in ALTER DATABASE does not match the name of the currently mounted database.

Action: Correct the database name spelling or DISMOUNT the mounted database.

ORA-01508: cannot create database; error in file string at line string

ORA-01508: cannot create database; error in file string at line string

Cause: CREATE DATABASE was unable to process the specified file.

Action: Check the offending line in the specified file.

ORA-01507: database not mounted

ORA-01507: database not mounted

Cause: A command was attempted that requires the database to be mounted.

Action: If you are using the ALTER DATABASE statement via the SQLDBA startup command, specify the MOUNT option to startup; else if you are directly doing an ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to ALTER DATABASE. If you are doing a backup or copy, you must first mount the desired database. If you are doing a FLASHBACK DATABASE, you must first mount the desired database.

ORA-01506: missing or illegal database name

ORA-01506: missing or illegal database name

Cause: No db_name INIT.ORA aprameter was specified.

Action: The database name must be given in the db_name INIT.ORA parameter.

ORA-01505: error in adding log files

ORA-01505: error in adding log files

Cause: During create or alter database, error(s) occurred when adding new log files.

Action: Check error stack for detailed error information.

ORA-01504: database name string does not match parameter db_name string

ORA-01504: database name string does not match parameter db_name string

Cause: The name in a database create or mount does not match the name given in the INIT.ORA parameter db_name.

Action: correct or omit one of the two names.

ORA-01503: CREATE CONTROLFILE failed

ORA-01503: CREATE CONTROLFILE failed

Cause: An error occurred during CREATE CONTROLFILE

Action: See accompanying errors.

ORA-01502: index string.string or partition of such index is in unusable state

ORA-01502: index string.string or partition of such index is in unusable state

Cause: An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation

Action: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition

ORA-01501: CREATE DATABASE failed

ORA-01501: CREATE DATABASE failed

Cause: An error occurred during create database

Action: See accompanying errors.

ORA-01497: illegal option for ANALYZE CLUSTER

ORA-01497: illegal option for ANALYZE CLUSTER

Cause: The FOR COLUMNS lamp;lt;lamp;nbsp;column-listlamp;gt; clause may not be used with ANALYZE CLUSTER.

Action: Retry with a legal syntax. RA-01500: failure in getting date or time Cause: During create database or alter tablespace, there was a failure in getting the date and time. Action: Contact your customer support representative.

ORA-01496: specified chain row table form incorrect

ORA-01496: specified chain row table form incorrect

Cause: The specified table does not have the proper field definitions.

Action: Specify the correct table to use.

ORA-01495: specified chain row table not found

ORA-01495: specified chain row table not found

Cause: The specified table either does not exist or user does not have the proper privleges.

Action: Specify the correct table to use.

ORA-01494: invalid SIZE specified

ORA-01494: invalid SIZE specified

Cause: The specified histogram SIZE value was out of range.

Action: Specify a value within the proper range.

ORA-01493: invalid SAMPLE size specified

ORA-01493: invalid SAMPLE size specified

Cause: The specified SAMPLE size is out of range

Action: Specify a value within the proper range.

ORA-01492: LIST option not valid

ORA-01492: LIST option not valid

Cause: The LIST option is only valid for tables or clusters.

Action: Do not specify LIST

ORA-01491: CASCADE option not valid

ORA-01491: CASCADE option not valid

Cause: The CASCADE option is only valid for tables or clusters.

Action: Do not specify CASCADE

ORA-01490: invalid ANALYZE command

ORA-01490: invalid ANALYZE command

Cause: Incorrect syntax specified

Action: Retry the command

ORA-01489: result of string concatenation is too long

ORA-01489: result of string concatenation is too long

Cause: String concatenation result is more than the maximum size.

Action: Make sure that the result is less than the maximum size.

ORA-01488: invalid nibble or byte in the input data

ORA-01488: invalid nibble or byte in the input data

Cause: An impossible request for decimal to oracle number conversion was made

Action: This conversion cannot be performed

ORA-01487: packed decimal number too large for supplied buffer

ORA-01487: packed decimal number too large for supplied buffer

Cause: An impossible request for decimal to oracle number conversion was made

Action: This conversion cannot be performed

ORA-01486: size of array element is too large

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

Action: none

ORA-01485: compile bind length different from execute bind length

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.

Action: none

ORA-01484: arrays can only be bound to PL or SQL statements

ORA-01484: arrays can only be bound to PL or SQL statements

Cause: You tried to bind an array to a non-PL or SQL statement.

Action: none

ORA-01483: invalid length for DATE or NUMBER bind variable

ORA-01483: invalid length for DATE or NUMBER bind variable

Cause: A bind variable of type DATE or NUMBER is too long.

Action: Consult your manual for the maximum allowable length.

ORA-01482: unsupported character set

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.

Action: Use one of the supported character sets.

ORA-01481: invalid number format model

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.

Action: Consult your manual.

ORA-01480: trailing null missing from STR bind value

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.

Action: Terminate the string with a null character

ORA-01479: last character in the buffer is not Null

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

Action: Make the last character null

ORA-01478: array bind may not include any LONG columns

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.

Action: Such bind variables cannot participate in array binds. Use an ordinary bind operation instead.

ORA-01470: In-list iteration does not support mixed operators

ORA-01470: In-list iteration does not support mixed operators

Cause: Constants of different types are specified in an in-list.

Action: Use constants of same type for in-lists.

ORA-01469: PRIOR can only be followed by a column name

ORA-01469: PRIOR can only be followed by a column name

Cause: Attempting to specify PRIOR lamp;lt;lamp;nbsp;somethinglamp;gt; where lamp;lt;lamp;nbsp;somethinglamp;gt; is not a column name.

Action: Only a column name can follow PRIOR. Replace with a column name.

ORA-01466: unable to read data - table definition has changed

ORA-01466: unable to read data - table definition has changed

Cause: Query parsed after tbl (or index) change, and executed w or old snapshot

Action: commit (or rollback) transaction, and re-execute

ORA-01463: cannot modify column datatype with current constraint(s)

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.

Action: Remove the constraint(s) or do not perform the offending operation.

ORA-01456: may not perform insert or delete or update operation inside a READ ONLY transaction

ORA-01456: may not perform insert or delete or update operation inside a READ ONLY transaction

Cause: A non-DDL insert or delete or update or select for update operation was attempted

Action: commit (or rollback) transaction, and re-execute

ORA-01453: SET TRANSACTION must be first statement of transaction

ORA-01453: SET TRANSACTION must be first statement of transaction

Cause: self-evident

Action: commit (or rollback) transaction, and re-execute

ORA-01451: column to be modified to NULL cannot be modified to NULL

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.

Action: if a primary key or check constraint is enforcing the NOT NULL constraint, then drop that constraint.

ORA-01438: value larger than specified precision allowed for this column

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.

Action: Enter a value that complies with the numeric column s precision, or use the MODIFY option with the ALTER TABLE command to expand the precision.

ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces

ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces

Cause: No overflow segment defined.

Action: Add overflow segment.