Troubleshooting
When datapatch Won’t Finish: An ORA-04021 Lock on DBMS_AQADM_SYS During a 19c RU Apply
I had one of those patching nights again last weekend — the kind where the maintenance window is booked, the...
When “Invalid Objects” Isn’t What It Looks Like: A GSMADMIN_INTERNAL Detective Story
Every DBA who has run a Release Update knows the moment. You kick off the pre-patch sanity checks, you're expecting...
Oracle RAC Node Addition Failed with INS-32156 Due to AHF Permissions
When adding a new node to an Oracle RAC cluster, the addnode.sh process can sometimes fail because of permission issues...
OPatchAuto Error Code 42: RemoteHostExecutor.pl Permission Denied During Oracle GI/RAC Patching
Oracle Grid Infrastructure patching with OPatchAuto is designed to automate rolling patch application across RAC nodes. However, incorrect file ownership...
Oracle RMAN Session Monitoring and Safely Identifying Long-Running RMAN Operations
Oracle Recovery Manager (RMAN) is one of the most important tools for protecting Oracle databases through backup and recovery. However,...
ORA-19751: Could Not Create the Change Tracking File – Solution After Database Recovery
Block Change Tracking (BCT) is a valuable Oracle feature that speeds up incremental RMAN backups by tracking changed blocks. However,...
ORA-16157: Media Recovery Not Allowed Following Successful FINISH Recovery
Oracle Data Guard provides continuous synchronization between primary and standby databases using Managed Recovery Process (MRP). However, administrators occasionally encounter...
DBD::Oracle::st bind_param failed: ORA-01652: unable to extend temp segment by 128 in tablespace TEMP (DBD ERROR: OCILobWrite in dbd_rebind_ph_lob)
Introduction During an Oracle Release Update (RU) installation, you may encounter the following error while running datapatch: DBD::Oracle::st bind_param failed:...
Oracle Datapatch Error: ‘19.31.0.0.0 Release_Update’ is installed in the CDB but ‘19.25.0.0.0 Release_Update’ is installed in the PDB – The Unexpected Root Cause
If you've recently upgraded an Oracle 19c CDB from 19.25 RU to 19.31 RU and encountered the following SQL patch...
OPatch CheckConflictAgainstOHWithDetail Shows DBWLM RU Conflict with OCW RU in Oracle GI 19.31 – Why You Can Safely Ignore It
Ran into this one during a routine GI patching cycle recently, and it's worth writing up because the output looks...
