Abdul Hafeez Kalsekar -- Oracle database tuning case studies

  In this Document Goal Solution APPLIES TO: Oracle Cloud Infrastructure - Database Service - Version N/A to N/A [Release 1.0] Information in this document applies to any platform. GOAL The procedure described in this note is applicable for OCI DBaaS environment, Oracle 18c and higher. Typically, when rolling forward a physical standby database using primary incremental backup, multiple steps are required: Identify the Start SCN on Standby for performing incremental backup on primary Perform incremental backup on primary with FROM SCN clause Move the backup-pieces from primary to standby Catalog the backup-piece on Standby Perform recovery on standby using recover database noredo Refresh standby controlfile again from primary Starting from 12.1, we could use "RECOVER DATABASE FROM SERVICE" command which will automate a few steps like performing incremental backup on primary, transfer the backup-pieces to standby over network and perform recovery on standby. However, we still ...

  In this Document Goal Solution   Stop Managed Recovery and Redo Transport   Save Existing Logfile Names   Refresh Standby Control File From Primary    Document the Current SCN for the Standby   Save Current RMAN Configuration Settings   Refresh the Standby Control File   Replace RMAN Configuration Settings and Remove Orphaned Online and Standby Redo Log Files   Catalog Standby Database Files to the Refreshed Control File   Restore Any Missing Files   Switch Database to Copy   Clean Up Orphaned Files   Clear Online Redo Logs and Standby Redo Logs   Roll the Standby Database Forward   Restart All Instances to Mount   Re-Enable Redo Transport   Determine Section Size to be Used   Run Recover From Service   Recover Until Consistent    Re-Enable Flashback Database   Restart the Standby and Managed Recovery   Take a New Backup (If Needed) References APPLIES TO: O...

  In this Document Goal Solution   Confirm the write mode:   Change the write mode: APPLIES TO: Oracle Database - Enterprise Edition - Version 12.1.0.2 and later Information in this document applies to any platform. GOAL  How to confirm/change write mode in unified auditing. SOLUTION Confirm the write mode: Confirm from the DBA_AUDIT_MGMT_CONFIG_PARAMS. SELECT PARAMETER_VALUE FROM DBA_AUDIT_MGMT_CONFIG_PARAMS WHERE PARAMETER_NAME='AUDIT WRITE MODE'; Confirm from the DBMS_AUDIT_MGMT.GET_AUDIT_TRAIL_PROPERTY_VALUE function. SET SERVEROUTPUT ON DECLARE   value NUMBER; BEGIN   value := DBMS_AUDIT_MGMT.GET_AUDIT_TRAIL_PROPERTY_VALUE(     audit_trail_type            => DBMS_AUDIT_MGMT.AUDIT_TRAIL_UNIFIED,     audit_trail_property        => DBMS_AUDIT_MGMT.AUDIT_TRAIL_WRITE_MODE);   CASE value     WHEN DBMS_AUDIT_MGMT.AU...

  In this Document Goal Solution   Requirements   Configuring   Instructions   Sample Code   Sample Output References APPLIES TO: Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Backup Service - Version N/A and later Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Oracle Database Cloud Service - Version N/A and later Information in this document applies to any platform. GOAL This script is intended to provide trend analysis information in the form of reports which would be used by the DBA to identify any sessions that over time use significantly more UGA and/or PGA memory than their peers by generating a snapshot report of the current values of UGA and PGA memory usage per RDBMS session as well as the maximum values of UGA and PGA memory usage since the time when each of the current RDBMS sessions started. For re-occurring ORA-04030 err...