There used to be the BYPASS_UJVC hint that allowed to update a non key-preserved table.
It is still there, but it must have stopped working around 11.2.
It turns out that Oracle introduced a fix control that seems to be doing the same in 19.10.
I was applying Grid Infrastructure Jan 2021 Release Update (GI RU) 18.13.0.0.210119 to an 18c cluster the other day.
opatchauto failed with the error OPATCHAUTO-72043.
It is a widely known fact that Oracle supports a maximum size of 32,767 bytes for the VARCHAR2, NVARCHAR2, and RAW data types (Extended Data Types) provided that MAX_STRING_SIZE = EXTENDED.
What I recently discovered is that SYS can create such columns even when MAX_STRING_SIZE = STANDARD.
It is something Oracle added in one of the latest Release Updates of 19c. I believe I discovered it either in 19.7 or 19.8 originally.
Following Data Guard switchover, a pluggable database was not opened on all RAC instances. This post demonstrates the issue and the fix.
In this post, let us demonstrate how to read Amazon S3 data from Oracle Database running on a non-OCI environment.
Oracle made some interesting improvements in the Database Configuration Assistant (DBCA) in 18c simplifying the creation of a standby database, namely allowing to create a copy of a database that will be a RAC database itself regardless of what type the primary database is (e.g. single-instance/RAC/etc.). This post demonstrates this capability.
The other day I debugged some Oracle provided utilities and came across another way of determining an Oracle Database edition. It does not require a running database instance.
I came across this error while applying Database Release Update 19.7 to my RAC database.
There is a wrong results issue I stumbled upon this morning. A developer told me that one of their queries started returning wrong results after we upgraded one of our databases from 12.2.0.1 to 19.7.