{"id":2783,"date":"2011-07-08T08:49:30","date_gmt":"2011-07-08T07:49:30","guid":{"rendered":"http:\/\/blog.capdata.fr\/?p=2783"},"modified":"2019-09-13T14:37:26","modified_gmt":"2019-09-13T13:37:26","slug":"comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/","title":{"rendered":"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation"},"content":{"rendered":"\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>

M\u00e9canisme\u00a0:<\/span><\/strong><\/p>\n

<\/span><\/p>\n

Le moteur oracle met en \u0153uvre un m\u00e9canisme de journalisation via les fichiers redo logs afin d\u2019enregistrer toutes les modifications apport\u00e9es \u00e0 la base de donn\u00e9es. Ceux-ci sont organis\u00e9s en groupes qui vont \u00eatre \u00e9crits de mani\u00e8re circulaire, c’est-\u00e0-dire \u00e9cras\u00e9s \u00e0 intervalle plus ou moins r\u00e9gulier.<\/p>\n

Ils sont primordiaux pour la restauration de l\u2019instance dans le cas d\u2019un arr\u00eat anormal ou pour la restauration de m\u00e9dia si un fichier de donn\u00e9es est corrompu ou tout simplement perdu. Coupl\u00e9s \u00e0 une sauvegarde de fichiers de donn\u00e9es, ils permettent donc de rejouer l\u2019int\u00e9gralit\u00e9 des changements survenus entre la sauvegarde et l\u2019incident.<\/p>\n

Les fichiers de journalisation se composent d\u2019au minimum deux groupes constitu\u00e9s chacun d\u2019un ou\u00a0 plusieurs membres. Ainsi les membres d\u2019un m\u00eame groupe vont \u00eatre \u00e9crits de mani\u00e8re simultan\u00e9e par l\u2019instance via le processus LGWR (logwriter) et contenir exactement les m\u00eames donn\u00e9es. Cette mise en miroir appel\u00e9e \u00e9galement multiplexage permet de diminuer les risques en cas de perte de fichiers. C\u2019est pourquoi il est conseill\u00e9 de positionner les redo logs sur des espaces physiques diff\u00e9rents. Tous les membres d\u2019un groupe ont la m\u00eame taille d\u00e9finie lors de leur cr\u00e9ation et celle-ci reste fixe. Il faut \u00e9galement savoir que le nombre de groupes n\u2019augmente pas dynamiquement. Ainsi lorsqu\u2019il n\u2019est plus possible d\u2019\u00e9crire dans un groupe qui est plein Oracle passe au groupe suivant et ainsi de suite jusqu\u2019au dernier. L\u2019\u00e9criture d\u2019un fichier \u00e0 un autre se nomme basculement (switch). Puis il va repasser au premier, d\u2019o\u00f9 la notion de circularit\u00e9, en \u00e9crasant toutes les informations qui y sont stock\u00e9es. Elles ne seront donc plus disponibles lors par exemple, d\u2019une restauration de m\u00e9dia. Pour garantir cela il faut donc activer le m\u00e9canisme d\u2019archivage, qui comme son nom l\u2019indique, permet d\u2019archiver les fichiers de journalisation d\u00e8s lors qu\u2019ils sont pleins avant qu\u2019ils ne soient r\u00e9utilis\u00e9s.<\/p>\n

<\/span><\/p>\n

Probl\u00e9matique\u00a0:<\/span><\/strong><\/p>\n

<\/span><\/p>\n

Toute la probl\u00e9matique se situe donc dans le simple fait de parvenir \u00e0 dimensionner correctement la taille des fichiers de journalisation et avoir le bon nombre de groupes.<\/p>\n

Cependant l\u2019objectif reste simple\u00a0:<\/p>\n

Avoir une taille de fichiers de journalisation suffisamment grande dans le but d\u2019\u00e9viter des basculements trop fr\u00e9quents qui seraient p\u00e9nalisants pour les performances. Sans perdre de vue qu\u2019avoir des basculements peu fr\u00e9quents et donc des points de reprise peu fr\u00e9quents pourraient dans certain cas allonger la dur\u00e9e de r\u00e9cup\u00e9ration de l\u2019instance et donc la dur\u00e9e de red\u00e9marrage lors d\u2019un arr\u00eat anormal. Il faut donc trouver le juste milieu entre bonne performance en fonctionnement normal mais \u00e9galement en cas de dysfonctionnement.<\/p>\n

Utiliser un nombre de groupes suffisamment important afin de permettre aux points de reprise et \u00e0 l\u2019archivage de se terminer avant que l\u2019instance ne revienne sur un fichier de journalisation et \u00e9crase les informations. Si ce n\u2019est pas le cas le processus LGWR est en attente d\u00e9gradant ainsi les performances.<\/p>\n

<\/span><\/p>\n

Analyse: <\/span><\/strong><\/p>\n

<\/span><\/p>\n

La premi\u00e8re chose \u00e0 faire est d\u2019analyser le fichier d\u2019alerte de l\u2019instance afin d\u2019auditer de mani\u00e8re simple l\u2019activit\u00e9 des fichiers de journalisation.<\/p>\n

Voici donc les trois types d\u2019informations \u00e0 surveiller\u00a0:<\/p>\n

– Basculement d\u2019un fichier de journalisation \u00e0 un autre<\/p>\n

Mon Jul 04 10:08:05 2011<\/em><\/pre>\n
Thread 1 advanced to log sequence 50<\/em><\/pre>\n
Current log# 2 seq# 50 mem# 0: E:\\ORADATA\\DBVC\\REDO02A.RDO <\/em><\/pre>\n
Current log# 2 seq# 50 mem# 1: D:\\ORADATA\\DBVC\\REDO02B.RDO<\/em><\/pre>\n
– Attente lors d\u2019un basculement\u00a0: Point de reprise non termin\u00e9<\/p>\n
Thu Jul 07 10:42:25 2011<\/em><\/pre>\n
Thread 1 cannot allocate new log, sequence 56<\/em><\/pre>\n
Checkpoint not complete<\/em><\/pre>\n
 <\/em><\/p>\n
– Attente lors d\u2019un basculement\u00a0: Archivage non termin\u00e9<\/p>\n
Thu Jul 07 10:42:25 2011<\/em><\/pre>\n
Thread 1 cannot allocate new log, sequence 57<\/em><\/pre>\n
All online logs needed archiving<\/em><\/pre>\n
 <\/em><\/p>\n
Ensuite il est bon de v\u00e9rifier la mani\u00e8re dont sont organis\u00e9s les redo logs en se connectant \u00e0 l\u2019instance, via par exemple\u00a0 sqlplus:<\/p>\n
SQL> select *from v$log;<\/em><\/pre>\n
 GROUP#\u00a0\u00a0\u00a0 THREAD#\u00a0 SEQUENCE#\u00a0\u00a0\u00a0\u00a0\u00a0 BYTES\u00a0\u00a0\u00a0 MEMBERS ARC STATUS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 FIRST_CHANGE# FIRST_TIM\r\n---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------\r\n1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\u00a0\u00a0\u00a0\u00a0\u00a0 12364\u00a0 419430400\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2 NO\u00a0 CURRENT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 530717709 18-MAY-11\r\n2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\u00a0\u00a0\u00a0\u00a0\u00a0 12363\u00a0 419430400\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2 NO\u00a0 ACTIVE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 530642826 18-MAY-11\r\n3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\u00a0\u00a0\u00a0\u00a0\u00a0 12362\u00a0 419430400\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2 NO\u00a0 INACTIVE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0530562254 18-MAY-11<\/em><\/pre>\n
 <\/em><\/p>\n
Ici l\u2019on interroge la vue v$log, o\u00f9 l\u2019on constate que l\u2019on dispose de trois groupes de fichiers de 400 Mo chacun. Le groupe N\u00b01 \u00e9tant celui en cours d\u2019utilisation par l\u2019instance.<\/p>\n
 <\/em><\/p>\n
SQL> select * from v$logfile order by group#;<\/em><\/pre>\n
 GROUP# STATUS\u00a0 TYPE\u00a0\u00a0\u00a0 MEMBER\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\u00a0\u00a0 IS_\r\n---------- ------- ------- ---------------------------------------- ---\r\n1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ONLINE\u00a0 D:\\ORADATA\\DBVC\\REDO01A.RDO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO\r\n1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ONLINE\u00a0 F:\\ORADATA\\DBVC\\REDO01B.RDO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO\r\n2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ONLINE\u00a0 E:\\ORADATA\\DBVC\\REDO02A.RDO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO\r\n2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ONLINE\u00a0 D:\\ORADATA\\DBVC\\REDO02B.RDO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO\r\n3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ONLINE\u00a0 F:\\ORADATA\\DBVC\\REDO03A.RDO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO\r\n3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ONLINE\u00a0 E:\\ORADATA\\DBVC\\REDO03B.RDO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO<\/em><\/pre>\n
Ici l\u2019on interroge la vue v$logfile o\u00f9 l\u2019on voit que chaque groupe est compos\u00e9 de deux membres. Chaque membre \u00e9tant positionn\u00e9 sur un disque physique distinct.<\/p>\n
 <\/em><\/p>\n
SQL> select * from v$loghist;<\/em><\/pre>\n
THREAD#\u00a0 SEQUENCE# FIRST_CHANGE# FIRST_TIME SWITCH_CHANGE#\r\n---------- ---------- ------------- ------------------- --------------<\/em><\/pre>\n
1\u00a0\u00a0 \u00a012247\u00a0\u00a0 \u00a0523471807\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a00:11:07\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523552937\r\n1\u00a0\u00a0 \u00a012248\u00a0\u00a0 \u00a0523552937\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a00:26:08\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523634497\r\n1\u00a0\u00a0 \u00a012249\u00a0\u00a0 \u00a0523634497\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a00:46:07\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523650275\r\n1\u00a0\u00a0 \u00a012250\u00a0\u00a0 \u00a0523650275\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a01:11:08\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523746442\r\n1\u00a0\u00a0 \u00a012251\u00a0\u00a0 \u00a0523746442\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a01:26:08\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523817931\r\n1\u00a0\u00a0 \u00a012252\u00a0\u00a0 \u00a0523817931\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a01:43:10\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523844135\r\n1\u00a0\u00a0 \u00a012253\u00a0\u00a0 \u00a0523844135\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a02:07:33\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523925461\r\n1\u00a0\u00a0 \u00a012254\u00a0\u00a0 \u00a0523925461\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a02:26:08\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0523985782\r\n1\u00a0\u00a0 \u00a012255\u00a0\u00a0 \u00a0523985782\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a02:42:57\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524023131\r\n1\u00a0\u00a0 \u00a012256\u00a0\u00a0 \u00a0524023131\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a03:06:09\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524118467\r\n1\u00a0\u00a0 \u00a012257\u00a0\u00a0 \u00a0524118467\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a03:23:03\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524159631\r\n1\u00a0\u00a0 \u00a012258\u00a0\u00a0 \u00a0524159631\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a03:42:51\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524216095\r\n1\u00a0\u00a0 \u00a012259\u00a0\u00a0 \u00a0524216095\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a04:04:04\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524297285\r\n1\u00a0\u00a0 \u00a012260\u00a0\u00a0 \u00a0524297285\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a04:21:50\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524330560\r\n1\u00a0\u00a0 \u00a012261\u00a0\u00a0 \u00a0524330560\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a04:42:45\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524393688\r\n1\u00a0\u00a0 \u00a012262\u00a0\u00a0 \u00a0524393688\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a05:01:10\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524491001\r\n1\u00a0\u00a0 \u00a012263\u00a0\u00a0 \u00a0524491001\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a05:21:08\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524506409\r\n1\u00a0\u00a0 \u00a012264\u00a0\u00a0 \u00a0524506409\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a05:42:36\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524587362\r\n1\u00a0\u00a0 \u00a012265\u00a0\u00a0 \u00a0524587362\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a06:01:08\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524668639\r\n1\u00a0\u00a0 \u00a012266\u00a0\u00a0 \u00a0524668639\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a06:16:25\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524684295\r\n1\u00a0\u00a0 \u00a012267\u00a0\u00a0 \u00a0524684295\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a06:41:46\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524764738\r\n1\u00a0\u00a0 \u00a012268\u00a0\u00a0 \u00a0524764738\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a06:59:28\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524861296\r\n1\u00a0\u00a0 \u00a012269\u00a0\u00a0 \u00a0524861296\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a07:16:10\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524877473\r\n1\u00a0\u00a0 \u00a012270\u00a0\u00a0 \u00a0524877473\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a07:41:13\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0524958651\r\n1\u00a0\u00a0 \u00a012271\u00a0\u00a0 \u00a0524958651\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a07:56:14\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0525040362\r\n1\u00a0\u00a0 \u00a012272\u00a0\u00a0 \u00a0525040362\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a08:16:10\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0525056411\r\n1\u00a0\u00a0 \u00a012273\u00a0\u00a0 \u00a0525056411\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a08:41:11\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0525137127\r\n1\u00a0\u00a0 \u00a012274\u00a0\u00a0 \u00a0525137127\u00a0\u00a0 \u00a017\/05\/2011\u00a0\u00a0 \u00a08:56:15\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0525233811<\/em><\/pre>\n
On peut \u00e9galement interroger la vue v$loghist o\u00f9 l\u2019on peut ici constater qu\u2019il y a un switch log toutes les 15\/25 min environ, ce qui reste correct.<\/p>\n
\n
Il faut donc comprendre que si la dur\u00e9e qui s\u00e9pare les messages d\u2019alerte de type \u00ab\u00a0Basculement d\u2019un fichier de journalisation \u00e0 un autre\u00a0\u00bb est courte, les fichiers sont mal dimensionn\u00e9s. Il faudra donc veiller \u00e0 les agrandir. C’est-\u00e0-dire supprimer les membres non actifs pour les recr\u00e9er de taille plus importante. Si ce message d\u2019alerte n\u2019apparait que de mani\u00e8re occasionnelle (par exemple une fois par jour) c\u2019est que les fichiers sont correctement taill\u00e9s.<\/p>\n
Si il y a beaucoup de messages d\u2019alertes au niveau des attentes (Checkpoint not complete \/ All online logs needed archiving) il faudra veiller \u00e0 ajouter un groupe de fichier. En effet de cette mani\u00e8re le processus LGWR mettra plus de temps \u00e0 effectuer le tour complet des fichiers de journalisation et permettra donc au point de reprise ou \u00e0 l\u2019archivage de se terminer correctement sans attente.<\/p>\n\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"
M\u00e9canisme\u00a0: Le moteur oracle met en \u0153uvre un m\u00e9canisme de journalisation via les fichiers redo logs afin d\u2019enregistrer toutes les modifications apport\u00e9es \u00e0 la base de donn\u00e9es. Ceux-ci sont organis\u00e9s en groupes qui vont \u00eatre \u00e9crits de mani\u00e8re circulaire, c’est-\u00e0-dire… Continuer la lecture →<\/span><\/a><\/p>\n","protected":false},"author":23,"featured_media":7913,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-2783","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oracle"],"yoast_head":"\nCheckpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation - Capdata TECH 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:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"M\u00e9canisme\u00a0: Le moteur oracle met en \u0153uvre un m\u00e9canisme de journalisation via les fichiers redo logs afin d\u2019enregistrer toutes les modifications apport\u00e9es \u00e0 la base de donn\u00e9es. Ceux-ci sont organis\u00e9s en groupes qui vont \u00eatre \u00e9crits de mani\u00e8re circulaire, c’est-\u00e0-dire… Continuer la lecture →\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2011-07-08T07:49:30+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-09-13T13:37:26+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2011\/07\/checkpoiny.png\" \/>\n\t<meta property=\"og:image:width\" content=\"674\" \/>\n\t<meta property=\"og:image:height\" content=\"398\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Louis PROU\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Louis PROU\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/\"},\"author\":{\"name\":\"Louis PROU\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9\"},\"headline\":\"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation\",\"datePublished\":\"2011-07-08T07:49:30+00:00\",\"dateModified\":\"2019-09-13T13:37:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/\"},\"wordCount\":881,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"articleSection\":[\"Oracle\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/\",\"name\":\"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2011-07-08T07:49:30+00:00\",\"dateModified\":\"2019-09-13T13:37:26+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.capdata.fr\/#website\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"name\":\"Capdata TECH BLOG\",\"description\":\"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting\",\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.capdata.fr\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.capdata.fr\/#organization\",\"name\":\"Capdata TECH BLOG\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"contentUrl\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"width\":800,\"height\":254,\"caption\":\"Capdata TECH BLOG\"},\"image\":{\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9\",\"name\":\"Louis PROU\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/lprou\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation - Capdata TECH 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:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/","og_locale":"fr_FR","og_type":"article","og_title":"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation - Capdata TECH BLOG","og_description":"M\u00e9canisme\u00a0: Le moteur oracle met en \u0153uvre un m\u00e9canisme de journalisation via les fichiers redo logs afin d\u2019enregistrer toutes les modifications apport\u00e9es \u00e0 la base de donn\u00e9es. Ceux-ci sont organis\u00e9s en groupes qui vont \u00eatre \u00e9crits de mani\u00e8re circulaire, c’est-\u00e0-dire… Continuer la lecture →","og_url":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2011-07-08T07:49:30+00:00","article_modified_time":"2019-09-13T13:37:26+00:00","og_image":[{"width":674,"height":398,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2011\/07\/checkpoiny.png","type":"image\/png"}],"author":"Louis PROU","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Louis PROU","Dur\u00e9e de lecture estim\u00e9e":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/"},"author":{"name":"Louis PROU","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9"},"headline":"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation","datePublished":"2011-07-08T07:49:30+00:00","dateModified":"2019-09-13T13:37:26+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/"},"wordCount":881,"commentCount":0,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"articleSection":["Oracle"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/","url":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/","name":"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2011-07-08T07:49:30+00:00","dateModified":"2019-09-13T13:37:26+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/comment-limiter-les-alertes-liees-a-la-journalisation-checkpoint-not-completed-et-compagnie\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"Checkpoint not complete: Comment limiter les alertes li\u00e9es \u00e0 la journalisation"}]},{"@type":"WebSite","@id":"https:\/\/blog.capdata.fr\/#website","url":"https:\/\/blog.capdata.fr\/","name":"Capdata TECH BLOG","description":"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting","publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.capdata.fr\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/blog.capdata.fr\/#organization","name":"Capdata TECH BLOG","url":"https:\/\/blog.capdata.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/","url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","contentUrl":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","width":800,"height":254,"caption":"Capdata TECH BLOG"},"image":{"@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9","name":"Louis PROU","url":"https:\/\/blog.capdata.fr\/index.php\/author\/lprou\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/2783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=2783"}],"version-history":[{"count":12,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/2783\/revisions"}],"predecessor-version":[{"id":2785,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/2783\/revisions\/2785"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/7913"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=2783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=2783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=2783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}