Recovery Area: Computing Obsolete files Wait Event in Oracle

I will explain Recovery Area: Computing Obsolete files Wait Event in Oracle in this post.

 

When I use the Switch database to copy command, my command is run more than 8 hours.

 

RMAN> SWITCH DATABASE TO COPY;

 

I have reviewed the AWR report and Session waits, I saw that Recovery Area: Computing Obsolete files Wait Event is seen.

Recovery Area: Computing Obsolete files Wait Event is caused because of Recovery area parameter.

 

 

 

 

 

To solve this wait event, you should disable the Recovery area parameters as follows.

 

SQL>
SQL> show parameter db_recovery_file_dest

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string +RECO
db_recovery_file_dest_size big integer 150000G
SQL>
SQL>
SQL> alter system reset db_recovery_file_dest scope=both sid='*';

System altered.

SQL> show parameter db_recovery_file_dest

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string
db_recovery_file_dest_size big integer 150000G
SQL>
SQL> alter system reset db_recovery_file_dest_size scope=both sid='*';
alter system reset db_recovery_file_dest_size scope=both sid='*'
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 -
18446744073709551614)

SQL> alter system set db_recovery_file_dest_size=1 scope=both sid='*';

System altered.

SQL>

 

 

Once I set these parameters, my switch database to copy command speed up and completed in a 30 minutes.

 

 

You can read the following post to learn more details about Wait events in Oracle.

Oracle Wait Events and Their Solutions in Oracle Database

See more

 

 

 

 

 

Do you want to learn Oracle Database Performance Tuning detailed, then read the following articles.

Performance Tuning and SQL Tuning Tutorial in the Oracle Database

See more