When thinking of high availability for the Oracle Database, RAC and DataGuard come into our mind. But when thinking about high availability for the Standard Edition 2 (SE2) of the Oracle Database, we think about … ? Until Oracle Database 18c, we thought about RAC, too. But since Oracle 19c, there’s SEHA – “Standard Edition High Availability”. What is this feature about, what are the restrictions and how to configure a database for SEHA? Beside that, we’ll see how the Multitenant feature “Refreshable PDB” can serve as a “poor man’s DataGuard alternative for SE2".
Before version 9i of the Oracle database, more and more Oracle components stored their tables in the SYSTEM tablespace. This lead to a high space consumption in this important tablespace. In Oracle database 10g introduced the SYSAUX tablespace and moved everything which is not part of the data dictionary from the SYSTEM tablespace to SYSAUX. Since then, more and more database components populate the SYSAUX tablespace and it keeps growing … – and if the DBA is not careful, the tablespace SYSAUX tablespace can become really huge The presentation shows how to analyze and reduce the occupancy of the SYSAUX tablespace and how to avoid it in advance by suitable settings.