{"id":1933,"date":"2016-04-29T10:20:46","date_gmt":"2016-04-29T07:20:46","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1933"},"modified":"2016-10-26T10:22:28","modified_gmt":"2016-10-26T07:22:28","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-16000-to-ora-16100","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-16000-to-ora-16100\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-16000 to ORA-16100"},"content":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-16000 to ORA-16100<\/strong><\/p>\n

\n
ORA-16000: database open for read-only access<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database was opened for read-only access. Attempts to modify the database using DML or DDL statements generate this error.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0In order to modify the database, it must first be shut down and reopened for read\/write access.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16001: database already open for read-only access by another instance<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database has been opened for read-only access by another instance, and cannot be opened for read\/write access by this instance.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0This instance must be opened for read\/write access, or all other instances must first be shut down and reopened for read-only access.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16002: database already open for read\/write access by another instance<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database has been opened for read\/write access by another instance, and cannot be opened for read-only access by this instance.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0This instance must be opened for read-only access, or all other instances must first be shut down and reopened for read\/write access.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16003: standby database is restricted to read-only access<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to open a physical standby database in read\/write mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Reissue the ALTER DATABASE OPEN specifying READ ONLY.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16004: backup database required recovery<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database could not be opened for read-only access by this instance because it requires recovery.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Perform the necessary recovery and reopen for read-only access.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16005: database requires recovery<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database requires recovery, and therefore cannot be opened for read-only access by this instance.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Perform the necessary recovery and reopen for read-only access.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16007: invalid backup control file checkpoint<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database could not be opened for read-only access because its control file did not contain a valid control file checkpoint.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Open the database for read\/write access to create a valid control file checkpoint. The database can then be opened for read-only access.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16008: indeterminate control file checkpoint<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The control file for the database being opened for read-only access was created using the CREATE CONTROLFILE statement. Therefore, a control file checkpoint could not be calculated and the database could not be opened for read-only access.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0First, open the database for read\/write access. This creates a valid control file checkpoint. Then, reopen the database for read-only access.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16009: invalid redo transport destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport destination could not accept redo data because it was not a valid redo transport destination type.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that all redo transport destinations are either standby databases or downstream capture databases.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16011: Remote File Server process is in Error state.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Remote File Server (RFS) process at the specified redo transport destination experienced an unrecoverable error and was unable to receive further redo data.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the problem at the redo transport destination.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16012: database identifier mismatch<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database identifier of a physical standby database did not match that of the primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure that the database identifier of each physical standby database matches that of the primary database.<\/span><\/span><\/span><\/dd>\n

<\/p>\n

