I got this error while trying to perform an import from another 19c database but apparently with a higher TZ version: The solution is to perform the TZ upgrade of the database. Check the current time zone version: Let’s see what’s the latest time zone to which we can upgrade to: We can see that…
It’s not something new in 19c, however, this feature has been improved and covers all the steps that a DBA must do or was supposed to do in the past in order to recover a lagging standby. I will simulate it and this is my setup: I have created a dataguard environment using Vagrant. The…
I know is not the most optimized Vagrantfile written out there but, I’m going to post only the Vagrantfile for the moment and soon I will upload also the files used to create the databases and broker config: And the result would be something like this:
As I’m a huge fan of Vagrant, this is the Vagrantfile I’m using to create in 1 run 3 nodes docker environment: Let’s start the creation of the VMs and measure the execution time (in Windows 10 this time 🙂 ): Now if you want to see the status: Let’s check the docker version:
There is no excerpt because this is a protected post.
Suppose you have only AIX platform available on your EM13c and you want to deploy agents on Linux servers. This is what one needs to do: Step 1: Check the available platforms on OMS: Step 2: Login on EM13c GUI and follow the path:Setup -> Extensibility -> Self Update Step 3: Go to Agent Software…
If you want to cleanup your EM13c installation, you would like to drop EM repository information as well. This is the way to do it: Have fun!
Playing with dataguard failover scenarios I bumped into this error: That’s due to inconsistent information within the broker files from both servers. To fix this, we can do this:
One of the reasons for getting this error might be that the sqlnet.ora does not contain the proper settings like in this particular case: As you can see there is nothing set in sqlnet.ora. Therefor when I was trying to reinstate a former PRIMARY as STANDBY, I was seeing in alert log of the reinstated…
