Last month I was confronted to a very interesting and strange problem while deploying a Cloud Control 12c infrastructure. One of my monitored server was a SuSE Linux Enterprise Server (SLES) 64 bits on which a 18.104.22.168 Oracle database was installed. The x86_64 cloud control 12c agent has been deployed on this server with the standard Cloud Control 12c agent deployment procedure (not the scope of this post). However despite several trials to configure the…
Troubleshooting Archives - Page 4 of 4 - Blog dbi services
During one of my recent missions I had the opportunity to install Red Hat 6.1 on a ESX Virtual Machine. During the installation process I got a strange message: “unable to read group information from repositories”. If you also encounter such a problem this article may help you..
Few days ago, I was at a customer that encountered some problems trying to restore his MySQL database. Indeed he got the following error message trying to restore his xwiki database:
mysql@dba-ecm-srv11:/ [mysqld1] mq < /MyBackupFile.sql
ERROR 2006 (HY000) at line 283: MySQL server has gone away
Oracle SQL Developer and Data Modeler are becoming more and more popular as they are both cost-free and available on many Operating Systems (Linux/Unix,Windows and Mac) with different installation types: “This zip does not include JRE” or “This zip file includes the JRE”. On linux, the choice is limited because the only version available doesn’t include Java Runtime Environment. And it’s an RPM !! So what… In this post I will provide all information required to install and run these tools on an Ubuntu machine.
A few days ago I downloaded the Cloud Control 12c binaries for Linux x86_64 from the Oracle Technet.
My friend, Hervé Schweitzer, configured an OEL 5.7 VM for test purpose and I was quite eager to install this new software. I checked the O.S settings, the required parameters, aso …, everything was fine. My OMS repository database (22.214.171.124) was ready. Unfortunately, as soon as I started the installer, it directly crashed.
Last week by a customer, we experienced an excessive redo log generation filling up rapidly the FRA (Flash/Fast Recovery Area) with archivelog files which caused the database to crash.
The Metalink note 949858.1 describes problems with 10.2.0.5 agents monitoring 11g databases – this might be the case if you have an “old” 10.2.0.5 Grid Infrastructure you did not want to upgrade yet. The 11g databases are generating errors in both the alert.log and the log.xml file. The agent 10.2.0.5 agent seems to have problem with this. This posting will show you what to do.