{"id":1735,"date":"2016-02-25T16:22:46","date_gmt":"2016-02-25T13:22:46","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1735"},"modified":"2016-10-20T16:26:27","modified_gmt":"2016-10-20T13:26:27","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-02000-to-ora-02100","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-02000-to-ora-02100\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-02000 to ORA-02100"},"content":{"rendered":"

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

ORA-02001: user SYS is not permitted to create indexes with freelist groups<\/strong><\/p>\n

Cause:<\/strong> user tried to create an index while running with sys authorization.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02004: security violation<\/strong><\/p>\n

Cause:<\/strong> This error code is never returned to a user. It is used as a value for column, audit_trail.returncode, to signal that a security violation occurred.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02007: can’t use ALLOCATE or DEALLOCATE options with REBUILD<\/strong><\/p>\n

Cause:<\/strong> Allocate or deallocate storage and rebuild index are not compatible.<\/p>\n

Action:<\/strong> Choose one or the other.<\/p>\n

ORA-02009: the size specified for a file must not be zero<\/strong><\/p>\n

Cause:<\/strong> A value of zero was specified in a SIZE or RESIZE clause of a file specification.<\/p>\n

Action:<\/strong> Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause.<\/p>\n

ORA-02020: too many database links in use<\/strong><\/p>\n

Cause:<\/strong> The current session has exceeded the INIT.ORA open_links maximum.<\/p>\n

Action:<\/strong> Increase the open_links limit, or free up some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases.<\/p>\n

ORA-02021: DDL operations are not allowed on a remote database<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to use a DDL operation on a remote database. For example, “CREATE TABLE tablename@remotedbname …”.<\/p>\n

Action:<\/strong> To alter the remote database structure, you must connect to the remote database with the appropriate privileges.<\/p>\n

ORA-02022: remote statement has unoptimized view with remote object<\/strong><\/p>\n

Cause:<\/strong> The local view is unoptimized and contains references to objects at the remote database and the statement must be executed at the remote database.<\/p>\n

Action:<\/strong> Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote.<\/p>\n

ORA-02024: database link not found<\/strong><\/p>\n

Cause:<\/strong> Database link to be dropped is not found in dictionary<\/p>\n

Action:<\/strong> Correct the database link name<\/p>\n

ORA-02025: all tables in the SQL statement must be at the remote database<\/strong><\/p>\n

Cause:<\/strong> The user’s SQL statement references tables from multiple databases. The remote database is not Oracle V7 or above, and can perform updates only if it can reference all tables in the SQL statement.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02026: missing LINK keyword<\/strong><\/p>\n

Cause:<\/strong> keyword missing<\/p>\n

Action:<\/strong> supply missing keyword<\/p>\n

ORA-02027: multi-row UPDATE of LONG column is not supported<\/strong><\/p>\n

Cause:<\/strong> A bind variable with length greater than 4000 bytes is being used to update a column, and the update statement updates more than one row.<\/p>\n

Action:<\/strong> You may only update a single row with such a bind variable.<\/p>\n

ORA-02028: fetching an exact number of rows is not supported by the server<\/strong><\/p>\n

Cause:<\/strong> The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side.<\/p>\n

Action:<\/strong> Connect to a valid server or do not use an exact fetch.<\/p>\n

ORA-02029: missing FILE keyword<\/strong><\/p>\n

Cause:<\/strong> keyword missing<\/p>\n

Action:<\/strong> supply missing keyword<\/p>\n

ORA-02030: can only select from fixed tables\/views<\/strong><\/p>\n

Cause:<\/strong> An attempt is being made to perform an operation other than a retrieval from a fixed table\/view.<\/p>\n

Action:<\/strong> You may only select rows from fixed tables\/views.<\/p>\n

ORA-02031: no ROWID for fixed tables or for external-organized tables<\/strong><\/p>\n

Cause:<\/strong> An attempt is being made to access rowid from a fixed table or from a external-organized table.<\/p>\n

Action:<\/strong> Do not access ROWID from a fixed table or from a external-organized table.<\/p>\n

ORA-02032: clustered tables cannot be used before the cluster index is built<\/strong><\/p>\n

Cause:<\/strong> User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created.<\/p>\n

Action:<\/strong> Create the cluster index.<\/p>\n

ORA-02033: a cluster index for this cluster already exists<\/strong><\/p>\n

Cause:<\/strong> A cluster index already exists for the cluster.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02034: speed bind not permitted<\/strong><\/p>\n

Cause:<\/strong> Speed bind not allowed with supplied bind variables. Trapped internally by the system.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02035: illegal bundled operation combination<\/strong><\/p>\n

Cause:<\/strong> User requested that the UPI bundled execution call perform an an illegal combination of operations.<\/p>\n

Action:<\/strong> See documentation for legal operation combinations.<\/p>\n

ORA-02036: too many variables to describe with automatic cursor open<\/strong><\/p>\n

Cause:<\/strong> User requested that the UPI bundled execution call perform automatic cursor open and close on a describe operation. There were too many select-list items or bind variables to do this.<\/p>\n

Action:<\/strong> open and close cursor explicitly<\/p>\n

ORA-02037: uninitialized speed bind storage<\/strong><\/p>\n

Cause:<\/strong> User attempted a UPI bundled execution call containing a standalone execute operation without first performing a UPI bundled execution call containing a bind operation.<\/p>\n

Action:<\/strong> perform a UPI bundled execution call with bind before performing a bundled execution call with execute<\/p>\n

ORA-02038: define is not allowed for array type<\/strong><\/p>\n

Cause:<\/strong> User attempted to define a select list variable of type “array”. Arrays may only serve as host bind variables.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02039: bind by value is not allowed for array type<\/strong><\/p>\n

Cause:<\/strong> User attempted to bind an array host variable by value. Arrays may only be bound by reference.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02040: remote database string does not support two-phase commit<\/strong><\/p>\n

Cause:<\/strong> the database was potentially updated but does not support prepare to commit (as determined by its logon transaction traits). The transaction was rolled back.<\/p>\n

Action:<\/strong> Do not attempt to update the remote database unless it is the only database updated in one transaction.<\/p>\n

ORA-02041: client database did not begin a transaction<\/strong><\/p>\n

Cause:<\/strong> internal error<\/p>\n

Action:<\/strong> contact support<\/p>\n

ORA-02042: too many distributed transactions<\/strong><\/p>\n

Cause:<\/strong> the distributed transaction table was full because too many distributed transactions were active.<\/p>\n

Action:<\/strong> Run fewer transactions. If you are sure you don’t have too many concurrent distributed transactions, this indicates an internal error and support should be notified. Instance shutdown\/restart would be a work-around.<\/p>\n

ORA-02043: must end current transaction before executing string<\/strong><\/p>\n

Cause:<\/strong> a transaction is in progress and one of the following commands commands is issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode.<\/p>\n

Action:<\/strong> COMMIT or ROLLBACK the current transaction and resubmit command.<\/p>\n

ORA-02044: transaction manager login denied: transaction in progress<\/strong><\/p>\n

Cause:<\/strong> a remote transaction manager tried to log in while a distributed transaction is in progress.<\/p>\n

Action:<\/strong> end the current transaction (this is a protocol error from a remote transaction manager)<\/p>\n

ORA-02045: too many local sessions participating in global transaction<\/strong><\/p>\n

Cause:<\/strong> too many sessions at this site for this transaction.<\/p>\n

Action:<\/strong> use an existing link so another session need not be created.<\/p>\n

ORA-02046: distributed transaction already begun<\/strong><\/p>\n

Cause:<\/strong> internal error or error in external transaction manager. A server session received a begin_tran RPC before finishing with a previous distributed tran.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02047: cannot join the distributed transaction in progress<\/strong><\/p>\n

Cause:<\/strong> Either a transaction is in progress against a remote database that does not fully support two phase commit, and an update is attempted on another database, or updates are pending and and an attempt is made to update a different database that does not fully support two phase commit.<\/p>\n

Action:<\/strong> complete the current transaction and then resubmit the update request.<\/p>\n

ORA-02048: attempt to begin distributed transaction without logging on<\/strong><\/p>\n

Cause:<\/strong> client program must issue a distributed transaction login.<\/p>\n

Action:<\/strong> contact support.<\/p>\n

ORA-02049: timeout: distributed transaction waiting for lock<\/strong><\/p>\n

Cause:<\/strong> exceeded INIT.ORA distributed_lock_timeout seconds waiting for lock.<\/p>\n

Action:<\/strong> treat as a deadlock<\/p>\n

ORA-02050: transaction string rolled back, some remote DBs may be in-doubt<\/strong><\/p>\n

Cause:<\/strong> network or remote failure in 2PC.<\/p>\n

Action:<\/strong> Notify operations; remote DBs will automatically re-sync when the failure is repaired.<\/p>\n

ORA-02051: another session in same transaction failed<\/strong><\/p>\n

Cause:<\/strong> a session at the same site with same global transaction ID failed; It can also be caused by application error if an attempt was made to update database while another tightly coupled transaction branch with same global transaction ID has been finalized.<\/p>\n

Action:<\/strong> none necessary, transaction automatically recovered. In case of application error, make sure no more updates to database once transaction manager has started two-phase commit for tightly coupled distributed transaction.<\/p>\n

ORA-02052: remote transaction failure at string<\/strong><\/p>\n

Cause:<\/strong> error in remote transaction at given DBLINK<\/p>\n

Action:<\/strong> retry<\/p>\n

ORA-02053: transaction string committed, some remote DBs may be in-doubt<\/strong><\/p>\n

Cause:<\/strong> network or remote failure in 2PC.<\/p>\n

Action:<\/strong> Notify operations; remote DBs will automatically re-sync when the failure is repaired.<\/p>\n

ORA-02054: transaction string in-doubt<\/strong><\/p>\n

Cause:<\/strong> network or remote failure in 2PC.<\/p>\n

Action:<\/strong> Notify operations; DBs will automatically re-sync when the failure is repaired. Monitor pending_trans$ for final outcome.<\/p>\n

ORA-02055: distributed update operation failed; rollback required<\/strong><\/p>\n

Cause:<\/strong> a failure during distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent, the transaction must roll back to a savepoint or entirely<\/p>\n

Action:<\/strong> rollback to a savepoint or rollback transaction and resubmit<\/p>\n

ORA-02056: 2PC: string: bad two-phase command number string from string<\/strong><\/p>\n

Cause:<\/strong> two-phase commit protocol error.<\/p>\n

Action:<\/strong> recovery of transaction attempted. Monitor pending_trans$ table to ensure correct resolution. Contact support.<\/p>\n

ORA-02057: 2PC: string: bad two-phase recovery state number string from string<\/strong><\/p>\n

Cause:<\/strong> internal error in two-phase recovery protocol<\/p>\n

Action:<\/strong> contact support<\/p>\n

ORA-02058: no prepared transaction found with ID string<\/strong><\/p>\n

Cause:<\/strong> no transaction with local_tran_id or global_tran_id found in the pending_trans$ table in prepared state.<\/p>\n

Action:<\/strong> check the pending_trans$ table.<\/p>\n

ORA-02059: ORA-2PC-CRASH-TEST-string in commit comment<\/strong><\/p>\n

Cause:<\/strong> This is a special comment used to test the two phase commit.<\/p>\n

Action:<\/strong> Don’t use this special comment (%s a number 1-10)<\/p>\n

ORA-02060: select for update specified a join of distributed tables<\/strong><\/p>\n

Cause:<\/strong> tables in a join with the for update clause must reside at the same DB.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02061: lock table specified list of distributed tables<\/strong><\/p>\n

Cause:<\/strong> tables in a lock table statement must reside at the same DB.<\/p>\n

Action:<\/strong> issue multiple lock table commands.<\/p>\n

ORA-02062: distributed recovery received DBID string, expected string<\/strong><\/p>\n

Cause:<\/strong> a database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different DB mounted.<\/p>\n

Action:<\/strong> restore link definition or remote database.<\/p>\n

ORA-02063: preceding stringstring from stringstring<\/strong><\/p>\n

Cause:<\/strong> an Oracle error was received from a remote database link.<\/p>\n

Action:<\/strong> refer to the preceding error message(s)<\/p>\n

ORA-02064: distributed operation not supported<\/strong><\/p>\n

Cause:<\/strong> One of the following unsupported operations was attempted:
\n1. array execute of a remote update with a subquery that references a dblink, or<\/p>\n

2. an update of a long column with bind variable and an update of a second column with a subquery that both references a dblink and a bind variable, or<\/p>\n

3. a commit is issued in a coordinated session from an RPC procedure call with OUT parameters or function call.<\/p>\n

Action:<\/strong> simplify remote update statement<\/p>\n

ORA-02065: illegal option for ALTER SYSTEM<\/strong><\/p>\n

Cause:<\/strong> The option specified for ALTER SYSTEM is not supported<\/p>\n

Action:<\/strong> refer to the user manual for option supported<\/p>\n

ORA-02066: missing or invalid DISPATCHERS text<\/strong><\/p>\n

Cause:<\/strong> A character string literal was expected, but not found, following ALTER SYSTEM SET DISPATCHERS<\/p>\n

Action:<\/strong> place the string literal containing the dispatcher’s specification after ALTER SYSTEM SET DISPATCHERS<\/p>\n

ORA-02067: transaction or savepoint rollback required<\/strong><\/p>\n

Cause:<\/strong> A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.<\/p>\n

Action:<\/strong> rollback to a previous savepoint or rollback the transaction and resubmit.<\/p>\n

ORA-02068: following severe error from stringstring<\/strong><\/p>\n

Cause:<\/strong> A severe error (disconnect, fatal Oracle error) received from the indicated database link. See following error text.<\/p>\n

Action:<\/strong> Contact the remote system administrator.<\/p>\n

ORA-02069: global_names parameter must be set to TRUE for this operation<\/strong><\/p>\n

Cause:<\/strong> A remote mapping of the statement is required but cannot be achieved because global_names should be set to TRUE for it to be achieved<\/p>\n

Action:<\/strong> Issue alter session set global_names = true if possible<\/p>\n

ORA-02070: database stringstring does not support string in this context<\/strong><\/p>\n

Cause:<\/strong> The remote database does not support the named capability in the context in which it is used.<\/p>\n

Action:<\/strong> Simplify the SQL statement.<\/p>\n

ORA-02071: error initializing capabilities for remote database string<\/strong><\/p>\n

Cause:<\/strong> Could not load a remote-specified capability table.<\/p>\n

Action:<\/strong> Contact support for the remote SQL*Connect product.<\/p>\n

ORA-02072: distributed database network protocol mismatch<\/strong><\/p>\n

Cause:<\/strong> This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example.<\/p>\n

Action:<\/strong> Upgrade the older release.<\/p>\n

ORA-02073: sequence numbers not supported in remote updates<\/strong><\/p>\n

Cause:<\/strong> Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02074: cannot string in a distributed transaction<\/strong><\/p>\n

Cause:<\/strong> A commit or rollback was attempted from session other than the parent of a distributed transaction.<\/p>\n

Action:<\/strong> Only commit or rollback from the parent session.<\/p>\n

ORA-02075: another instance changed state of transaction string<\/strong><\/p>\n

Cause:<\/strong> A commit force or rollback force was issued from a session in another instance.<\/p>\n

Action:<\/strong> Check if another Oracle instance is performing recovery of pending transactions. Query DBA_2PC_PENDING to determine the new state of the transaction.<\/p>\n

ORA-02076: sequence not co-located with updated table or long column<\/strong><\/p>\n

Cause:<\/strong> all referenced sequences must be co-located with the table with the long column.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02077: selects of long columns must be from co-located tables<\/strong><\/p>\n

Cause:<\/strong> if a select returns long columns from multiple tables, all the tables must be co-located<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02079: cannot join a committing distributed transaction<\/strong><\/p>\n

Cause:<\/strong> Once a transaction branch is prepared, no more new transaction branches are allowed to start, nor is the prepared transaction branch allowed to be joined.<\/p>\n

Action:<\/strong> Check the application code as this is an XA protocol violation.<\/p>\n

ORA-02080: database link is in use<\/strong><\/p>\n

Cause:<\/strong> a transaction is active or a cursor is open on the database link given in the alter session close database link command.<\/p>\n

Action:<\/strong> commit or rollback, and close all cursors<\/p>\n

ORA-02081: database link is not open<\/strong><\/p>\n

Cause:<\/strong> dblink given is not currently open.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02082: a loopback database link must have a connection qualifier<\/strong><\/p>\n

Cause:<\/strong> attempt to create a database link with the same name as the current database.<\/p>\n

Action:<\/strong> a loopback database link needs a trailing qualifier, e.g. MYDB.DEV.US.ORACLE.COM@INST1 – the ‘@INST1’ is the qualifier<\/p>\n

ORA-02083: database name has illegal character ‘string’<\/strong><\/p>\n

Cause:<\/strong> supplied database name can contain only A-Z, 0-9, ‘_’, ‘#’, ‘$’ ‘.’ and ‘@’ characters.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02084: database name is missing a component<\/strong><\/p>\n

Cause:<\/strong> supplied database name cannot contain a leading ‘.’, trailing ‘.’ or ‘@’, or two ‘.’ or ‘@’ in a row.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02085: database link string connects to string<\/strong><\/p>\n

Cause:<\/strong> a database link connected to a database with a different name. The connection is rejected.<\/p>\n

Action:<\/strong> create a database link with the same name as the database it connects to, or set global_names=false.<\/p>\n

ORA-02086: database (link) name is too long<\/strong><\/p>\n

Cause:<\/strong> database\/database link name can have at most 128 characters.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02087: object locked by another process in same transaction<\/strong><\/p>\n

Cause:<\/strong> A database link is being used in the cluster database environment that loops back to the same instance. One session is trying to convert a lock that was obtained by the other session.<\/p>\n

Action:<\/strong> Get the more restrictive lock first. For example, if session 1 gets a share lock and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or, simply use the same session to access the object.<\/p>\n

ORA-02088: distributed database option not installed<\/strong><\/p>\n

Cause:<\/strong> Remote and distributed updates and transactions are a separately priced option in ORACLE V7.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02089: COMMIT is not allowed in a subordinate session<\/strong><\/p>\n

Cause:<\/strong> COMMIT was issued in a session that is not the two-phase commit global coordinator.<\/p>\n

Action:<\/strong> Issue commit at the global coordinator only.<\/p>\n

ORA-02090: network error: attempted callback+passthru<\/strong><\/p>\n

Cause:<\/strong> internal error.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02091: transaction rolled back<\/strong><\/p>\n

Cause:<\/strong> Also see error 2092. If the transaction is aborted at a remote site then you will only see 2091; if aborted at host then you will see 2092 and 2091.<\/p>\n

Action:<\/strong> Add rollback segment and retry the transaction.<\/p>\n

ORA-02092: out of transaction table slots for distributed transaction<\/strong><\/p>\n

Cause:<\/strong> The transaction is assigned to the system rollback segment and is trying to get into the PREPARED state, but the required number of non-PREPARED slots are not available, hence the transaction is rolled back.<\/p>\n

Action:<\/strong> Add a rollback segment and retry the transaction.<\/p>\n

ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)<\/strong><\/p>\n

