On this article we are going to do a silent install of Oracle Enterprise Manager Clod Control 24ai on a Oracle Linux 8 server.First we need an oracle DB where the repository will run. You can use a non-cdb, but since starting from 26ai, CBD/PDB is a must, we are going to use a 19c... » read more
We had someone complaining saying why v$flash_recovery_area_usage is empty when DB is in archive log mode? Should not list everything there? This has been replicated on 26ai, but it is valid on previous releases. Answer is simple, log_archive_dest_1 is not set properly, lets replicate on a test db…. Initially ok, right? well….. Since this is... » read more
On this activity we are going to create a DB in silent mode on a single server with ASM (GRID). That’s it! For a list of 26ai articles, go to HERE
On this activity we are going to rename the scan name on a Oracle 19c RAC environment.We don’t want to change the IP’s, just the name. ORIGINAL NAME: CLUSTER-ORA-SCAN2 TARGET NAME: CLUSTER-ORA2-SCAN First, you need to make sure new SCAN NAME is pingable from all RAC servers (to avoid name resolution issues) 1:- Check current... » read more
Since there is not much out there in terms and easy guide to follow, on this activity we are going to configure an Oracle RAC cluster to allow TLS encrypted connections.Because SCAN listeners redirect you to the local listeners on each server, we also need to setup the local listeners. Here we are going to... » read more
Today after patching our databases, datapatch was failing with these errors: I found few suggestions of deinstall/reinstall OLAP, run few scripts, etc etc, all very destructive. At the end, issue was just a missing grant: So the fix was just: After this, datapatch runs ok:
After applying the binaries for RU 19.28 (Jul 25), we had datapatch failing with this error: There was nothing very clear on PDB_PLUG_IN_VIOLATIONS, but checking DB alert log, we could see this error on PDB$SEED: After we added a temp file, datapatch ran without issues.
This exact scenario is on a Solaris sparc server without GI/HAS where we upgraded from 19.27 to 19.28. and a DB with CDB/PDB’s. Binary patching all went ok as expected: But at the time of running datapatch, it fails with this error: Nothing really clear on PDB_PLUG_IN_VIOLATIONS: Issue looks very similar to “19.28 OJVMRU Datapatch... » read more
Recently we had some issues running opatchauto analyze failing with this error: We even had error running any opatch command: Since we wanted to automate the process of patching doing it hands off, we wanted to rely on opatchauto so created an SR, on which after suggesting not great options (like copy the inventory from... » read more
This is an easy one, but really helpful when you are on a server with a few DB’s and you want the visual piece of mind you are not doing something on the wrong database. Add the following line on file $ORACLE_HOME/sqlplus/admin/glogin.sql That’s it, now try to access DB: