{"id":2218,"date":"2011-05-06T11:51:36","date_gmt":"2011-05-06T09:51:36","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/"},"modified":"2011-05-06T11:51:36","modified_gmt":"2011-05-06T09:51:36","slug":"pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/","title":{"rendered":"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ?"},"content":{"rendered":"<p>Certaines requ\u00eates DDL offrent la possibilit\u00e9 de ne pas g\u00e9n\u00e9rer des enregistrements dans les redo log via la clause NOLOGGING. Le mode nologging permet donc dans certains cas d&#8217;acc\u00e9l\u00e9rer des traitements, ceux-ci pouvant facilement \u00eatre r\u00e9cup\u00e9rables \u00e0 travers des m\u00e9canismes externes \u00e0 la base de donn\u00e9es. Ce mode peut cependant avoir des cons\u00e9quences f\u00e2cheuses comme nous allons le constater et ce pas uniquement dans le contexte de configurations comme Oracle DataGuard.<\/p>\n<p>Dans le cadre de mon activit\u00e9 de consultant, je rencontre fr\u00e9quemment des bases de donn\u00e9es qui sont en mode NOLOGGING. Quelle en est la signification et quelles peuvent \u00eatre les implications d&#8217;une telle configuration ?<\/p>\n<p>Pour r\u00e9pondre \u00e0 cette question nous allons nous int\u00e9resser au comportement d&#8217;une instance de base de donn\u00e9es en mode NOLOGGING.<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; select force_logging from v$database; \n FORCE_LOGGING\n---\n NO<\/pre>\n<p>&nbsp;<\/p>\n<p>Les tablespaces de l&#8217;instance sont eux par contre en mode LOGGING :<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; select tablespace_name , logging from dba_tablespaces;\n \n TABLESPACE_NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LOGGING\n ------------------------------\u00a0\u00a0\u00a0\u00a0\u00a0 ---------\n SYSTEM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0LOGGING\n SYSAUX\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0LOGGING\n UNDOTBS1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LOGGING\n TEMP\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NOLOGGING\n USERS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0LOGGING\n REPO_RMAN\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0LOGGING\n REPO_RMAN2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LOGGING<\/pre>\n<p>Nous cr\u00e9ons une table test_redo et nous la pla\u00e7ons en mode NOLOGGING:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; create table test_redo as select * from all_objects where 1=2;\n Table created.\n \n SQL&gt; alter table test_redo nologging;\n Table altered.<\/pre>\n<p>En ins\u00e9rant des donn\u00e9es dans la table redo_test, on visualise une activit\u00e9 des redologs :<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; set autotrace on statistics;\n SQL&gt; insert into test_redo select * from all_objects;\n 71890 rows created.\n \n Statistics\n ----------------------------------------------------------\n 1527 recursive calls\n 9938 db block gets\n 50166 consistent gets\n 859 physical reads\n 8430816 redo size\n 674 bytes sent via SQL*Net to client\n 619 bytes received via SQL*Net from client\n 3 SQL*Net roundtrips to\/from client\n 1523 sorts (memory)\n 0 sorts (disk)\n 71890 rows processed<\/pre>\n<p>Si on r\u00e9alise une insertion en direct load via le hint APPEND, l&#8217;activit\u00e9 des redologs est moins importante, il y a eu beaucoup moins d&#8217;\u00e9criture dans les redologs :<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; insert \/*+ APPEND *\/ into test_redo select * from all_objects;\n \n 71890 rows created.\n \n Statistics\n ----------------------------------------------------------\n 225 recursive calls\n 1380 db block gets\n 47267 consistent gets\n 0 physical reads\n 28304 redo size\n 663 bytes sent via SQL*Net to client\n 633 bytes received via SQL*Net from client\n 3 SQL*Net roundtrips to\/from client\n 1501 sorts (memory)\n 0 sorts (disk)\n 71890 rows processed<\/pre>\n<p>Si nous interrogeons la vue v$datafile, nous pouvons visualiser qu&#8217;il y a eu une activit\u00e9 qui n&#8217;a pas \u00e9t\u00e9 \u00e9crite dans les redologs :<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; SELECT NAME, UNRECOVERABLE_CHANGE#, \n 2\u00a0\u00a0\u00a0 TO_CHAR (UNRECOVERABLE_TIME,'DD-MON-YYYY HH:MI:SS') \n 3\u00a0\u00a0\u00a0\u00a0FROM V$DATAFILE; \n \n NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0UNRECOVERABLE_CHANGE# TO_CHAR(UNRECOVERABLE_TIME \n \/u01\/database\/DB112\/system01.dbf\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 0 \n \/u01\/database\/DB112\/sysaux01.dbf\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a00 \n \/u01\/database\/DB112\/undotbs01.dbf\u00a0\u00a0\u00a0\u00a0\u00a0 0 \n \/u01\/database\/DB112\/users01.dbf\u00a0\u00a0 2048947\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 18-APR-2011 05:07:10<\/pre>\n<p>A pr\u00e9sent, restaurons l&#8217;instance de base de donn\u00e9es \u00e0 un instant t post\u00e9rieur \u00e0 l&#8217;insertion en direct load, ces donn\u00e9es ne seront pas restaur\u00e9es un message de bloc corrompu apparaitra :<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; select count(*) from redo_test; \n select count(*) from redo_test \n * \n ERROR at line 1: \n ORA-01578: ORACLE data block corrupted (file # 4, block # 1410) \n ORA-01110: data file 4: '\/u01\/database\/DB112\/users01.dbf' \n ORA-26040: Data block was loaded using the NOLOGGING option<\/pre>\n<p>Les op\u00e9rations en nologging sont plus rapides puisqu&#8217;il n&#8217;y a pas d&#8217;\u00e9criture dans les redologs :<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; set timing on \n SQL&gt; create table redo_test as select * from all_objects where 1=2; \n Table created. \n Elapsed: 00:00:01.29 \n \n SQL&gt; create table redo_test_nolog nologging as select * from all_objects where 1=2; \n Table created. \n Elapsed: 00:00:00.56 \n \n SQL&gt; insert into redo_test select * from all_objects; \n 71892 rows created. \n Elapsed: 00:00:05.58 \n \n SQL&gt; insert \/* +APPEND *\/ into redo_test_nolog select * from all_objects; \n 71892 rows created. \n Elapsed: 00:00:03.62<\/pre>\n<p>Regardons maintenant si une table cr\u00e9\u00e9e en mode NOLOGGING a des cons\u00e9quences sur toutes les op\u00e9rations DML. Nous allons d\u00e9truire toutes les lignes de la table redo_test_nolog et effectuer un rollback :<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; create table redo_test_nolog nologging as select * from all_objects; \n Table created. \n \n SQL&gt; delete from redo_test_nolog; \n 71892 rows deleted. \n \n SQL&gt; rollback; \n Rollback complete. \n \n SQL&gt; select count(*) from redo_test_nolog; \n COUNT(*) \n \n 71892<\/pre>\n<p>Comme pr\u00e9cis\u00e9 dans la documentation Oracle :<\/p>\n<p>&#8220;The NOLOGGING clause also specifies that subsequent direct loads using SQL*Loader and direct load INSERT operations are not logged. Subsequent DML statements (UPDATE, DELETE, and conventional path insert) are unaffected by the NOLOGGING attribute of the table and generate redo.&#8221;<\/p>\n<p>En r\u00e9sum\u00e9 les op\u00e9rations en nologging peuvent faire gagner du temps, mais il faut \u00eatre conscient du risque pris lors de telles op\u00e9rations. Toute op\u00e9ration effectu\u00e9e en direct load insert implique n\u00e9cessairement un backup de l&#8217;instance.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Certaines requ\u00eates DDL offrent la possibilit\u00e9 de ne pas g\u00e9n\u00e9rer des enregistrements dans les redo log via la clause NOLOGGING. Le mode nologging permet donc dans certains cas d&#8217;acc\u00e9l\u00e9rer des traitements, ceux-ci pouvant facilement \u00eatre r\u00e9cup\u00e9rables \u00e0 travers des m\u00e9canismes externes \u00e0 la base de donn\u00e9es. Ce mode peut cependant avoir des cons\u00e9quences f\u00e2cheuses comme nous allons le constater et ce pas uniquement dans le contexte de configurations comme Oracle DataGuard.<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[198],"tags":[267,236],"type_dbi":[],"class_list":["post-2218","post","type-post","status-publish","format-standard","hentry","category-database-management","tag-force-logging","tag-oracle-data-guard"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.5) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Pourquoi mettre une base de donn\u00e9es Oracle en force logging ? - dbi Blog<\/title>\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.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ?\" \/>\n<meta property=\"og:description\" content=\"Certaines requ\u00eates DDL offrent la possibilit\u00e9 de ne pas g\u00e9n\u00e9rer des enregistrements dans les redo log via la clause NOLOGGING. Le mode nologging permet donc dans certains cas d&#039;acc\u00e9l\u00e9rer des traitements, ceux-ci pouvant facilement \u00eatre r\u00e9cup\u00e9rables \u00e0 travers des m\u00e9canismes externes \u00e0 la base de donn\u00e9es. Ce mode peut cependant avoir des cons\u00e9quences f\u00e2cheuses comme nous allons le constater et ce pas uniquement dans le contexte de configurations comme Oracle DataGuard.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2011-05-06T09:51:36+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\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.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ?\",\"datePublished\":\"2011-05-06T09:51:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/\"},\"wordCount\":436,\"commentCount\":0,\"keywords\":[\"Force logging\",\"Oracle Data Guard\"],\"articleSection\":[\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/\",\"name\":\"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2011-05-06T09:51:36+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/oracle-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ? - dbi Blog","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.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/","og_locale":"en_US","og_type":"article","og_title":"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ?","og_description":"Certaines requ\u00eates DDL offrent la possibilit\u00e9 de ne pas g\u00e9n\u00e9rer des enregistrements dans les redo log via la clause NOLOGGING. Le mode nologging permet donc dans certains cas d'acc\u00e9l\u00e9rer des traitements, ceux-ci pouvant facilement \u00eatre r\u00e9cup\u00e9rables \u00e0 travers des m\u00e9canismes externes \u00e0 la base de donn\u00e9es. Ce mode peut cependant avoir des cons\u00e9quences f\u00e2cheuses comme nous allons le constater et ce pas uniquement dans le contexte de configurations comme Oracle DataGuard.","og_url":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/","og_site_name":"dbi Blog","article_published_time":"2011-05-06T09:51:36+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ?","datePublished":"2011-05-06T09:51:36+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/"},"wordCount":436,"commentCount":0,"keywords":["Force logging","Oracle Data Guard"],"articleSection":["Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/","url":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/","name":"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2011-05-06T09:51:36+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/pourquoi-mettre-une-base-de-donnes-oracle-en-force-logging\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Pourquoi mettre une base de donn\u00e9es Oracle en force logging ?"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2218","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=2218"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2218\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=2218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=2218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=2218"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=2218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}