{"id":1727,"date":"2016-02-23T16:03:05","date_gmt":"2016-02-23T13:03:05","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1727"},"modified":"2016-10-20T16:38:59","modified_gmt":"2016-10-20T13:38:59","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-01700-to-ora-01800","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-01700-to-ora-01800\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-01700 to ORA-01800"},"content":{"rendered":"

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

ORA-01702: a view is not appropriate here<\/strong><\/p>\n

Cause:<\/strong> Among other possible causes, this message will be produced if an attempt was made to define an Editioning View over a view.<\/p>\n

Action:<\/strong> An Editioning View may only be created over a base table.<\/p>\n

ORA-01704: string literal too long<\/strong><\/p>\n

Cause:<\/strong> The string literal is longer than 4000 characters.<\/p>\n

Action:<\/strong> Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables.<\/p>\n

ORA-01715: UNIQUE may not be used with a cluster index<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to create a cluster index with the UNIQUE attribute.<\/p>\n

Action:<\/strong> Remove UNIQUE from the CREATE INDEX statement.<\/p>\n

ORA-01716: NOSORT may not be used with a cluster index<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to create a cluster index using the NOSORT option.<\/p>\n

Action:<\/strong> Remove NOSORT from the CREATE INDEX statement.<\/p>\n

ORA-01718: BY ACCESS | SESSION clause not allowed for NOAUDIT<\/strong><\/p>\n

Cause:<\/strong> Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.<\/p>\n

Action:<\/strong> Remove BY ACCESS | SESSION.<\/p>\n

ORA-01719: outer join operator (+) not allowed in operand of OR or IN<\/strong><\/p>\n

Cause:<\/strong> An outer join appears in an or clause.<\/p>\n

Action:<\/strong> If A and B are predicates, to get the effect of (A(+) or B), try (select where (A(+) and not B)) union all (select where (B)).
\n<\/p>\n

ORA-01720: grant option does not exist for ‘string.string’<\/strong><\/p>\n

Cause:<\/strong> A grant was being performed on a view and the grant option was not present for an underlying object.<\/p>\n

Action:<\/strong> Obtain the grant option on all underlying objects of the view.<\/p>\n

ORA-01721: USERENV(COMMITSCN) invoked more than once in a transaction<\/strong><\/p>\n

Cause:<\/strong> The USERENV(‘COMMITSCN’) function can only be used once in a transaction.<\/p>\n

Action:<\/strong> Re-write the transactioin to use USERENV(‘COMMITSCN’) only once<\/p>\n

ORA-01724: floating point precision is out of range (1 to 126)<\/strong><\/p>\n

Cause:<\/strong> Self-evident.<\/p>\n

Action:<\/strong> Self-evident.<\/p>\n

ORA-01725: USERENV(‘COMMITSCN’) not allowed here<\/strong><\/p>\n

Cause:<\/strong> The function USERNEV(‘COMMMITSCN’) is only allowed as a top-level expression in the VALUES clause of an INSERT statements, and on the right hand side of an assignment in an UPDATE statement.<\/p>\n

Action:<\/strong> Correct the use of the function.<\/p>\n

ORA-01734: illegal parameters – EXTENT MIN higher than EXTENT MAX<\/strong><\/p>\n

Cause:<\/strong> A wrong value is specified for the parameter.<\/p>\n

Action:<\/strong> Correct the parameter and reissue the statement.<\/p>\n

ORA-01742: comment not terminated properly<\/strong><\/p>\n

Cause:<\/strong> The indicated comment or hint begun with the \/* token did not have the terminating *\/.<\/p>\n

Action:<\/strong> Properly terminate the comment or hint with a *\/.<\/p>\n

ORA-01743: only pure functions can be indexed<\/strong><\/p>\n

Cause:<\/strong> The indexed function uses SYSDATE or the user environment.<\/p>\n

Action:<\/strong> PL\/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL expressions must not use SYSDATE, USER, USERENV(), or anything else dependent on the session state. NLS-dependent functions are OK.<\/p>\n

ORA-01751: Invalid dump undo option<\/strong><\/p>\n

Cause:<\/strong> An invalid option is specified in the ALTER DUMP UNDO command.<\/p>\n

Action:<\/strong> Correct and reissue the command.<\/p>\n

ORA-01752: cannot delete from view without exactly one key-preserved table<\/strong><\/p>\n

Cause:<\/strong> The deleted table had
\n– no key-preserved tables,<\/p>\n

– more than one key-preserved table, or<\/p>\n

– the key-preserved table was an unmerged view.<\/p>\n

Action:<\/strong> Redefine the view or delete it from the underlying base tables.<\/p>\n

ORA-01754: a table may contain only one column of type LONG<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped.<\/p>\n

Action:<\/strong> Remove the LONG column currently in the table by using the ALTER TABLE command.<\/p>\n

ORA-01755: Must specify an extent number or block number<\/strong><\/p>\n

Cause:<\/strong> Expecting an extent or block number but something else was specified.<\/p>\n

Action:<\/strong> Correct the error and reissue the command.<\/p>\n

ORA-01757: Must specify an object number<\/strong><\/p>\n

Cause:<\/strong> Expecting an object number but something else was specified.<\/p>\n

Action:<\/strong> Correct the error and reissue the command.<\/p>\n

ORA-01761: DML operation does not map to a unique table in the join<\/strong><\/p>\n

Cause:<\/strong> The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table.<\/p>\n

Action:<\/strong> Change the join specification.<\/p>\n

ORA-01763: update or delete involves outer joined table<\/strong><\/p>\n

Cause:<\/strong> For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer- joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table.<\/p>\n

Action:<\/strong> Change the join specification.<\/p>\n

ORA-01764: new update value of join is not guaranteed to be unique<\/strong><\/p>\n

Cause:<\/strong> A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated.<\/p>\n

Action:<\/strong> Change the join specification.<\/p>\n

ORA-01769: duplicate CLUSTER option specifications<\/strong><\/p>\n

Cause:<\/strong> During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.<\/p>\n

Action:<\/strong> Remove the extra CLUSTER option.<\/p>\n

ORA-01771: illegal option for a clustered table<\/strong><\/p>\n

Cause:<\/strong> During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. These options may only be specified for the cluster itself.<\/p>\n

Action:<\/strong> Remove the illegal option(s).<\/p>\n

ORA-01772: Must specify a value for LEVEL<\/strong><\/p>\n

Cause:<\/strong> Expecting the value of LEVEL but something else was specified.<\/p>\n

Action:<\/strong> Correct the error and reissue the command.<\/p>\n

ORA-01774: Dump undo option specified more than once<\/strong><\/p>\n

Cause:<\/strong> The same option for ALTER DUMP UNDO was specified twice.<\/p>\n

Action:<\/strong> Remove the redundant options and reissue the command.<\/p>\n

ORA-01776: cannot modify more than one base table through a join view<\/strong><\/p>\n

Cause:<\/strong> Columns belonging to more than one underlying table were either inserted into or updated.<\/p>\n

Action:<\/strong> Phrase the statement as two or more separate statements.<\/p>\n

ORA-01779: cannot modify a column which maps to a non key-preserved table<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.<\/p>\n

Action:<\/strong> Modify the underlying base tables directly.<\/p>\n

ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT<\/strong><\/p>\n

Cause:<\/strong> UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.<\/p>\n

Action:<\/strong> Do not specify UNRECOVERABLE.<\/p>\n

ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table<\/strong><\/p>\n

Cause:<\/strong> A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.<\/p>\n

Action:<\/strong> Do not specify UNRECOVERABLE.<\/p>\n

ORA-01783: only one RECOVERABLE or UNRECOVERABLE clause may be specified<\/strong><\/p>\n

Cause:<\/strong> RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.<\/p>\n

Action:<\/strong> Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement.<\/p>\n

ORA-01784: RECOVERABLE cannot be specified with database media recovery disabled<\/strong><\/p>\n

Cause:<\/strong> A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.<\/p>\n

Action:<\/strong> Do not specify RECOVERABLE, or restart the database with media recovery enabled.<\/p>\n

ORA-01792: maximum number of columns in a table or view is 1000<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.<\/p>\n

Action:<\/strong> If the error is a result of a CREATE command, then reduce the number of columns in the command and resubmit. If the error is a result of an ALTER TABLE command, then there are two options: 1) If the table contained unused columns, remove them by executing ALTER TABLE DROP UNUSED COLUMNS before adding new columns; 2) Reduce the number of columns in the command and resubmit.<\/p>\n

ORA-01799: a column may not be outer-joined to a subquery<\/strong><\/p>\n

Cause:<\/strong> (+) () is not allowed.<\/p>\n

Action:<\/strong> Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case.<\/p>\n

ORA-01702: a view is not appropriate here<\/strong><\/p>\n

Cause:<\/strong> Among other possible causes, this message will be produced if an attempt was made to define an Editioning View over a view.<\/p>\n

Action:<\/strong> An Editioning View may only be created over a base table.<\/p>\n

ORA-01704: string literal too long<\/strong><\/p>\n

Cause:<\/strong> The string literal is longer than 4000 characters.<\/p>\n

Action:<\/strong> Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables.<\/p>\n

ORA-01715: UNIQUE may not be used with a cluster index<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to create a cluster index with the UNIQUE attribute.<\/p>\n

Action:<\/strong> Remove UNIQUE from the CREATE INDEX statement.<\/p>\n

ORA-01716: NOSORT may not be used with a cluster index<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to create a cluster index using the NOSORT option.<\/p>\n

Action:<\/strong> Remove NOSORT from the CREATE INDEX statement.<\/p>\n

ORA-01718: BY ACCESS | SESSION clause not allowed for NOAUDIT<\/strong><\/p>\n

Cause:<\/strong> Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.<\/p>\n

Action:<\/strong> Remove BY ACCESS | SESSION.<\/p>\n

ORA-01719: outer join operator (+) not allowed in operand of OR or IN<\/strong><\/p>\n

Cause:<\/strong> An outer join appears in an or clause.<\/p>\n

Action:<\/strong> If A and B are predicates, to get the effect of (A(+) or B), try (select where (A(+) and not B)) union all (select where (B)).<\/p>\n

ORA-01720: grant option does not exist for ‘string.string’<\/strong><\/p>\n

Cause:<\/strong> A grant was being performed on a view and the grant option was not present for an underlying object.<\/p>\n

Action:<\/strong> Obtain the grant option on all underlying objects of the view.<\/p>\n

ORA-01721: USERENV(COMMITSCN) invoked more than once in a transaction<\/strong><\/p>\n

Cause:<\/strong> The USERENV(‘COMMITSCN’) function can only be used once in a transaction.<\/p>\n

Action:<\/strong> Re-write the transactioin to use USERENV(‘COMMITSCN’) only once<\/p>\n

ORA-01724: floating point precision is out of range (1 to 126)<\/strong><\/p>\n

Cause:<\/strong> Self-evident.<\/p>\n

Action:<\/strong> Self-evident.<\/p>\n

ORA-01725: USERENV(‘COMMITSCN’) not allowed here<\/strong><\/p>\n

Cause:<\/strong> The function USERNEV(‘COMMMITSCN’) is only allowed as a top-level expression in the VALUES clause of an INSERT statements, and on the right hand side of an assignment in an UPDATE statement.<\/p>\n

Action:<\/strong> Correct the use of the function.<\/p>\n

ORA-01734: illegal parameters – EXTENT MIN higher than EXTENT MAX<\/strong><\/p>\n

Cause:<\/strong> A wrong value is specified for the parameter.<\/p>\n

Action:<\/strong> Correct the parameter and reissue the statement.<\/p>\n

ORA-01742: comment not terminated properly<\/strong><\/p>\n

Cause:<\/strong> The indicated comment or hint begun with the \/* token did not have the terminating *\/.<\/p>\n

Action:<\/strong> Properly terminate the comment or hint with a *\/.<\/p>\n

ORA-01743: only pure functions can be indexed<\/strong><\/p>\n

Cause:<\/strong> The indexed function uses SYSDATE or the user environment.<\/p>\n

Action:<\/strong> PL\/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL expressions must not use SYSDATE, USER, USERENV(), or anything else dependent on the session state. NLS-dependent functions are OK.<\/p>\n

ORA-01751: Invalid dump undo option<\/strong><\/p>\n

Cause:<\/strong> An invalid option is specified in the ALTER DUMP UNDO command.<\/p>\n

Action:<\/strong> Correct and reissue the command.<\/p>\n

ORA-01752: cannot delete from view without exactly one key-preserved table<\/strong><\/p>\n

Cause:<\/strong> The deleted table had
\n– no key-preserved tables,<\/p>\n

– more than one key-preserved table, or<\/p>\n

– the key-preserved table was an unmerged view.<\/p>\n

Action:<\/strong> Redefine the view or delete it from the underlying base tables.<\/p>\n

ORA-01754: a table may contain only one column of type LONG<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped.<\/p>\n

Action:<\/strong> Remove the LONG column currently in the table by using the ALTER TABLE command.<\/p>\n

ORA-01755: Must specify an extent number or block number<\/strong><\/p>\n

Cause:<\/strong> Expecting an extent or block number but something else was specified.<\/p>\n

Action:<\/strong> Correct the error and reissue the command.<\/p>\n

ORA-01757: Must specify an object number<\/strong><\/p>\n

Cause:<\/strong> Expecting an object number but something else was specified.<\/p>\n

Action:<\/strong> Correct the error and reissue the command.<\/p>\n

ORA-01761: DML operation does not map to a unique table in the join<\/strong><\/p>\n

Cause:<\/strong> The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table.<\/p>\n

Action:<\/strong> Change the join specification.<\/p>\n

ORA-01763: update or delete involves outer joined table<\/strong><\/p>\n

Cause:<\/strong> For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer- joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table.<\/p>\n

Action:<\/strong> Change the join specification.<\/p>\n

ORA-01764: new update value of join is not guaranteed to be unique<\/strong><\/p>\n

Cause:<\/strong> A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated.<\/p>\n

Action:<\/strong> Change the join specification.<\/p>\n

ORA-01769: duplicate CLUSTER option specifications<\/strong><\/p>\n

Cause:<\/strong> During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.<\/p>\n

Action:<\/strong> Remove the extra CLUSTER option.<\/p>\n

ORA-01771: illegal option for a clustered table<\/strong><\/p>\n

Cause:<\/strong> During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. These options may only be specified for the cluster itself.<\/p>\n

Action:<\/strong> Remove the illegal option(s).<\/p>\n

ORA-01772: Must specify a value for LEVEL<\/strong><\/p>\n

Cause:<\/strong> Expecting the value of LEVEL but something else was specified.<\/p>\n

Action:<\/strong> Correct the error and reissue the command.<\/p>\n

ORA-01774: Dump undo option specified more than once<\/strong><\/p>\n

Cause:<\/strong> The same option for ALTER DUMP UNDO was specified twice.<\/p>\n

Action:<\/strong> Remove the redundant options and reissue the command.<\/p>\n

ORA-01776: cannot modify more than one base table through a join view<\/strong><\/p>\n

Cause:<\/strong> Columns belonging to more than one underlying table were either inserted into or updated.<\/p>\n

Action:<\/strong> Phrase the statement as two or more separate statements.<\/p>\n

ORA-01779: cannot modify a column which maps to a non key-preserved table<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.<\/p>\n

Action:<\/strong> Modify the underlying base tables directly.<\/p>\n

ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT<\/strong><\/p>\n

Cause:<\/strong> UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.<\/p>\n

Action:<\/strong> Do not specify UNRECOVERABLE.<\/p>\n

ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table<\/strong><\/p>\n

Cause:<\/strong> A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.<\/p>\n

Action:<\/strong> Do not specify UNRECOVERABLE.<\/p>\n

ORA-01783: only one RECOVERABLE or UNRECOVERABLE clause may be specified<\/strong><\/p>\n

Cause:<\/strong> RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.<\/p>\n

Action:<\/strong> Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement.<\/p>\n

ORA-01784: RECOVERABLE cannot be specified with database media recovery disabled<\/strong><\/p>\n

Cause:<\/strong> A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.<\/p>\n

Action:<\/strong> Do not specify RECOVERABLE, or restart the database with media recovery enabled.<\/p>\n

ORA-01792: maximum number of columns in a table or view is 1000<\/strong><\/p>\n

Cause:<\/strong> An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.<\/p>\n

Action:<\/strong> If the error is a result of a CREATE command, then reduce the number of columns in the command and resubmit. If the error is a result of an ALTER TABLE command, then there are two options: 1) If the table contained unused columns, remove them by executing ALTER TABLE DROP UNUSED COLUMNS before adding new columns; 2) Reduce the number of columns in the command and resubmit.<\/p>\n

ORA-01799: a column may not be outer-joined to a subquery<\/strong><\/p>\n

Cause:<\/strong> (+) () is not allowed.<\/p>\n

Action:<\/strong> Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case.<\/p>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-01700 to ORA-01800 ORA-01702: a view is not appropriate here Cause: Among other possible causes, this message will be produced if an attempt was made to define an Editioning View over a view. Action: An Editioning View may only be created over a base table. ORA-01704: string…<\/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-1727","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-rR","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1727","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=1727"}],"version-history":[{"count":2,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1727\/revisions"}],"predecessor-version":[{"id":1739,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1727\/revisions\/1739"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1727"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1727"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1727"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}