dbi services Blog
Welcome to the dbi services Blog! This blog focuses on IT infrastructure - featuring news, troubleshooting, and tips & tricks. It covers database, middleware, and OS technologies such as Oracle, Microsoft SQL Server, Documentum, MySQL, PostgreSQL, Sybase, Unix/Linux, etc. The dbi services blog represents the view of our consultants, not necessarily that of dbi services. Feel free to comment on the postings!
Dans le cadre d'un cluster Oracle Grid Infrastructure 11g R2 utilisé pour gérer des bases de données en mode FAILOVER, j'ai été amené à me pencher sur l'algorithme de basculement d'une ressource et des paramètres le régissant.
L'objet de ce posting est de décrire la mise en place et l'utilisation d'un gestionnaire de sauvegarde pour un cluster de base postgresql. Barman - acronyme de "backup recovery manager"- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C'est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.
A few days ago we had a quick request at a customer which had to replace a voting disk in an ASM disk group. The current ASM disk group (redundancy normal) had 3 disks: Two were located in the "VE" data center and one disk in the "SH" data center. The goal of this operation was to replace one voting disk from the "VE" data center with one disk coming from a third Data Center ("SH2"). Many thanks to Antoine Marty working at this customer for having performed these steps!
Starting with MySQL 5.5 it is possible to configure semi-synchronous replication. As you probably know, MySQL replication is asynchronous by default. Asynchronous replication means that events/transactions applied on one server are not immediately applied on the other one.
Ayant rencontré récemment des problèmes de blocs corrompus sur des bases Oracle en version Oracle 10g et Oracle 11g, des différences notables sont apparues notamment au niveau de la vue v$database_block_corruption. Je vous livre dans ce post le résultat de mes tests.

Last week, I attended the Microsoft TechDays for the first time. The Swiss 2011 "edition" took place in Bern. For me this is really a new challenge because I have never worked deeply with the Microsoft database platform "SQL Server".
During our test to create a failover clustering with the new function 'AlwaysOn High Availability', we had a few difficulties to overcome like the databases restore on the secondary cluster node.
In this article, we will explain how to avoid it before encountering the problem.
Last week, I was not able to complete a backup because of the ORA-19566 error: "exceeded limit of 0 corrupt blocks". Here is what you can do to fix it.
Nowadays, MySQL Databases are encapsulated into many mission critical software solutions. Lots of companies host one or many MySQL databases in their data center, sometimes even without knowing it except when the MySQL service is not available anymore. In order to increase the service availability, it is mandatory to have a monitoring solution. Regardless of if you are using MySQL Server, MySQL replication or cluster, the Oracle/MySQL monitoring solution is called MySQL Enterprise Monitor.
I was upgrading Netbackup yesterday to version 7.0.1 and faced a quite "funny" issue with the OpsCenter. The installation failed on pre-requirements checks saying that no space was available. Nothing strange at this point...except that we still had about 79GB free space! 



Hi Arnaud,
Can I hav english version of these document.
Rgds
Raffi
Merci José pour l'astuce. J'ai pu valider "chopt", c'est pratique.