Cause:<\/strong> Value of parameter specified is greater than allowed on this port.<\/p>\n

Action:<\/strong> Use default or reduce it to less than max.<\/p>\n

ORA-02094: replication option not installed<\/strong><\/p>\n

Cause:<\/strong> The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable.<\/p>\n

Action:<\/strong> Install the replication option. The replication option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased.<\/p>\n

ORA-02095: specified initialization parameter cannot be modified<\/strong><\/p>\n

Cause:<\/strong> The specified initialization parameter is not modifiable<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-02096: specified initialization parameter is not modifiable with this option<\/strong><\/p>\n

Cause:<\/strong> Though the initialization parameter is modifiable, it cannot be modified using the specified command.<\/p>\n

Action:<\/strong> Check the DBA guide for information about under what scope the parameter may be modified<\/p>\n

ORA-02097: parameter cannot be modified because specified value is invalid<\/strong><\/p>\n

Cause:<\/strong> Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter.<\/p>\n

Action:<\/strong> Check the DBA guide for range of acceptable values for this parameter.<\/p>\n

ORA-02098: error parsing index-table reference (:I)<\/strong><\/p>\n

Cause:<\/strong> An incorrect index-table (:I) syntax was encountered.<\/p>\n

Action:<\/strong> This syntax is for oracle internal use only.<\/p>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-02000 to ORA-02100 ORA-02001: user SYS is not permitted to create indexes with freelist groups Cause: user tried to create an index while running with sys authorization. Action: None ORA-02004: security violation Cause: This error code is never returned to a user. It is used as a…<\/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":false,"_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-1735","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-rZ","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1735","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=1735"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1735\/revisions"}],"predecessor-version":[{"id":1736,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1735\/revisions\/1736"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1735"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1735"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1735"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}