<\/a><\/a>ORA-16013: log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0does not need archiving<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16014: log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0not archived, no available destinations<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to archive the named log, but the archive was unsuccessful. The archival failed because there were no archive log destinations specified, or all destinations are in an error state.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that archive log destinations are specified or take the necessary step to correct any errors that may have occurred.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16015: Log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0was not archived.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to archive the named log to a destination, but the operation did not succeed because the destination was not in ARCHIVELOG mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Enable ARCHIVELOG mode at all destinations and retry.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16016: archived log for thread\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0unavailable<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Redo apply timed out waiting for the requested archived log file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that the primary database is still archiving redo data to the standby database and reissue the RECOVER STANDBY DATABASE command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Set the primary archive destination to a valid non-NULL value.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16018: cannot use\u00a0string<\/i>\u00a0with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1…31) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Eliminate any incompatible parameter definitions.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16019: cannot use\u00a0string<\/i>\u00a0with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1…31) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Eliminate any incompatible parameter definitions.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16020: fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The number of archive log destinations that could be used was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Either adjust the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16021: session\u00a0string<\/i>\u00a0destination cannot be the same as session\u00a0string<\/i>\u00a0destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16023: system\u00a0string<\/i>\u00a0destination cannot be the same as session\u00a0string<\/i>\u00a0destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16024: parameter\u00a0string<\/i>\u00a0cannot be parsed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…31) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16025: parameter\u00a0string<\/i>\u00a0contains repeated or conflicting attributes<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained either repeated attributes or attributes that conflicted with each other.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16026: parameter\u00a0string<\/i>\u00a0contains an invalid attribute value<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained an attribute with an invalid value.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16027: parameter\u00a0string<\/i>\u00a0is missing a destination option<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…31) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16028: new\u00a0string<\/i>\u00a0causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change the indicated LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameter (n = 1…31) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1…31). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16030: session specific change to the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter requires a LOG_ARCHIVE_DEST_n destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1…31) parameters.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16031: parameter\u00a0string<\/i>\u00a0destination string exceeds\u00a0string<\/i>\u00a0character limit<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the specified parameter contained a destination string that is too long.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16032: parameter\u00a0string<\/i>\u00a0destination string cannot be translated<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the specified parameter contained a destination string that could not be translated.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use a valid destination string in the specified parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16033: parameter\u00a0string<\/i>\u00a0destination cannot be the same as parameter\u00a0string<\/i>\u00a0destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a different value for one of the archive log parameters.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16034: Recovery could not be started.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Database recovery could not be started because the FROM and MANAGED STANDBY DATABASE clauses were both specifed when attempting to start recovery.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Retry the command with either the FROM or MANAGED STANDBY DATABASE clause, but not both.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16035: missing required keyword\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The indicated keyword is required but was not specified.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the syntax and retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16036: invalid CANCEL option<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A mode other than IMMEDIATE followed the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify either nothing or IMMEDIATE following CANCEL.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16037: user requested cancel of managed recovery operation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The managed standby database recovery operation has been canceled per user request.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16038: log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0cannot be archived<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16039: RFS request version mismatch<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A request to archive a redo log to a redo transport destination failed because of an Oracle software version mismatch at the destination.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that a compatible version of Oracle software is running at the redo transport destination.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16040: Destination archive log file is locked.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The target archive log file was locked. This indicates that the file is being archived to another Remote File Server (RFS) process.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure that each remote redo transport destination uses a unique network service name.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16041: Remote File Server fatal error<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Remote File Server (RFS) process at a redo transport destination encountered a fatal error and was no longer available. Further redo transmission to this destination may not be possible.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Refer to the appropriate RFS trace file located at the redo transport destination for details regarding the error encountered and take corrective action.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16042: user requested cancel immediate of redo apply<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Redo apply was canceled immediately per user request. Processing of the current archive log file has been interrupted and, therefore, the database is in an inconsistent state.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16043: Redo apply has been canceled.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Redo apply was canceled per user request or operation timeout.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0More specific messages will accompany this message.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16044: Destination\u00a0string<\/i>\u00a0attribute cannot be specified at session level.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to modify a redo transport destination attribute using the ALTER SESSION command.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the ALTER SYSTEM command to modify the destination attribute.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16045: circular redo transport destination dependency chain<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to make a redo transport destination dependent on a redo transport destination that was dependent on it.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure that no redo transport destination is dependent on any destination that is dependent on it.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16046: Redo transport destination failed due to failed dependent destination.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport destination was dependent upon another destination, which failed. Therefore, this destination failed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16047: DGID mismatch between destination setting and target database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The DB_UNIQUE_NAME specified for the destination did not match the DB_UNIQUE_NAME at the target database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter matches the DB_UNIQUE_NAME parameter defined at the destination.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16050: destination exceeded specified quota size<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16051: parameter\u00a0string<\/i>\u00a0contains an invalid delay time<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16052: DB_UNIQUE_NAME attribute is required.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0DB_UNIQUE_NAME attribute was not specified. The value of the LOG_ARCHIVE_DEST_n parameter for each remote redo transport destination must contain the DB_UNIQUE_NAME attribute if the LOG_ARCHIVE_CONFIG parameter value contains the DG_CONFIG attribute.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the DB_UNIQUE_NAME attribute to specify the DB_UNIQUE_NAME for the destination.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16053: DB_UNIQUE_NAME\u00a0string<\/i>\u00a0is not in the Data Guard Configuration<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16055: FAL request rejected<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Fetch archive log (FAL) server rejected a redo gap fetch request from the client. This may have various causes.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0to solve the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16056: Backup control file archival requires proper syntax.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the USING BACKUP CONTROLFILE clause to perform an online log file archival using a backup control file.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16057: server not in Data Guard configuration<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The primary database or fetch archive log (FAL) server was not found in the Data Guard configuration of the standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Add the database unique name of the primary database or FAL server to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16058: standby database instance is not mounted<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Remote File Server (RFS) process on the standby database received an internal error.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the standby alert log and RFS trace files for more information.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16059: empty log file or invalid next available block<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to archive an empty or invalid log file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16060: Log file is current.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to archive current log file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16061: Log file status has changed.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The online log file was reclaimed as a new log file either before archival started or during the archival operation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16062: standby database not in Data Guard configuration<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The standby database was not found in the Data Guard configuration of the server.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Add the database unique name of the standby database to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16065: remote archival disabled at standby destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If appropriate change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16066: remote archival disabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If appropriate change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16067: activation identifier mismatch in archive log\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Locate the appropriate archive log for the database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16068: redo log file activation identifier mismatch<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The activation identifier of the indicated redo log file does not match the activation identifier of the database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16069: activation identifier mismatch<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Redo transport failed because the activation identifier of the primary and physical standby databases did not match. This can happen if the physical standby database was not created from a backup of the primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Create a valid configuration and re-try the failed operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16070: parameter\u00a0string<\/i>\u00a0contains an invalid REGISTER attribute value<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O\/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the value for the LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16071: Archived log file\u00a0string<\/i>\u00a0was not found at dependency destination.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified archived log file was not found at a redo tranpsort destination on which other destinations are dependent.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that all redo transport destinations that are dependent upon another destination or upon which other destinations are dependent are configured correctly.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16072: a minimum of one standby database destination is required<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0No standby database archive log destinations were specified.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a standby archive log destination in the initialization parameter file.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16073: archiving must be enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Online log file archiving is disabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Enable log file archiving.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16074: No ARCH processes are active.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0All ARCH processes have stopped.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Restart the instance.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16075: standby database destination mismatch<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Another instance had access to a standby database destination that this instance did not. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this may be due to a standby database becoming unavailable recently.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16076: unknown standby database destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A standby database destination was specified that was not accessed by another instance. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this mismatch may be due to a standby database having been restarted recently.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16078: media recovery disabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database is not in ARCHIVELOG mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Place the database in ARCHIVELOG mode.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16079: standby archival not enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The standby database did not have archival enabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0In order to allow the standby database to access the standby log files, the standby database must be in ARCHIVELOG mode.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16080: invalid LogMiner session\u00a0string<\/i>\u00a0for APPLY<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby apply engine was started with an invalid LogMiner session identifier.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Fix the problem with the LogMiner session or create a new session.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16081: insufficient number of processes for APPLY<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby apply engine was started with fewer processes available than needed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Increase the values of the initialization parameters PROCESSES and or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16082: logical standby is not initialized correctly<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby apply engine was started but it found inconsistencies in its metadata.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Look in the trace file for more information.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16083: LogMiner session has not been created<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby apply engine was started without creating a LogMiner session.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Create a LogMiner session and restart the apply engine.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16084: an apply engine is already running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A logical standby apply engine was running when another was created.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shut down the previous apply engine before starting a new one.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16086: Redo data cannot be written to the standby redo log<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The primary database was in MAXIMUM PROTECTION or MAXIMUM AVAILABILITY mode, but redo data could not be written to the standby redo log at the standby database(s).<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Remote File Server (RFS) trace file for specific errors and reconfigure the standby redo log as appropriate.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16087: Switchover requires standby or current control file.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to perform a switchover operation using a backup or clone control file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Convert the backup control file into a current control file prior to attempting a switchover operation. A clone control file cannot be used for a switchover operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16088: archive log has not been completely archived<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a “current” log file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a completed archive log.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16089: archive log has already been registered<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the V$ARCHIVED_LOG fixed view to verify the archive log information.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16090: archive log to be replaced not created by managed standby process<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No user action required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16091: dependent archive log destination already archived<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An archive log destination contains a dependency to another archive log destination that has previously been archived.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16092: dependent archive log destination is not active<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An archive log destination contains a dependency to another archive log destination that is not active”<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16093: dependent archive log destination is not LGWR-enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process”<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16094: Database shut down during archival operation.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database was shut down while an online log file archival was active.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16095: Dependent destination removal for inactivation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16098: Primary database has been shut down to prevent data loss.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The primary database was shut down because it was operating in maximum protection mode and no suitable standby databases were available to protect the primary database from data loss.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Diagnose and correct whatever errors exist in the configuration or configure the primary database for maximum availability or maximum performance mode.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16099: internal error ORA-00600 occurred at standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The RFS process on the standby database received an internal error.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the standby alert log and RFS trace files for more information.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16100: not a valid Logical Standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This database has not been completely configured as a Logical Standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax.<\/span><\/span><\/span><\/dd>\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-16000 to ORA-16100 ORA-16000: database open for read-only access Cause:\u00a0The database was opened for read-only access. Attempts to modify the database using DML or DDL statements generate this error. Action:\u00a0In order to modify the database, it must first be shut down and reopened for read\/write access. ORA-16001:…<\/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":[14,32,54],"class_list":["post-1933","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-database-administration","tag-oracle-administration","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-vb","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1933","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=1933"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1933\/revisions"}],"predecessor-version":[{"id":1934,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1933\/revisions\/1934"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1933"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1933"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1933"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}