SQL*Plus 12.2 and searching path of login.sql
Having installed Oracle Database 12.2 on a client, I have noticed that the login.sql script, which is placed in a custom directory specified by SQLPATH, is not invoked anymore.
Oracle¶
ORA-3180 on Active Data Guard standby database
Got a call asking me to provide advice on the cause of ORA-3180 error on an Active Data Guard standby database instance
DBMS_METADATA.GET_SXML_DDL may produce incorrect DDL for trigger in EBR environment
I have recently discovered a case when DBMS_METADATA.GET_SXML_DDL returns incorrect DDL for a trigger in an EBR environment.
A lot of log.* files in dirbdb directory
After adding ENABLEMONITORING in the GLOBALS file, I noticed that the $OGG_HOME/dirbdb directory started growing.
Excluding DDL in Integrated Extract using DBMS_STREAMS_ADM.SET_TAG
A couple of months ago I had to configure an Oracle GoldenGate Integrated Extract to exclude specific DDL statements from replication.
Having worked a lot with Oracle Streams, I decided to utilize DBMS_STREAMS_ADM.SET_TAG for that task.
Incorrect handling of unused columns during GoldenGate initial load using Direct Bulk Load to SQL*Loader
Today I faced an interesting issue performing a GoldenGate initial load with a Direct Bulk Load to SQL*Loader. The issue was related to the incorrect handling of unused columns during such loads and can cause incorrect data getting loaded into a database under certain conditions.
opatch and libpicl on Solaris SPARC
This morning while applying the most recent Database Bundle Patch (DBBP) the datapatch invocation finished with an error.
Asynchronous Global Index Maintenance effects
I think Asynchronous Global Index Maintenance is one of the most exciting features in Oracle Database 12c. This post is about one particular case when that feature can cause performance issues.
ORA-8102 on ALTER TABLE SHRINK SPACE with default column optimization
Encountered ORA-8102 while executing a regular database maintenance routine.
This post analyzes the problem, builds a test case to reproduce it, and shows how the problem can be avoided.
V$SQL_PLAN_MONITOR.STARTS is higher than expected due to NLJ batching/Prefetching
Recently one of our developers asked me to explain why V$SQL_PLAN_MONITOR.STARTS is higher than expected for one particular query.