{"id":2062,"date":"2016-08-11T13:39:58","date_gmt":"2016-08-11T10:39:58","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2062"},"modified":"2016-12-12T09:21:33","modified_gmt":"2016-12-12T06:21:33","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-01500-to-ora-01600","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-01500-to-ora-01600\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01500 to ORA-01600"},"content":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01500 to ORA-01600<\/strong><\/p>\n

\n
ORA-01500: failure in getting date\/time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During create database or alter tablespace, there was a failure in getting the date and time.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact your customer support representative.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01501: CREATE DATABASE failed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred during create database<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See accompanying errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01502: index ‘string<\/i>.string<\/i>‘ or partition of such index is in unusable state<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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<\/span><\/span><\/p>\n

Action:<\/b>\u00a0DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition<\/span><\/span><\/p>\n

\n
<\/a> ORA-01503: CREATE CONTROLFILE failed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred during CREATE CONTROLFILE<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See accompanying errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01504: database name ‘string<\/i>‘ does not match parameter db_name ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The name in a database create or mount does not match the name given in the INIT.ORA parameter db_name.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0correct or omit one of the two names.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01505: error in adding log files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During create or alter database, error(s) occurred when adding new log files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check error stack for detailed error information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01506: missing or illegal database name<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No db_name INIT.ORA aprameter was specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The database name must be given in the db_name INIT.ORA parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01507: database not mounted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A command was attempted that requires the database to be mounted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If 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.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-01508: cannot create database; error in file ‘string<\/i>‘ at line\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE DATABASE was unable to process the specified file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the offending line in the specified file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01509: specified name ‘string<\/i>‘ does not match actual ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database name specified in ALTER DATABASE does not match the name of the currently mounted database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the database name spelling or DISMOUNT the mounted database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01510: error in deleting log files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During ALTER DATABASE, an error occurred while dropping log files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for detailed error information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01511: error in renaming log\/data files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred during the ALTER DATABASE RENAME FILE command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for detailed error information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01512: error renaming log file\u00a0string<\/i>\u00a0– new file\u00a0string<\/i>\u00a0not found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to change a log file’s name in the control file failed because no file was found with the new name.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure that the log file has been properly renamed by the operating system and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01513: invalid current time returned by operating system<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operating system returned a time that was not between 1988 and 2121.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the time kept by the operating system.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01514: error in log specification: no such log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A log file name, or list of member names, did not correspond to an existing log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify an existing log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01515: error dropping log group\u00a0string<\/i>: no such log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER DATABASE is attempting to drop a log file which is not known to the database control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the name of an existing log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01516: nonexistent log file, data file, or temporary file “string<\/i>” in the current container<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use ALTER DATABASE to rename a log file, data file, or temporary file; or to change attributes of a data file or temporary file (for example, resize, autoextend, online or offline); or to re-create or move a data file. The attempt failed because the specified file is not known to the database’s control file or the current container or is not of a type supported by the request.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01517: log member: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Used to print member names<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See top level error for information<\/span><\/span><\/p>\n

\n
<\/a> ORA-01518: CREATE DATABASE must specify more than one log file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Only one log file was specified in the CREATE DATABASE statement.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify at least two log files.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01519: error while processing file ‘string<\/i>‘ near line\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE DATABASE encountered a problem while processing specified file. The specified file is bad.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry your system installation procedure or contact your customer support representative.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01520: number of data files to add (string<\/i>) exceeds limit of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE TABLESPACE statement specifies more files than is permitted for this database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use fewer files or re-create the database with a larger value of MAXDATAFILES.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01521: error in adding data files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During CREATE or ALTER TABLESPACE, an error was detected while adding data files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for detailed error information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01522: file ‘string<\/i>‘ to be renamed does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the correct file name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01523: cannot rename data file to ‘string<\/i>‘ – file already part of database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Rename the file to a name not already being used as part of the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01524: cannot create data file as ‘string<\/i>‘ – file already part of database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create the file as a name not already being used as part of the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01525: error in renaming data files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred when renaming files as part of ALTER TABLESPACE.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01526: error in opening file ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry your system installation procedure or contact your customer support representative.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01527: error while reading file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry your system installation procedure or contact your customer support representative.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01528: EOF while processing SQL statement<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE DATABASE unexpectedly hit EOF while reading the specified file. The sql.bsq file is bad.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry your system installation procedure or contact your customer support representative.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01529: error closing file ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE DATABASE was not able to close the specified file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry your system installation procedure or contact your customer support representative.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01530: a database already mounted by the instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If you wish to mount the database, shutdown the instance and then startup the instance and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01531: a database already open by the instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If you wish to open a new database on the instance, first shutdown the instance and then startup the instance and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01532: cannot create database; instance being started elsewhere<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During CREATE DATABASE, another user appears to be simultaneously altering the instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure no one else is simultaneously altering the instance. If no one is, contact your customer support representative; otherwise, retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01533: cannot rename file ‘string<\/i>‘; file does not belong to tablespace<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the correct file name or the correct tablespace name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01534: rollback segment ‘string<\/i>‘ doesn’t exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the correct rollback segment name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01535: rollback segment ‘string<\/i>‘ already exists or given name has prefix _SYSSMU<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Specified rollback segment already exists or given name starts with _SYSSMU.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a different name. Note that _SYSSMU is an illegal prefix to an RBU segment.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01536: space quota exceeded for tablespace ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either drop unnecessary objects in the tablespace to reclaim space or have a privileged user increase the quota on this tablespace for the segment owner.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01537: cannot add file ‘string<\/i>‘ – file already part of database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During CREATE or ALTER TABLESPACE, a file being added is already part of the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a different file name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01538: failed to acquire any rollback segment<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to acquire any rollback segment during startup in shared mode<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Startup in exclusive mode to create one more public segment or specify available private segments in the INIT.ORA parameter rollback_segments_required, then startup in shared mode<\/span><\/span><\/p>\n

