{"id":2044,"date":"2016-08-03T11:09:11","date_gmt":"2016-08-03T08:09:11","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2044"},"modified":"2016-12-12T09:31:16","modified_gmt":"2016-12-12T06:31:16","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-00200-to-ora-00300","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-00200-to-ora-00300\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00200 to ORA-00300"},"content":{"rendered":"

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

\n
ORA-00200: control file could not be created<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0It was not possible to create the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00201: control file version\u00a0string<\/i>\u00a0incompatible with ORACLE version\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file was created by incompatible software.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00202: control file: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This message reports the name file involved in other messages.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See associated error messages for a description of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00203: using the wrong control files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that the correct control files were specified.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00204: error in reading (block\u00a0string<\/i>, # blocks\u00a0string<\/i>) of control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A disk I\/O failure was detected on reading the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00205: error in identifying control file, check alert log for more info<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The system could not find a control file of the specified name and size.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that ALL control files are online and that they are the same files that the system created at cold start time.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00206: error in writing (block\u00a0string<\/i>, # blocks\u00a0string<\/i>) of control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A disk I\/O failure was detected on writing the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00207: control files are not for the same database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that the control file is for the correct database and is not an old version.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-00208: number of control file names exceeds limit of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use more control files than Oracle supports.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00209: control file blocksize mismatch, check alert log for more info<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Look at the alert log for more information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00210: cannot open the specified control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Cannot open the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check to make sure the control file exists and is not locked by some other program.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00211: control file does not match previous control files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A control file was specified that belongs to another database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find and install the correct control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00212: block size\u00a0string<\/i>\u00a0below minimum required size of\u00a0string<\/i>\u00a0bytes<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The block size specified was too small. Space for the system overhead is required.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a larger block size and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00213: cannot reuse control file; old file size\u00a0string<\/i>,\u00a0string<\/i>\u00a0required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0To reuse a control file, it must be the same size as the one previously used.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00214: control file ‘string<\/i>‘ version\u00a0string<\/i>\u00a0inconsistent with file ‘string<\/i>‘ version\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An inconsistent set of control files, datafiles\/logfiles, and redo files was used.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a consistant set of control files, datafiles\/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00215: must be at least one control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No control file is specified or the control file specified does not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify at least one valid control file and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00216: control file could not be resized for migration from 8.0.2<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00217: control file could not be resized for new record types<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00218: block size\u00a0string<\/i>\u00a0of control file ‘string<\/i>‘ does not match DB_BLOCK_SIZE (string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00219: required control file size (string<\/i>\u00a0logical blocks) exceeds maximum allowable size (string<\/i>\u00a0logical blocks)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00220: control file not mounted by first instance, check alert log for more info<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find and install the correct control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00221: error on write to control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred when writing to one or more of the control files.<\/span><\/span><\/p>\n

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

\n
<\/a> ORA-00222: operation would reuse name of a currently mounted control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation with a different filename.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00223: convert file is invalid or incorrect version<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00224: control file resize attempted with illegal record type (string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16).<\/span><\/span><\/p>\n

\n
<\/a> ORA-00225: expected size\u00a0string<\/i>\u00a0of control file differs from actual size\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore a good copy of the control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00226: operation disallowed while alternate control file open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.<\/span><\/span><\/p>\n

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

\n
<\/a> ORA-00227: corrupt block detected in control file: (block\u00a0string<\/i>, # blocks\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A block header corruption or checksum error was detected on reading the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00228: length of alternate control file name exceeds maximum of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation with a shorter filename.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00229: operation disallowed: already hold snapshot control file enqueue<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00230: operation disallowed: snapshot control file enqueue unavailable<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00231: snapshot control file has not been named<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a name for the snapshot control file by calling cfileSetSnapshotName.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Call cfileMakeAndUseSnapshot again (or for the first time).<\/span><\/span><\/p>\n

\n
<\/a> ORA-00233: copy control file is corrupt or unreadable<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00234: error in identifying or opening snapshot or copy control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00235: control file read without a lock inconsistent due to concurrent update<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Concurrent update activity on a control file caused a process to read inconsistent information from the control file without a lock.<\/span><\/span><\/p>\n

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

\n
<\/a> ORA-00236: snapshot operation disallowed: mounted control file is a backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mount a current control file and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00237: snapshot operation disallowed: control file newly created<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mount a current control file and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00238: operation would reuse a filename that is part of the database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation with a different filename.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00239: timeout waiting for control file enqueue: held by ‘string<\/i>‘ for more than\u00a0string<\/i>\u00a0seconds<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified process waited the maximum allowed time for the control file enqueue.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restart the blocking instance indicated in the incident trace file or reboot the blocking node.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00240: control file enqueue held for more than\u00a0string<\/i>\u00a0seconds<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The current process did not release the control file enqueue within the maximum allowed time.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reissue any commands that failed and contact Oracle Support Services with the incident information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00241: operation disallowed: control file is not yet checked against data dictionary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Either the control file was recently created by using CREATE CONTROLFILE, an incomplete recovery was done, or some previous operations require the control file to be re-checked against the data dictionary.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut down and restart the database or the pluggable database so that the check is performed, and then retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00242: maximum allowed filename records used up in control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to create a new filename record entry in the control file because the maximum allowed filename records have been allocated and are in use.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Free up controlfile filename section entries by dropping unwanted tablespaces\/datafiles\/redofiles.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00243: failed to expand control file filename section by\u00a0string<\/i>\u00a0records<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to expand control file filename section. See alert log for more details.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation after increasing disk space for controlfile expansion.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00244: concurrent control file backup operation in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to create a control file backup because concurrent control file backup operation was in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry backup creation later.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00245: control file backup failed; in Oracle RAC, target might not be on shared storage<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failed to create a control file backup because some process signaled an error during backup creation. This is likely caused by the backup target (i.e., RMAN snapshot controlfile) being on a local file system so it could not be accessed by other instances. It can also be caused by other I\/O errors to the backup target. Any process of any instance that starts a read\/write control file transaction must have access to the backup control file during backup creation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check whether RMAN snapshot controlfile is on shared storage. Also, check alert files of all instances for further information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00246: control file backup failed; error accessing backup target<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to create a control file backup failed because some process signaled an I\/O error when accessing the backup target.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check alert and trace files for further information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00250: archiver not started<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to stop automatic archiving, but the archiver process was not running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00252: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0is empty, cannot archive<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However it is possible that instance death during a log switch left the log empty.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Empty logs do not need to be archived. Do not attempt to archive the redo log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00253: character limit\u00a0string<\/i>\u00a0exceeded by archive destination string\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00254: error in archive control string ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the archive string used to make sure it refers to a valid online device.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00255: error archiving log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, sequence #\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred during archiving.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00256: cannot translate archive destination string\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00257: Archiver error. Connect AS SYSDBA only until resolved.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is that the destination device is out of space to store the redo log file. Another possible cause is that a destination marked as MANDATORY has failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the alert log and trace files for detailed error information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00258: manual archiving in NOARCHIVELOG mode must identify log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or filename.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify log by filename, by group number or by thread and sequence number.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00259: log\u00a0string<\/i>\u00a0of open instance\u00a0string<\/i>\u00a0(thread\u00a0string<\/i>) is the current log, cannot archive<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00260: cannot find online log sequence\u00a0string<\/i>\u00a0for thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00261: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0is being archived or modified<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the current operation to complete and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00262: current log\u00a0string<\/i>\u00a0of closed thread\u00a0string<\/i>\u00a0cannot switch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00263: there are no logs that need archiving for thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00264: no recovery required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to perform media recovery on files that do not \/\/ need any type of recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00265: instance recovery required, cannot set ARCHIVELOG mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00266: name of archived log file needed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During media recovery, the name of an archived redo log file was requested, but no name was entered.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mount the correct redo log file and enter its name when it is requested.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00267: name of archived log file not needed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During media recovery, the name of an archived redo log file was entered, but no name was requested.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Continue media recovery, but do not enter a new log name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00268: specified log file does not exist ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The given redo log file does not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the spelling and capitalization of the filename and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00269: specified log file is part of thread\u00a0string<\/i>\u00a0not\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The given redo log file is not part of the given thread<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00270: error creating archive log\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error was encountered when either creating or opening the destination file for archiving.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that the archive destination is valid and that there is sufficient space on the destination device.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00271: there are no logs that need archiving<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00272: error writing archive log\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An I\/O error occurred while archiving a redo log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00273: media recovery of direct load data that was not logged<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00274: illegal recovery option\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An illegal option was specified for a recovery command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the syntax and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00275: media recovery has already been started<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to start a second media recovery operation in the same session.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Complete or cancel the first media recovery session or start another session to perform media recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00276: CHANGE keyword specified but no change number given<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The CHANGE keyword was specified on the command line, but no change number was given.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the command using a valid change number after the CHANGE keyword.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00277: illegal option to the UNTIL recovery flag\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the UNTIL keyword.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the syntax.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00278: log file ‘string<\/i>‘ no longer needed for this recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified redo log file is no longer needed for the current recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00279: change\u00a0string<\/i>\u00a0generated at\u00a0string<\/i>\u00a0needed for thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The requested log is required to proceed with recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Please supply the requested log with “ALTER DATABASE RECOVER LOGFILE <file_name>” or cancel recovery with “ALTER DATABASE RECOVER CANCEL”.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00280: change\u00a0string<\/i>\u00a0for thread\u00a0string<\/i>\u00a0is in sequence #string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This message helps to locate the redo log file with the specified change number requested by other messages.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the information provided in this message to specify the required archived redo log files for other errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00281: media recovery may not be performed using dispatcher<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Connect to the instance via a dedicated server process to perform media recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00282: UPI\u00a0string<\/i>\u00a0call not supported, use ALTER DATABASE RECOVER<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The given UPI call is no longer supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the ALTER DATABASE RECOVER command for all recovery actions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00283: recovery session canceled due to errors<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error during recovery was determined to be fatal enough to end the current recovery session.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0More specific messages will accompany this message. Refer to the other messages for the appropriate action.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00284: recovery session still in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error during recovery was determined to be minor enough to allow the current recovery session to continue.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0More specific messages will accompany this message. Refer to the other messages for the appropriate action.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00285: TIME not given as a string constant<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0TIME was not followed by a string constant for the time.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Enter the time enclosed in single quotation marks.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00286: no members available, or no member contains valid data<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0None of the members of a redo log file group are available, or the available members do not contain complete data.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If a member is temporarily offline, attempt to make it available. Make sure that the correct filenames are being used, especially if the redo log file is being accessed from a remote location.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00287: specified change number\u00a0string<\/i>\u00a0not found in thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The given change number does not appear in any of the online redo logs for the given thread.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00288: to continue recovery type ALTER DATABASE RECOVER CONTINUE<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00289: suggestion :\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Consider using this filename for the next log needed for recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00290: operating system archival error occurred. See error below<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0While attempting to archive to a redo log file, the server encountered an unexpected operating system error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00291: numeric value required for PARALLEL option<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-enter the command with a numeric argument specifying the degree of parallelism desired.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00292: parallel recovery feature not installed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A parallel recovery was requested when the parallel recovery option is not installed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00293: control file out of sync with redo log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The redo log file and control file are out of sync because a non-current controle file was specified when the instance was started.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00294: invalid archivelog format specifier ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted following the % symbol are s, S, t, and T.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the initialization file and re-start the instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00295: datafile\/tempfile number\u00a0string<\/i>\u00a0is invalid, must be between 1 and\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An invalid file number was specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a valid datafile or tempfile number and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00296: maximum number of files (string<\/i>) exceeded for RECOVER DATAFILE LIST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than recovery manager needs to recover to satisfy the user’s RECOVER command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-start the instance with a higher value for DB_FILES.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The RECOVER DATAFILE START command was issued, but no RECOVER DATAFILE LIST commands had been issued. This only happens when doing recovery with Recovery Manager, and is an internal error in Recovery Manager, because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START.<\/span><\/span><\/p>\n

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

\n
<\/a> ORA-00298: Missing or invalid attribute value<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the syntax and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00299: must use file-level media recovery on data file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file does not contain an entry for this file, so block media recovery cannot be done.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the data file and perform file-level media recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00300: illegal redo log block size\u00a0string<\/i>\u00a0specified – exceeds limit of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified block size of the redo log is greater than the maximum block size for the operating system.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create the redo log on a device with a smaller block size<\/span><\/span><\/p>\n

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

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00200 to ORA-00300 ORA-00200: control file could not be created Cause:\u00a0It was not possible to create the control file. Action:\u00a0Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again. ORA-00201: control file version\u00a0string\u00a0incompatible with ORACLE version\u00a0string…<\/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-2044","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-wY","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2044","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=2044"}],"version-history":[{"count":2,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2044\/revisions"}],"predecessor-version":[{"id":2113,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2044\/revisions\/2113"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2044"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2044"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2044"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}