OraEasy

Introduction: Snapshot standby is a feature since Oracle 11g that allows doing a read-write operation on the standby database. Suppose application team want to do testing on Fresh Live Data, but DBA cannot allow them to test on Primary. To help on this, DBA can convert physical standby to snapshot standby in read-write mode. Then application team can make their changes in snapshot database. Whatever changes done on snapshot standby will be rollbacked once convert back to physical standby database from snapshot standby. Primary database changes will not be applied to snapshot standby database as there is no MRP process running snapshot database. Prerequisites: Oracle Data Guard should be configured. Disable DG broker if any as it will start MRP automatically. Environment: Server Primary Standby Hostname Source Target IP 192.168.80.51 192.168.80.111 OS...

Introduction: A Release Update (RU) is Oracle's primary method for delivering both bug fixes and new features for Oracle Database versions 12.2 and later. Introduced to replace the older Patch Set Updates (PSUs) and Critical Patch Updates (CPUs), RUs are part of Oracle's shift toward a more predictable and modern patching model. In this article we will apply the Oracle RU 19.27 Patch on Primary & Standby database. Data Guard Standby-First Patch Apply: As we are having Data Guard configured, so we will first apply the patch on Standby Database as per Oracle standard. Although we must go through the Patch ReadMe to ensure that the Patch is Data Guard Standby-First Installable . Refer Oracle Doc 1265700.1 for more details Approach: o Apply patch at binary level on Standby. o Apply patch at binary level on Primary. o Ensure Primay & Standby are in Sync. o Run Datapatch (SQL Patch) on Primary & verify the sync between Primary ...

Introduction: Since Oracle 12c, the CDB (Container Database) and PDB (Pluggable Database) model has been the recommended architecture. Oracle has announced that non-CDB architecture is deprecated (and not supported starting from Oracle 21c). So migrating is necessary if you are upgrading to a newer Oracle version. Patch consideration: If the instances are not at the same patch level, you will get PDB violations visible in the PDB_PLUG_IN_VIOLATIONS view. If the destination is at a higher patch level than the source, then run the datapatch -verbose utility on the destination instance in the normal way. It may throw any error and also suggest what action needs to be taken. If the destination is at a lower patch level than the source, you will need to run a datapatch -rollback operation. Methods of migration: DBMS_PDB Package (Plugging method) Creating the PDB via DB Link Export/Import Method In previous article Migrating Non-CDB to CDB ...