\n
<\/a> ORA-01539: tablespace ‘string<\/i>‘ is not online<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to either make a tablespace read-only or offline because it is not online. A tblespace must be online before it can become read-only or offline normal.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read-only.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01540: tablespace ‘string<\/i>‘ is not offline<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to bring a tablespace online because it is not offline<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the status of the tablespace<\/span><\/span><\/p>\n

\n
<\/a> ORA-01541: system tablespace cannot be brought offline; shut down if necessary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to bring system tablespace offline<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown if necessary to do recovery<\/span><\/span><\/p>\n

\n
<\/a> ORA-01542: tablespace ‘string<\/i>‘ is offline, cannot allocate space in it<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to allocate space in an offline tablespace<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Bring the tablespace online or create the object in other tablespace<\/span><\/span><\/p>\n

\n
<\/a> ORA-01543: tablespace ‘string<\/i>‘ already exists<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to create a tablespace which already exists<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a different name for the new tablespace<\/span><\/span><\/p>\n

\n
<\/a> ORA-01544: cannot drop system rollback segment<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to drop system rollback segment<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-01545: rollback segment ‘string<\/i>‘ specified not available<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Either: 1) An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. 2) An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. 3) An attempt was made to drop a rollback segment that is currently online. 4) An attempt was made to alter a rollback segment that is currently online to use unlimited extents. 5) An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either: 1) Make the rollback segment available; for example, bring an offline tablespace online. 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment. 3) Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions. 4) Same as 3). 5) Remove the name from the _corrupted_rollback_segments parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01546: tablespace contains active rollback segment ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to make a tablespace that contains active rollback segment(s) offline or read-only<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown instances that use the active rollback segments in the tablespace and then make the tablespace offline or read-only<\/span><\/span><\/p>\n

\n
<\/a> ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01548: active rollback segment ‘string<\/i>‘ found, terminate dropping tablespace<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to drop a tablespace that contains active rollback segment(s)<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown instances that use the active rollback segments in the tablespace and then drop the tablespace<\/span><\/span><\/p>\n

\n
<\/a> ORA-01549: tablespace not empty, use INCLUDING CONTENTS option<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to drop a non-empty tablespace<\/span><\/span><\/p>\n

Action:<\/b>\u00a0To drop all the objects in the tablespace, use the INCLUDING CONTENTS option<\/span><\/span><\/p>\n

\n
<\/a> ORA-01550: cannot drop system tablespace<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to drop system tablespace<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-01551: extended rollback segment, pinned blocks released<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Doing recursive extent of rollback segment, trapped internally by the system<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-01552: cannot use system rollback segment for non-system tablespace ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create one or more private\/public segment(s), shutdown and then startup again. May need to modify the INIT.ORA parameter rollback_segments to acquire private rollback segment. If this is a clone database being used for tablspace point in time recovery then this operation is not allowed. If the non-system tablespace has AUTO segment space management, then create an undo tablespace.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01553: MAXEXTENTS must be no smaller than the\u00a0string<\/i>\u00a0extents currently allocated<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The number of extents allocated is greater than the MAXEXTENTS specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a larger MAXEXTENTS value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01554: transaction concurrency limit reached reason:string<\/i>\u00a0params:string<\/i>,\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Too many concurrent transactions<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01555: snapshot too old: rollback segment number\u00a0string<\/i>\u00a0with name “string<\/i>” too small<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0rollback records needed by a reader for consistent read are overwritten by other writers<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If in Automatic Undo Management mode, increase undo_retention setting. Otherwise, use larger rollback segments<\/span><\/span><\/p>\n

