Oracle 26ai: How to create DB in silent mode
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
Oracle 19c: Steps for modifying SCAN NAME in oracle RAC
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
TLS for Oracle Real Application Cluster (RAC)
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
Oracle 19c: Datapatch Fails with ORA-37002: Oracle OLAP failed to initialize. Please contact Oracle OLAP
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:
Oracle 19c: Datapatch fails with Unsupported named object type for bind parameter at….
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.
Oracle 19c: Datapatch Fails with ORA-29532 after applying 19.28 RU
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
Oracle 19c: opatchauto apply -analyze fails with OPATCHAUTO-68061
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
Oracle: How to change SQL*Plus prompt to show the connected user and database?
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:
Oracle 19c: Datapatch stuck: Unable to acquire sqlpatch global lock in EXCLUSIVE mode
After a session got stuck/failed or process got killed somehow, we are getting an error trying to re-run datapatch. Checking if we have a rogue process, we can see the old PID still there: We killed, but still the same,no progress. This case we had to kill the sqlpatch pid, and after this, datapatch completed... » read more
Oracle GI 19c: How to remove/drop disk in EXTERNAL redundancy
I was never 100% clear to me you could remove a disk from a diskgroup wtih EXTERNAL redundancy without having data loss, so let’s to a test. We are going to do it on Oracle GI 19c, but I don’t see why it should not work on older versions. But please always try to replicate... » read more