{"id":4245,"date":"2019-07-31T13:39:14","date_gmt":"2019-07-31T16:39:14","guid":{"rendered":"https:\/\/www.dbarj.com.br\/?p=4245"},"modified":"2019-07-31T13:39:14","modified_gmt":"2019-07-31T16:39:14","slug":"oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065","status":"publish","type":"post","link":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/","title":{"rendered":"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065"},"content":{"rendered":"<p>Those days, I was updating some of my lab environments running Oracle Database <strong>12.1.0.2<\/strong> to the <strong>190716<\/strong> quarterly update <strong>Bundle Patch<\/strong>. However, during the Datapatch execution phase, I was getting some ORA errors.<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">Patch 29496791 apply (pdb CDB$ROOT): SUCCESS\r\n  logfile: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/29496791\/22993732\/29496791_apply_ORCL_CDBROOT_2019Jul31_11_55_12.log (no errors)\r\nPatch 29496791 apply (pdb PDB$SEED): WITH ERRORS\r\n  logfile: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/29496791\/22993732\/29496791_apply_ORCL_PDBSEED_2019Jul31_11_58_00.log (errors)\r\n    Error at line 26523: ORA-04068: existing state of packages has been discarded\r\n    Error at line 26524: ORA-04061: existing state of package body \"SYS.DBMS_REGISTRY_SYS\" has been\r\n    Error at line 26526: ORA-04065: not executed, altered or dropped package body\r\n    Error at line 26528: ORA-06508: PL\/SQL: could not find program unit being called:\r\n    Error at line 33825: ORA-20000: Insufficient privileges to analyze an object in Dictionary Schema\r\nPatch 29496791 apply (pdb PDB01): WITH ERRORS\r\n  logfile: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/29496791\/22993732\/29496791_apply_ORCL_PDB01_2019Jul31_11_58_00.log (errors)\r\n    Error at line 26330: ORA-04068: existing state of packages has been discarded\r\n    Error at line 26331: ORA-04061: existing state of package body \"SYS.DBMS_REGISTRY_SYS\" has been\r\n    Error at line 26333: ORA-04065: not executed, altered or dropped package body\r\n    Error at line 26335: ORA-06508: PL\/SQL: could not find program unit being called:\r\n    Error at line 33632: ORA-20000: Insufficient privileges to analyze an object in Dictionary Schema<\/pre>\n<p>Checking the datapatch log file, I could find it was related with OLS:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">SQL&gt; EXECUTE DBMS_REGISTRY.LOADING('OLS', 'Oracle Label Security', 'validate_ols', 'LBACSYS');\r\nBEGIN DBMS_REGISTRY.LOADING('OLS', 'Oracle Label Security', 'validate_ols', 'LBACSYS'); END;\r\n*\r\nERROR at line 1:\r\nORA-04068: existing state of packages has been discarded\r\nORA-04061: existing state of package body \"SYS.DBMS_REGISTRY_SYS\" has been invalidated\r\nORA-04065: not executed, altered or dropped package body \"SYS.DBMS_REGISTRY_SYS\"<\/pre>\n<p>After some research, I&#8217;ve found the following note:<\/p>\n<table id=\"kmPgTpl:sd_r1:0:dv_rDoc:0:tl5\" style=\"width: 100%; height: 44px;\" border=\"0\" summary=\"\" width=\"100%\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr id=\"kmPgTpl:sd_r1:0:dv_rDoc:0:rl12\" style=\"height: 44px;\">\n<td id=\"kmPgTpl:sd_r1:0:dv_rDoc:0:cf49\" style=\"height: 44px;\" align=\"left\"><a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocumentDisplay?id=2534844.1\" target=\"_blank\" rel=\"noopener noreferrer\"><span id=\"kmPgTpl:sd_r1:0:dv_rDoc:0:ol22\" class=\"xq\"><label>Oracle Database Proactive Patch 12.1.0.2.190716 Known Issues (Doc ID 2534844.1)<\/label><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>And it states:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">In certain situations the Post-install actions (datapatch -verbose) may fail for DBBP 12.1.0.2.190716:\r\n\r\nError at line 26397: ORA-04068: existing state of packages has been discarded\r\nError at line 26398: ORA-04061: existing state of package body \"SYS.DBMS_REGISTRY_SYS\" has been\r\nError at line 26400: ORA-04065: not executed, altered or dropped package body\r\nError at line 26402: ORA-06508: PL\/SQL: could not find program unit being called:\r\nError at line 33699: ORA-20000: Insufficient privileges to analyze an object in Dictionary Schema\r\n\r\nWhen this occurs, it is simply a consequence of the order that certain actions are performed within the \"datapatch\" process. The workaround is simply to run 'datapatch \u2013verbose' a second time.\r\n\r\nA fix for this will be included into a future quarterly DBBP.<\/pre>\n<p>So basically, a datapatch rerun should fix this issue..<\/p>\n<p>Let&#8217;s run it again:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">SQL Patching tool version 12.1.0.2.0 Production on Wed Jul 31 12:56:18 2019\r\nCopyright (c) 2012, 2017, Oracle.  All rights reserved.\r\n\r\nLog file for this invocation: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/sqlpatch_14491_2019_07_31_12_56_18\/sqlpatch_invocation.log\r\n\r\nConnecting to database...OK\r\nNote:  Datapatch will only apply or rollback SQL fixes for PDBs\r\n       that are in an open state, no patches will be applied to closed PDBs.\r\n       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation\r\n       (Doc ID 1585822.1)\r\nBootstrapping registry and package to current versions...done\r\n\r\nQueryable inventory could not determine the current opatch status.\r\nExecute 'select dbms_sqlpatch.verify_queryable_inventory from dual'\r\nand\/or check the invocation log\r\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/sqlpatch_14491_2019_07_31_12_56_18\/sqlpatch_invocation.log\r\nfor the complete error.\r\nPrereq check failed, exiting without installing any patches.\r\n\r\nPlease refer to MOS Note 1609718.1 and\/or the invocation log\r\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/sqlpatch_14491_2019_07_31_12_56_18\/sqlpatch_invocation.log\r\nfor information on how to resolve the above errors.\r\n\r\nSQL Patching tool complete on Wed Jul 31 12:56:29 2019<\/pre>\n<p>Now I got a different error. However, if I run for a <strong>third time<\/strong>:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">SQL Patching tool version 12.1.0.2.0 Production on Wed Jul 31 12:56:29 2019\r\nCopyright (c) 2012, 2017, Oracle.  All rights reserved.\r\n\r\nLog file for this invocation: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/sqlpatch_14802_2019_07_31_12_56_29\/sqlpatch_invocation.log\r\n\r\nConnecting to database...OK\r\nNote:  Datapatch will only apply or rollback SQL fixes for PDBs\r\n       that are in an open state, no patches will be applied to closed PDBs.\r\n       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation\r\n       (Doc ID 1585822.1)\r\nBootstrapping registry and package to current versions...done\r\nDetermining current state...done\r\n\r\nCurrent state of SQL patches:\r\nBundle series DBBP:\r\n  ID 190716 in the binary registry and ID 190716 in PDB CDB$ROOT, ID 190716 with errors in PDB PDB$SEED, ID 190716 with errors in PDB PDB01\r\n\r\nAdding patches to installation queue and performing prereq checks...\r\nInstallation queue:\r\n  For the following PDBs: CDB$ROOT\r\n    Nothing to roll back\r\n    Nothing to apply\r\n  For the following PDBs: PDB$SEED PDB01\r\n    Nothing to roll back\r\n    The following patches will be applied:\r\n      29496791 (DATABASE BUNDLE PATCH 12.1.0.2.190716)\r\n\r\nInstalling patches...\r\nPatch installation complete.  Total patches installed: 2\r\n\r\nValidating logfiles...\r\nPatch 29496791 apply (pdb PDB$SEED): SUCCESS\r\n  logfile: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/29496791\/22993732\/29496791_apply_ORCL_PDBSEED_2019Jul31_12_56_57.log (no errors)\r\nPatch 29496791 apply (pdb PDB01): SUCCESS\r\n  logfile: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/29496791\/22993732\/29496791_apply_ORCL_PDB01_2019Jul31_12_56_57.log (no errors)\r\nSQL Patching tool complete on Wed Jul 31 12:59:03 2019<\/pre>\n<p><strong>That&#8217;s it, if you face the error above, just rerun your datapatch 2 more times and you will be fine.<\/strong><\/p>\n<b>Have you enjoyed? Please leave a comment or give a \ud83d\udc4d!<\/b>\n<div class='watch-action'><div class='watch-position align-left'><div class='action-like'><a class='lbg-style2 like-4245 jlk' href='javascript:void(0)' data-task='like' data-post_id='4245' data-nonce='de4404f630' rel='nofollow'><img class='wti-pixel' src='https:\/\/www.dbarj.com.br\/wp-content\/plugins\/wti-like-post\/images\/pixel.gif' title='Like' \/><span class='lc-4245 lc'>+2<\/span><\/a><\/div><\/div> <div class='status-4245 status align-left'><\/div><\/div><div class='wti-clear'><\/div>","protected":false},"excerpt":{"rendered":"<p>Those days, I was updating some of my lab environments running Oracle Database 12.1.0.2 to the 190716 quarterly update Bundle Patch. However, during the Datapatch execution phase, I was getting some ORA errors. Patch 29496791 apply (pdb CDB$ROOT): SUCCESS logfile: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/29496791\/22993732\/29496791_apply_ORCL_CDBROOT_2019Jul31_11_55_12.log (no errors) Patch 29496791 apply (pdb PDB$SEED): WITH ERRORS logfile: \/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/29496791\/22993732\/29496791_apply_ORCL_PDBSEED_2019Jul31_11_58_00.log (errors) Error at &hellip; <\/p>\n<p><a class=\"more-link btn\" href=\"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/\">Continue reading<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30],"tags":[],"class_list":["post-4245","post","type-post","status-publish","format-standard","hentry","category-data-guard-en","item-wrap"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065 - DBA - Rodrigo Jorge - Oracle Tips and Guides<\/title>\n<meta name=\"description\" content=\"What to do when Oracle Database 12.1.0.2 receives ORA-04068, ORA-04061 and ORA-04065 during 190716 quarterly Bundle Patch apply.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"DBA RJ\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/\"},\"author\":{\"name\":\"DBA RJ\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\"},\"headline\":\"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065\",\"datePublished\":\"2019-07-31T16:39:14+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/\"},\"wordCount\":125,\"commentCount\":3,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\"},\"articleSection\":[\"Data Guard\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/\",\"url\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/\",\"name\":\"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065 - DBA - Rodrigo Jorge - Oracle Tips and Guides\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#website\"},\"datePublished\":\"2019-07-31T16:39:14+00:00\",\"description\":\"What to do when Oracle Database 12.1.0.2 receives ORA-04068, ORA-04061 and ORA-04065 during 190716 quarterly Bundle Patch apply.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2019\\\/07\\\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/\",\"name\":\"DBA - Rodrigo Jorge - Oracle Tips and Guides\",\"description\":\"Blog about Databases, Security and High Availability\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\",\"name\":\"DBA RJ\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\",\"url\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\",\"contentUrl\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\",\"width\":712,\"height\":712,\"caption\":\"DBA RJ\"},\"logo\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065 - DBA - Rodrigo Jorge - Oracle Tips and Guides","description":"What to do when Oracle Database 12.1.0.2 receives ORA-04068, ORA-04061 and ORA-04065 during 190716 quarterly Bundle Patch apply.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/","twitter_misc":{"Written by":"DBA RJ","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/#article","isPartOf":{"@id":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/"},"author":{"name":"DBA RJ","@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9"},"headline":"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065","datePublished":"2019-07-31T16:39:14+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/"},"wordCount":125,"commentCount":3,"publisher":{"@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9"},"articleSection":["Data Guard"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/","url":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/","name":"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065 - DBA - Rodrigo Jorge - Oracle Tips and Guides","isPartOf":{"@id":"https:\/\/www.dbarj.com.br\/en\/#website"},"datePublished":"2019-07-31T16:39:14+00:00","description":"What to do when Oracle Database 12.1.0.2 receives ORA-04068, ORA-04061 and ORA-04065 during 190716 quarterly Bundle Patch apply.","breadcrumb":{"@id":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbarj.com.br\/en\/2019\/07\/oracle-database-proactive-patch-12-1-0-2-190716-failing-with-ora-04068-ora-04061-ora-04065\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbarj.com.br\/en\/"},{"@type":"ListItem","position":2,"name":"Oracle Database Proactive Patch 12.1.0.2.190716 failing with ORA-04068 ORA-04061 ORA-04065"}]},{"@type":"WebSite","@id":"https:\/\/www.dbarj.com.br\/en\/#website","url":"https:\/\/www.dbarj.com.br\/en\/","name":"DBA - Rodrigo Jorge - Oracle Tips and Guides","description":"Blog about Databases, Security and High Availability","publisher":{"@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbarj.com.br\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9","name":"DBA RJ","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png","url":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png","contentUrl":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png","width":712,"height":712,"caption":"DBA RJ"},"logo":{"@id":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png"}}]}},"_links":{"self":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts\/4245","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/comments?post=4245"}],"version-history":[{"count":3,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts\/4245\/revisions"}],"predecessor-version":[{"id":4248,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts\/4245\/revisions\/4248"}],"wp:attachment":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/media?parent=4245"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/categories?post=4245"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/tags?post=4245"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}