\n
<\/a> ORA-01556: MINEXTENTS for rollback segment must be greater than 1<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Specified MINEXTENTS of less than 2 for rollback segment<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify larger MINEXTENTS<\/span><\/span><\/p>\n

\n
<\/a> ORA-01557: rollback segment extents must be at least\u00a0string<\/i>\u00a0blocks<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Specified extent of less than minimum size for rollback segment<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify larger extents<\/span><\/span><\/p>\n

\n
<\/a> ORA-01558: out of transaction ID’s in rollback segment\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0All the available transaction id’s have been used<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction id’s.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01559: MAXEXTENTS for rollback segment must be greater than 1<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Specified MAXEXTENTS of less than 2 for rollback segment<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify larger MAXEXTENTS<\/span><\/span><\/p>\n

\n
<\/a> ORA-01560: LIKE pattern contains partial or illegal character<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0like pattern is not formed correctly<\/span><\/span><\/p>\n

Action:<\/b>\u00a0make sure like pattern is specified correctly<\/span><\/span><\/p>\n

\n
<\/a> ORA-01561: failed to remove all objects in the tablespace specified<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to remove all objects when dropping a tablespace<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the drop tablespace until all objects are dropped<\/span><\/span><\/p>\n

\n
<\/a> ORA-01562: failed to extend rollback segment number\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failure occurred when trying to extend rollback segment<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintainence. Use the alter rollback segment offline command to take the rollback segment offline.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01563: rollback segment is PUBLIC, need to use the keyword PUBLIC<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Did not use the keyword PUBLIC to identified public rollback segment<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the keyword PUBLIC when identifying public rollback segment<\/span><\/span><\/p>\n

\n
<\/a> ORA-01564: rollback segment is not PUBLIC<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The rollback segment segment identified is not public<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not use the keyword PUBLIC when identifying private rollback segment<\/span><\/span><\/p>\n

