Infrastructure at your Service
Introduction I’ve been dreaming of this kind of feature: just because most of the ODA configurations now include Disaster Recovery capabilities, through Data Guard or Dbvisit standy. If Dbvisit will obviously never be integrated to odacli, the lack of Data Guard features is now solved by the very latest 19.8 ODA software appliance kit. How Data Guard was implemented before 19.8? Those who have been using ODA and Data Guard for a while know that…
The ODA software 19.6 is released and people are starting to patch. A direct patch to version 19.6 is possible from version 18.8. Before patching your deployment to Oracle Database Appliance release 19.6, you must upgrade the operating system to Oracle Linux 7. In this blog I am describing the steps I follow when patching an ODA from 18.8 to 19.6. I am using an ODA X7-2 (one node) The first step is of course…
During ODA deployment I could see that starting 18.7, immediately after reimaging or patching the ODA, I was getting some regular errors in the root mail box. The error message came every hour at 13 minutes and 43 minutes.
Recently I had to add some storage on an ODA X8-2M that I deployed early February. At that time the last available release was ODA 18.7. In this post I would like to share my experience and the challenge I could face.
Introduction With the latest ODA X8 range, at least 80% of the customers could find an ODA configuration that fits their needs. For the others, either they can’t afford it, either they are already in the Cloud, or they need extremely large storage or EXADATA performance. Among these 80% of customers, only a few choose ODA. Let’s see how Oracle could improve the ODA to make it a must. 1) Make robust and reliable releases…
I have recently faced an issue deleting database on an ODA. I was getting following error whatever database I wanted to delete : DCS-10001:Internal error encountered: null. Through this blog, I would like to share with you my experience on this case hoping it will help you if you are facing same problem. On this project I was using ODA Release 18.5 and 18.8 and faced the same problem on both versions. On 18.3 and…
During a past project, we were using ODA X8-2M with one additional network card. As per my knowledge, on an appliance, additional cards are used to extend connectivity to additional network. Customer was really enforcing to have network redundancy between the 2 cards. I then took opportunity for some tests. In this post, I would like to share my experience on these tests and how to properly configure network card extension on an ODA.
Introduction If you’re considering ODA for your next platform, you surely already appreciate the simplicity of the offer. 3 models with few options, this is definitely easy to choose from. One of the other benefit is also the hardware support of 5 years, and combined with software updates generally available for up to 7 years old ODAs, you can keep your ODA running even longer for non-critical databases and/or if you have a strong Disaster…
Introduction It’s been 1 year now that 19c is available on-premise. Finally, 19c is now available today on ODA too, in a real production release. Let’s have a glance of what’s inside. Is 19.6 available for my old ODA? The 19.6 release, like most recent releases, is the same for all ODAs. But oldest ODAs will not support it. First-gen ODA (now 8 years old), X3-2 (7yo) and X4-2 (6yo) won’t support this very latest…
Introduction 19c will soon be available for your ODAs. But you may not be ready. Here is how to patch your ODA from 18.3 to 18.8, the very latest 18c release. This patch has here been applied on X7-2M hardware. Download the patch files Patch number is 30518425. This patch is composed of 2 zipfiles you will copy on your ODA. Check free space on disk Applying a patch requires several GB, please check free…
