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

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

\n
ORA-01100: database already mounted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A database is already mounted in this instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01101: database being created currently mounted by some other instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some other instance has the database of same name currently mounted and you are trying to create it.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either change the database name or shutdown the other instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01102: cannot mount database in EXCLUSIVE mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some other instance has the database mounted exclusive or shared.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown other instance or mount in a compatible mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01103: database name ‘string<\/i>‘ in control file is not ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database name in the control file does not match your database name.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either find the correct control file or change your database name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01104: number of control files (string<\/i>) does not equal\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The number of control files used by this instance disagrees with the number of control files in an existing instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check to make sure that all control files are listed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01105: mount is incompatible with mounts by other instances<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

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

\n
<\/a> ORA-01106: database must be closed before dismounting<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Obvious<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01107: database must be mounted for media recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to perform media recovery was made but the database is not mounted.<\/span><\/span><\/p>\n

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

\n
<\/a> ORA-01108: file\u00a0string<\/i>\u00a0is in backup or media recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Complete or cancel the media recovery session or backup.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-01109: database not open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Open the database and try the command again<\/span><\/span><\/p>\n

\n
<\/a> ORA-01110: data file\u00a0string<\/i>: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0See associated error message.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01111: name for data file\u00a0string<\/i>\u00a0is unknown – rename to correct file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Rename the MISSING file to the name of the real file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01112: media recovery not started<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to continue media recovery is being made but media recovery was not started.<\/span><\/span><\/p>\n

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

