Relational Databases

According to Oracle Backup and Recovery documentation, restoring a Pluggable Database (PDB) normally requires access to the backup of the Container Database (CDB) that originally hosted the PDB. Without the source CDB metadata, restoring a standalone PDB backup is generally not possible. However, there is an alternative approach that can sometimes be used to recover a PDB backup and plug it into a different CDB. Although this method is not guaranteed to work in every scenario, it is a useful technique to be aware of when designing backup and recovery strategies. In this example, we will back up a PDB named RMANPDB, transfer the backup to another server, and restore it into a completely new CDB. Backing Up the PDB First, verify that the PDB exists and is open: Connected to: Oracle Database 21c Enterprise Edition Release 21.0.0.0.0 - Production Version 21.3.0.0.0 SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- -----------------------------...

  In data dictionary views related to partitioning, the HIGH_VALUE column is one of the most frequently used attributes. However, its datatype is LONG , which comes with several limitations and restrictions. To address these limitations, Oracle AI Database 26ai introduces two additional columns, HIGH_VALUE_CLOB and HIGH_VALUE_JSON , allowing partition high values to be represented in more convenient formats. The following example creates an interval-partitioned table: SQL > create table tb( 2 id number, 3 date_ date 4 ) 5 partition by range ( date_ ) 6 interval ( numtoyminterval( 1 , 'YEAR' )) 7 ( 8 PARTITION p2022 VALUES LESS THAN (TO_DATE( '2023/01/01' , 'YYYY/MM/DD' )), 9 PARTITION p2023 VALUES LESS THAN (TO_DATE( '2024/01/01' , 'YYYY/MM/DD' )), 10 PARTITION p2024 VALUES LESS THAN (TO_DATE( '2025/01/01' , 'YYYY/MM/DD' )) 11 ); Table created To display partition ...

  Oracle AI Database 26ai introduces a useful enhancement for Data Guard environments that contain multiple standby databases. The new PrimaryDatabaseCandidates Data Guard Broker property allows administrators to explicitly define which databases are eligible to assume the primary role during switchover or failover operations. This feature is particularly valuable in environments where some standby databases are dedicated to disaster recovery while others are used for reporting, testing, cloning, or other non-production purposes. *The PrimaryDatabaseCandidates property is available starting with Oracle Database 19.26 Release Update (RU). Test Environment For this test, I configured a Data Guard environment consisting of one primary database and two physical standby databases. DGMGRL> show configuration Configuration - DB2 Protection Mode: MaxPerformance Members: DB2 - Primary database dg1 - Physical standby database dg2 - Physical standby database...