\n
<\/a> ORA-01565: error in identifying file ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred while trying to identify a file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for detailed information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01566: file specified more than once in ALTER DATABASE<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The list of files supplied to the command contained at least one duplicate.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove the duplicate file specification and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01567: dropping log\u00a0string<\/i>\u00a0would leave less than 2 log files for instance\u00a0string<\/i>\u00a0(thread\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Dropping all the logs specified would leave fewer than the required two log files per enabled thread.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01568: cannot set space quota on PUBLIC<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Trying to set space quota on a tablespace for PUBLIC.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If trying to grant system-wide or tablespace-wide space priviledges to all users, use GRANT RESOURCE [ON\u00a0tablespace<\/i>] TO PUBLIC.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01569: data file too small for system dictionary tables<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The datafile specified during creation of the database is too small to hold the system dictionary tables.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Recreate the database by specifying a larger file or more files.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01570: MINEXTENTS must be no larger than the\u00a0string<\/i>\u00a0extents currently allocated<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The number of extents allocated is smaller than the MINEXTENTS specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a smaller MINEXTENTS value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01571: redo version\u00a0string<\/i>\u00a0incompatible with ORACLE version\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01572: rollback segment ‘string<\/i>‘ cannot be brought online,\u00a0string<\/i>\u00a0extents exceeded<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Drop and recreate the rollback segment.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01573: shutting down instance, no further change allowed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some process tries to make changes while the db is being shutdown<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-01574: maximum number of concurrent transactions exceeded<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0the limit on the number of concurrent transactions has been hit<\/span><\/span><\/p>\n

Action:<\/b>\u00a0shutdown the system, increase the INIT.ORA parameter ‘transactions’ , and then restart the system.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01575: timeout waiting for space management resource<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0failed to acquire necessary resource to do space management.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01576: The instance\u00a0string<\/i>\u00a0is not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The thread associated with instance is not enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Enable the thread associated with the instance using ALTER DATABASE ENABLE INSTANCE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01577: cannot add log file ‘string<\/i>‘ – file already part of database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During CREATE or ALTER DATABASE, a file being added is already part of the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a different file name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01578: ORACLE data block corrupted (file #\u00a0string<\/i>, block #\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The data block indicated was corrupt. This was a physical corruption, also called a media corruption. The cause is unknown but is most likely external to the database. If ORA-26040 is also signaled, the corruption is due to NOLOGGING or UNRECOVERABLE operations.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The general method to repair a media corrupt block is to restore a backup and recover the backup. For databases in ARCHIVELOG mode, use block media recovery or media recovery. In some situations, you can also drop the segment and re-create it. For example, you can drop an index and re-create the index.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01579: write error occurred during recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A write error occurred during recovery<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Consult trace files for the nature of the write error, and correct error.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01580: error creating control backup file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operating system error occurred while attempting to create a control file backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for more detailed information<\/span><\/span><\/p>\n

\n
<\/a> ORA-01581: attempt to use rollback segment (string<\/i>) new extent (string<\/i>) which is being allocated<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent which has not been completely allocated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The rollback segment extending will be rollbacked by the system, no more extension will be possible untill the next extent is freed up by rolling back or committing other transactions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01582: unable to open control file for backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operating system error occurred while attempting to open a control file for backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for more detailed information<\/span><\/span><\/p>\n

\n
<\/a> ORA-01583: unable to get block size of control file to be backed up<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operating system error occurred while attempting to get the block size of a control file for backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for more detailed information<\/span><\/span><\/p>\n

\n
<\/a> ORA-01584: unable to get file size of control file to be backed up<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operating system error occurred while attempting to get the file size of a control file for backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for more detailed information<\/span><\/span><\/p>\n

\n
<\/a> ORA-01585: error identifying backup file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operating system error occurred when attempting to identify the file to be used for control file backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the error stack for more detailed information<\/span><\/span><\/p>\n

\n
<\/a> ORA-01586: database must be mounted EXCLUSIVE and not open for this operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempting to DROP DATABASE when the database is not mounted EXCLUSIVE.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mount the database in EXCLUSIVE mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01587: error during control file backup file copy<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01588: must use RESETLOGS option for database open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup, or a FLASHBACK DATABASE was done.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the RESETLOGS option when opening the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01589: must use RESETLOGS or NORESETLOGS option for database open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the appropriate option.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01590: number of segment free list (string<\/i>) exceeds maximum of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0storage parameter FREELIST GROUPS is too large.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reduce storage parameters FREELIST GROUPS<\/span><\/span><\/p>\n

\n
<\/a> ORA-01591: lock held by in-doubt distributed transaction\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Trying to access resource that is locked by a dead two-phase commit transaction that is in prepared state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0DBA should query the pending_trans$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, DBA should contact DBA at commit point if known or end user for correct outcome, or use heuristic default if given to issue a heuristic commit or abort command to finalize the local portion of the distributed transaction.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01592: error converting Version 7 rollback segment (string<\/i>) to Oracle 8 format<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Look at the accompanying internal error; Version 7 database may not have shutdown cleanly.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Investigate the internal error; may have to reload the Version 7 Investigate the internal error; may have to reload the Version 7 database (from backup) and shutdown the database cleanly.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01593: rollback segment optimal size (string<\/i>\u00a0blks) is smaller than the computed initial size (string<\/i>\u00a0blks)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a larger OPTIMAL size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01594: attempt to wrap into rollback segment (string<\/i>) extent (string<\/i>) which is being freed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and\/or too many extents to free<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The rollback segment shrinking will be rollbacked by the system; increase the optimal size of the rollback segment.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01595: error freeing extent (string<\/i>) of rollback segment (string<\/i>))<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some error occurred while freeing inactive rollback segment extents.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Investigate the accompanying error.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01596: cannot specify system in\u00a0string<\/i>\u00a0parameter<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The system rollback segment is specified in the INIT.ORA parameter referred to in the error message<\/span><\/span><\/p>\n

Action:<\/b>\u00a0change the INIT.ORA parameter<\/span><\/span><\/p>\n

\n
<\/a> ORA-01597: cannot alter system rollback segment online or offline<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Tried to online or offline the system rollback segment<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-01598: rollback segment ‘string<\/i>‘ is not online<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Could have been taken offline before by DBA or cleaned up by SMON.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the status of rollback segment in undo$ or dba_rollback_segs to make sure the rollback segment is actually online.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01599: failed to acquire rollback segment (string<\/i>), cache space is full<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0the amount statically allocated is not enough based on max_rollback_segments parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0For now take another rollback segment offline or increase the parameter max_rollback_segments<\/span><\/span><\/p>\n

\n
<\/a> ORA-01600: at most one “string<\/i>” in clause “string<\/i>” of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The INIT.ORA parameter was mis-specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the INIT.ORA parameter and restart the instance.<\/span><\/span><\/p>\n

\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01500 to ORA-01600 ORA-01500: failure in getting date\/time Cause:\u00a0During create database or alter tablespace, there was a failure in getting the date and time. Action:\u00a0Contact your customer support representative. ORA-01501: CREATE DATABASE failed Cause:\u00a0An error occurred during create database Action:\u00a0See accompanying errors. ORA-01502: index ‘string.string‘ or…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[54],"class_list":["post-2062","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-xg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2062","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=2062"}],"version-history":[{"count":2,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2062\/revisions"}],"predecessor-version":[{"id":2103,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2062\/revisions\/2103"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2062"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}