Using SEHA Features in EE
Here is a short demonstration how to make use of the Standard Edition High Availability (SEHA) cold failover feature in Enterprise Edition (EE).
Here is a short demonstration how to make use of the Standard Edition High Availability (SEHA) cold failover feature in Enterprise Edition (EE).
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.