How to configure the size of Fast Recovery Area (FRA) in Oracle database ?

Configure the size of FRA 

 

SQL>

SQL>

SQL> show parameter db_recovery

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

db_recovery_file_dest                string      /u01/app/oracle/fast_recovery_

                                                 area

db_recovery_file_dest_size           big integer 12732M

SQL>

SQL>

SQL> alter system set db_recovery_file_dest_size=12G scope=both ;

System altered.

SQL> show parameter db_recovery_file_dest_size;

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

db_recovery_file_dest_size           big integer 12G

SQL>

How to add a redo log member to an existing redo log group in an Oracle database | Redo log files Multiplexed

Add a redo log member to an existing redo log group in an Oracle database

SQL> select group#,status,member from v$logfile;

    GROUP# STATUS

---------- -------

MEMBER

--------------------------------------------------------------------------------

         3

/u01/app/oracle/oradata/DB1/redo03.log

         2

/u01/app/oracle/oradata/DB1/redo02.log

         1

/u01/app/oracle/oradata/DB1/redo01.log

SQL>

SQL> select group#,members,archived,status from v$log;

    GROUP#    MEMBERS ARC STATUS

---------- ---------- --- ----------------

         1          1 NO  CURRENT

         2          1 YES INACTIVE

         3          1 YES INACTIVE

SQL>

SQL> alter database add logfile member '/u01/app/oracle/oradata/DB1/redo01b.log' to group 1;

Database altered.

SQL> select member from v$logfile;

MEMBER

--------------------------------------------------------------------------------

/u01/app/oracle/oradata/DB1/redo03.log

/u01/app/oracle/oradata/DB1/redo02.log

/u01/app/oracle/oradata/DB1/redo01.log

/u01/app/oracle/oradata/DB1/redo01b.log

SQL> 

Best Practices & Notes

Always add members on different disks for redundancy.

The new log file must not exist already on disk.

All members of a group are written to simultaneously — they are identical.

Adding a member does not affect the database availability.

Two key features of Oracle Exadata Machine

Smart Scan (Exadata Smart Storage):

Offloads query processing to the storage layer, reducing the amount of data sent to the database servers.

Enables operations like filtering, column projection, and join processing to be performed directly on the storage servers, improving query performance significantly.

Hybrid Columnar Compression (HCC):

Provides advanced data compression techniques to reduce storage requirements and improve I/O performance.

Optimized for both OLTP (Online Transaction Processing) and OLAP (Online Analytical Processing) workloads, enabling faster query execution and efficient storage utilization.

Steps for Onboarding Oracle Database to Azure

Assessment and Planning:

Evaluate the Oracle database version, size, and features.

Identify the target Azure service (e.g., Azure Virtual Machines, Azure Database for PostgreSQL if migrating to an open-source database, or Azure SQL Managed Instance for re-platforming).

Use tools like:

Azure Migrate: For assessing workloads.

Oracle SQL Developer Migration Workbench: For schema and data migration.

Data Migration Assistant (DMA): For compatibility checks if re-platforming.

Choose the Deployment Model:

Decide whether to run Oracle on:

Azure Virtual Machines: For lift-and-shift migrations, running Oracle Database on Azure VMs.

Azure Database Services: If re-platforming to a different database engine.

Provision the Target Environment:

Set up the required Azure infrastructure, such as virtual networks, storage, and compute resources.

Migrate the Database:

Use tools like Oracle Data Pump, RMAN, or third-party tools for data migration.