On one of my Exadata Cloud at Customer system, I recently had an issue which required to check exactly which files were updated when upgrading the cloud-specific tooling included on Exadata Cloud at Customer, also know as
Continue reading “Exadata Cloud at Customer : Drill down into Cloud Tooling RPM content”
dbaastools_exa. I needed to know if a configuration file had been overwritten or not, when upgrading
dbaastools_exa. My knowledge in RPM packages being very limited, I did some research and here is what I found :
There is a very handy new command available in Oracle Data Guard Broker 18c. Too bad I discovered it AFTER I solved my problem 😉
This quick blog post demonstrates what can be easily spotted with this new
VALIDATE NETWORK CONFIGURATION command.
In this example, I have 2 sites, each with a 2-node Oracle 18.6 Grid Infrastructure cluster. On both clusters, there is an Oracle 18.6 RAC database.
The primary database on site 1 is called
tool, and the standby database on site 2 is called
opeth. Both RAC databases have 2 instances.
I had trouble setting a correct Oracle Data Guard configuration between database
Continue reading “Oracle Data Guard Broker 18 : new VALIDATE NETWORK CONFIGURATION command”
tool and database
(Photo by Joël Assuied, on Unsplash)
I just started working on Exadata Cloud at Customer. And with this, come my first mistakes 😉
One of my compute node had all cloud tooling scripts located in the adequate directories :
# ls -l /var/opt/oracle/exapatch/
-r-xr-xr-x 1 oracle oinstall 0 Feb 4 21:23 exadbcpatchsm
-r-xr-xr-x 1 oracle oinstall 0 Feb 4 21:23 exadbcpatchmulti
-r-xr-xr-x 1 oracle oinstall 0 Feb 4 21:23 exadbcpatch
but for an obscure reason (made of failed update combined with full filesystem), they were all emtpy.
Continue reading “Exadata Cloud at Customer : Reinstall Cloud Tooling”
(Photo by Alex Guillaume, on Unsplash)
I recently encountered a problem, for which I do not have any clue yet. But at least, I have a workaround. The goal of this blog post is to remember the exploration towards this workaround. And then to switch back to a normal sitution when possible.
For some reason, 120 development databases were configured to use Shared Server Architecture. The day after this change of configuration, a lot of users started complaining about a fully-automatized-0-problem-encountered-in-the-last-2-years-procedure to duplicate a production database to development database … Indeed, this procedure begins with stopping target database, and this day, failed almost everytime during this step … Why ?
Continue reading “Fun with attribute STOP_TIMEOUT for a custom clusterware resource”
(Photo by Alfons Morales, on Unsplash)
There are several ways to dig for precious information in listener logs, for example this method described by Arup Nanda or this one by Liron Amitzi.
I currently work in an environment with 40+ servers and 550+ databases managed by Grid Infrastructure. I recently wanted to help a colleague who was experiencing problems with a brand new installed application. Her application should connect to a database in another VLAN. Our first intuition was to check if the application could, at least, reach the database. Since the database resides on a Grid Infrastructure cluster, it would have been tedious to check all (scan-) listener logs spread accross all servers. This is where Splunk has proven useful.
Continue reading “Use of Splunk with Oracle listener log files”
(Photo by Johannes Plenio, on Unsplash)
Conferences are great. Not only for the technical content, also for the people. Recently during DOAG, I had very interesting conversations (yes, several conversations 🙂 ) with Martin Berger about how to control who is connecting to which database in a complex environment. Among other topics, we mentioned that it was possible, starting with Oracle 12.2, to set Access Control Lists to allow connections to a database service (in Non-CDB or PDB) from specific IP addresses.
This new feature Database Service Firewall was introduced with Oracle 12.2. It should not to be confused with Database Firewall, which is a dedicated system used to monitor traffic from and to databases, and is part of Oracle Audit Vault and Database Firewall product.
As I never used Database Service Firewall, I decided to give it a try in a Multitenant environment with RAC.
My lab is a 2-node RAC cluster with Grid Infrastructure 18, a 18.3 RAC Container database called
metal, and one pluggable database called
Continue reading “Database Service Firewall : Access Control to a PDB in RAC”
(Picture by Rodion Kutsaev, via Unsplash)
I like CLIs. I really like CLIs. Especially when 90% of my previous and quite long blog post can be summarized with only 3 commands 🙂
It was about creating restricted read only access for users, using a role and a named credential. But EM CLI can greatly simplify this task. To better understand what follows, please read the previous post explaining how to Create READ ONLY + AWR access on database targets in Oracle Enterprise Manager 220.127.116.11 first.
Continue reading “Create READ ONLY + AWR access on database targets in Oracle Enterprise Manager 18.104.22.168 – EM CLI edition”