\n
<\/a> ORA-01113: file\u00a0string<\/i>\u00a0needs media recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to online or open a database with a file that is in need of media recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0First apply media recovery to the file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01114: IO error writing block to file\u00a0string<\/i>\u00a0(block #\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Restore access to the device or remove unnecessary files to free up space.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01115: IO error reading block from file\u00a0string<\/i>\u00a0(block #\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Device on which the file resides is probably offline<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore access to the device<\/span><\/span><\/p>\n

\n
<\/a> ORA-01116: error in opening database file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Usually the file is not accessible.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the database file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01117: adding file ‘string<\/i>‘ with illegal block size:\u00a0string<\/i>; limit is\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to add a database file with a block size that is greater than the maximum block size allowed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the DDL command with a smaller block size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01118: cannot add any more database files: limit of\u00a0string<\/i>\u00a0exceeded<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0There is no more room in the control file for adding database files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Resize the control file or drop other tablespaces.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01119: error in creating database file ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Usually due to not having enough space on the device.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01120: cannot remove online database file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempting to drop a datafile when it is online<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Take file offline before dropping.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01121: cannot rename database file\u00a0string<\/i>\u00a0– file is in use or recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempted to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Close database in all instances and end all recovery sessions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01122: database file\u00a0string<\/i>\u00a0failed verification check<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The information in this file is inconsistent with information from the control file. See accompanying message for reason.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make certain that the db files and control files are the correct files for this database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01123: cannot start online backup; media recovery not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to start backup of an on-line tablespace failed because media recovery is not enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Enable media recovery and retry this operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01124: cannot recover data file\u00a0string<\/i>\u00a0– file is in use or recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Do not do media recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01125: cannot disable media recovery – file\u00a0string<\/i>\u00a0has online backup set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to disable media recovery found that an online backup is still in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0End the backup of the offending tablespace and retry this command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01126: database must be mounted in this instance and not open in any instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Obvious<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01127: database name ‘string<\/i>‘ exceeds size limit of\u00a0string<\/i>\u00a0characters<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Obvious<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01128: cannot start online backup – file\u00a0string<\/i>\u00a0is offline<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to start an online backup found that one of the files is offline.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Bring the offending files online and retry this command or do a cold backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01129: user’s default or temporary tablespace does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The user’s default or temporary tablespace was dropped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reassign the default or temporary tablespace.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01130: database file version\u00a0string<\/i>\u00a0incompatible with ORACLE version\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01131: DB_FILES system parameter value\u00a0string<\/i>\u00a0exceeds limit of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01132: length of database file name ‘string<\/i>‘ exceeds limit of\u00a0string<\/i>\u00a0characters<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01133: length of log file name ‘string<\/i>‘ exceeds limit of\u00a0string<\/i>\u00a0characters<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01134: database mounted exclusive by another instance<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01135: file\u00a0string<\/i>\u00a0accessed for DML\/query is offline<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempted to access a data file that is offline<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Bring the data file back online<\/span><\/span><\/p>\n

\n
<\/a> ORA-01136: specified size of file\u00a0string<\/i>\u00a0(string<\/i>\u00a0blocks) is less than original size of\u00a0string<\/i>\u00a0blocks<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller the the size needed<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create the file with a larger size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01137: data file\u00a0string<\/i>\u00a0is still in the middle of going offline<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Wait a bit and try to online the file again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01138: database must either be open in this instance or not at all<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The requested operation can not be done when the database is mounted but not open in this instance, and another instance has the database open.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Execute the operation in an open instance, open the datbase in this instance, or close the database in the other instances.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01139: RESETLOGS option only valid after an incomplete database recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the ALTER DATABASE OPEN without specifying RESETLOGS<\/span><\/span><\/p>\n

\n
<\/a> ORA-01140: cannot end online backup – all files are offline or readonly<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0All the files were found to be offline or readonly when attempting to end an online backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None. Online backup does not need to be ended for this tablespace.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01141: error renaming data file\u00a0string<\/i>\u00a0– new file ‘string<\/i>‘ not found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to change a data 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 data file has been properly renamed by the operating system and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01142: cannot end online backup – none of the files are in backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0None of the files were found to be in online backup when attempting to end an online backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None. Online backup does not need to be ended for this tablespace.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01143: cannot disable media recovery – file\u00a0string<\/i>\u00a0needs media recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Recover the offending file or drop the tablespace it belongs to and retry this command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01144: File size (string<\/i>\u00a0blocks) exceeds maximum of\u00a0string<\/i>\u00a0blocks<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Specified file size is larger than maximum allowable size value.<\/span><\/span><\/p>\n

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

\n
<\/a> ORA-01145: offline immediate disallowed unless media recovery enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER TABLESPACE … OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE … OFFLINE is only allowed if database is in ARCHIVELOG mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Take tablespace offline normally or shutdown abort. Reconsider your backup strategy. You could do this if you were archiving your logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01146: cannot start online backup – file\u00a0string<\/i>\u00a0is already in backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When starting an online backup it was noticed that an online backup was already started for one of the data files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0End the first backup before beginning another.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01147: SYSTEM tablespace file\u00a0string<\/i>\u00a0is offline<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Bring the file online.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01148: cannot refresh file size for datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operating system or device error occurred when retrieving the file’s size. The device on which the file resides may have been offline.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore access to the device.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01149: cannot shutdown – file\u00a0string<\/i>\u00a0has online backup set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to shutdown normally found that an online backup is still in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0End the backup of the offending tablespace and retry this command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01150: cannot prevent writes – file\u00a0string<\/i>\u00a0has online backup set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0End the backup of the offending tablespace and retry this command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01151: use media recovery to recover block, restore backup if needed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Error 1172 occurred.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is additional information for error 1172.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01152: file\u00a0string<\/i>\u00a0was not restored from a sufficiently old backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Either apply more logs until the database is consistent or restore the database file from an older backup and repeat recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01153: an incompatible media recovery is active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Complete or cancel the other media recovery session or RMAN backup<\/span><\/span><\/p>\n

\n
<\/a> ORA-01154: database busy. Open, close, mount, and dismount not allowed now<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some operation is in progress that expects the opened\/mounted state of this instance to remain the same.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the operation to complete then retry. If attempting to do a shutdown, SHUTDOWN ABORT will work. If this is a shutdown of a standby database that is operating in NO DATA LOSS mode, you must shutdown the primary database first.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01155: the database is being opened, closed, mounted or dismounted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The requested operation needs the instance to be in a particular state but the state is being changed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the open, close, mount, or dismount to complete then retry the operation. If necessary, a SHUTDOWN ABORT will always work.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01156: recovery or flashback in progress may need access to files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Wait for recovery or flashback to complete.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01157: cannot identify\/lock data file\u00a0string<\/i>\u00a0– see DBWR trace file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01158: database\u00a0string<\/i>\u00a0already mounted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Another instance has a database by this name mounted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find which instance is still running. Perhaps you have not lost the control files after all.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01159: file is not from same database as previous files – wrong database id<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Please double check the list of files provided to the CREATE<\/span><\/span><\/p>\n

\n
<\/a> ORA-01160: file is not a\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Please double check the mentioned file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01161: Database name\u00a0string<\/i>\u00a0in the file header does not match\u00a0string<\/i>\u00a0in the DATABASE clause.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database name provided in the DATABASE clause did not match the database name found in the file header.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure consistency of database names. Use the SET DATABASE clause if you are renaming the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01162: block size\u00a0string<\/i>\u00a0in file header does not match configured block sizes<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the INIT.ORA file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Configure the appropriate cache for this block size using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01163: SIZE clause indicates\u00a0string<\/i>\u00a0(blocks), but should match header\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Specify the correct filename and size ( in bytes ).<\/span><\/span><\/p>\n

\n
<\/a> ORA-01164: MAXLOGFILES may not exceed\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0MAXLOGFILES specified on the command line too large.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Resubmit the command with a smaller MAXLOGFILES<\/span><\/span><\/p>\n

\n
<\/a> ORA-01165: MAXDATAFILES may not exceed\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0MAXDATAFILES specified on the command line too large.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Resubmit the command with a smaller MAXDATAFILES<\/span><\/span><\/p>\n

\n
<\/a> ORA-01166: file number\u00a0string<\/i>\u00a0is larger than\u00a0string<\/i>\u00a0(string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the maximum specified on the command line.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01167: two files are the same file\/group number or the same file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate control file, check the control_files parameter in the init.ora file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01168: physical block size\u00a0string<\/i>\u00a0does not match size\u00a0string<\/i>\u00a0of other members<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The file is located on a device with a different physical block size than the other members in the group<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a physical device with matching block size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01169: DATAFILE number 1 not found. Must be present<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Datafile number 1 was not specified in a CREATE CONTROLFILE command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Locate datafile number 1 and resubmit the CREATE CONTROLFILE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01170: file not found ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the process for CREATE CONTROLFILE.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The file specified probably contains a typing error. Double check command and the existance of all files and then resubmit.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01171: datafile\u00a0string<\/i>\u00a0going offline due to error advancing checkpoint<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01172: recovery of thread\u00a0string<\/i>\u00a0stuck at block\u00a0string<\/i>\u00a0of file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem then restore the file from a backup and recover it.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01173: data dictionary indicates missing data file from system tablespace<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0For the former problem you need to recover the database from a more recent control file. For the latter problem, simply recreate the control file checking to be sure that you include all the datafiles in the system tablespace.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01174: DB_FILES is\u00a0string<\/i>\u00a0buts needs to be\u00a0string<\/i>\u00a0to be compatible<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Change the value of the DB_FILES parameter to be compatible<\/span><\/span><\/p>\n

\n
<\/a> ORA-01175: data dictionary has more than the\u00a0string<\/i>\u00a0files allowed by the instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The data dictionary is found to have more files than that which can be supported by this instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown the instance and restart with a larger number of db_files<\/span><\/span><\/p>\n

\n
<\/a> ORA-01176: data dictionary has more than the\u00a0string<\/i>\u00a0files allowed by the controlfile<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0After a CREATE CONTROLFILE, the data dictionary was found to have more data files than that supported by the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-create the control file with a larger MAXDATAFILES.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01177: data file does not match dictionary – probably old incarnation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Do a CREATE CONTROLFILE with the correct file or none at all.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01178: file\u00a0string<\/i>\u00a0created before last CREATE CONTROLFILE, cannot recreate<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01179: file\u00a0string<\/i>\u00a0does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During datafile recovery, a file was listed which was not part for the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Recheck the datafile name. Remember to use double quotes at the SQLDBA command line and remember that the file name is translated in the environment of the SQLDBA.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01180: can not create datafile 1<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempting to create datafile 1 using ALTER DATABASE CREATE DATAFILE.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Recover file from a backup or recreate database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01181: file\u00a0string<\/i>\u00a0created before last known RESETLOGS, cannot recreate<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed before the last known RESETLOGS.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01182: cannot create database file\u00a0string<\/i>\u00a0– file is in use or recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that is online in an open instance or is being recovered.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Close database in all instances and end all recovery sessions<\/span><\/span><\/p>\n

\n
<\/a> ORA-01183: cannot mount database in SHARED mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some other instance has the database mounted exclusive.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown other instance then mount shared.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01184: logfile group\u00a0string<\/i>\u00a0already exists<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is already in use.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a different logfile number, or let the database choose an unused value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01185: logfile group number\u00a0string<\/i>\u00a0is invalid<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is too large.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a correct logfile number.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01186: file\u00a0string<\/i>\u00a0failed verification tests<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01187: cannot read from file\u00a0string<\/i>\u00a0because it failed verification tests<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The data file did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01188: The block size specified\u00a0string<\/i>\u00a0does not match header block size\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Specify the correct block size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01189: file is from a different RESETLOGS than previous files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consistent with the rest of the datafiles and resubmit the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01190: control file or data file\u00a0string<\/i>\u00a0is from before the last RESETLOGS<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Restore file from a more recent backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01191: file\u00a0string<\/i>\u00a0is already offline – cannot do a normal offline<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When attempting to do a normal tablespace offline it was discovered that one of the files in the tablespace was already offline.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either bring the datafile online first, or use another tablespace offline option.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01192: must have at least one enabled thread<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0You must specify at least two logfiles from at least one thread at the create contolfile command line.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find the missing logfiles and resubmit the command with the newly found logfiles included in the command line.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01193: file\u00a0string<\/i>\u00a0is not the same file seen at start of recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Ensure the correct file is available, then retry recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01194: file\u00a0string<\/i>\u00a0needs more recovery to be consistent<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01195: online backup of file\u00a0string<\/i>\u00a0needs more recovery to be consistent<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Either apply more logs until the file is consistent or restore the database files from an older backup and repeat recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01196: file\u00a0string<\/i>\u00a0is inconsistent due to a failed media recovery session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Either apply more logs until the file is consistent or restore the backup again and repeat recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01197: thread\u00a0string<\/i>\u00a0only contains one log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01198: must specify size for log file if RESETLOGS<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0File sizes must be given for all logfiles if doing a CREATE CONTROLFILE with the RESETLOGS option.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Resubmit the command with the appropriate logfile size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01199: file\u00a0string<\/i>\u00a0is not in online backup mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempting to end an online backup for a file that is not in online backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not enter command since it is not needed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01200: actual file size of\u00a0string<\/i>\u00a0is smaller than correct size of\u00a0string<\/i>\u00a0blocks<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

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

Action:<\/b>\u00a0Restore a good copy of the data file and do recovery as needed.<\/span><\/span><\/p>\n

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

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01100 to ORA-01200 ORA-01100: database already mounted Cause:\u00a0A database is already mounted in this instance. Action:\u00a0n\/a ORA-01101: database being created currently mounted by some other instance Cause:\u00a0Some other instance has the database of same name currently mounted and you are trying to create it. Action:\u00a0Either change…<\/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-2054","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-x8","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2054","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=2054"}],"version-history":[{"count":2,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2054\/revisions"}],"predecessor-version":[{"id":2108,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2054\/revisions\/2108"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2054"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2054"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2054"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}