kidswhe.blogg.se -

#ALTER SYSTEM DB RECOVERY FILE DEST SIZE ARCHIVE#
#ALTER SYSTEM DB RECOVERY FILE DEST SIZE WINDOWS#

#ALTER SYSTEM DB RECOVERY FILE DEST SIZE WINDOWS#

Impose a smaller recovery window on the retention period, if the current recovery windows is significantly big. Just like we talked about in solution #1, #4 and #5. Set a reasonable size for FRA in advance. Here are preventive actions that you can consider to take to prevent ORA-19809. SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_1=e:\oracle\dbname\archivelog SCOPE=SPFILE Preventive Actions Change Destination of Archived LogsĪgain, you have to restart the database to make it work.

#ALTER SYSTEM DB RECOVERY FILE DEST SIZE ARCHIVE#

Switch FRA to Another LocationĬhange log archive destination to another location SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST=e:\oracle\flash_recovery_area2\dbname SCOPE=SPFILE ĭon't forget to bounce the database service in order to apply the new change. Then make the archived log list consistent. Delete All Archived Logsĭelete all archive logs, no matter what. If the space is still full, you need a stronger medication like the next one. ~]$ rman target /Īdding NOPROMPT right after DELETE makes RMAN to directly delete all archived logs without user's confirmation. Assuming a lot of expired archive logs are available to be deleted. Delete Expired Archived Logsĭelete expired archive logs if there have no more space for archived logs. If your database is still online, then use SCOPE=BOTH SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=200G SCOPE=BOTH 2. Just make sure that the value does not exceed the overall disk space for FRA. SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=200G SCOPE=SPILE Īctually, starting up the database to MOUNT or NOMOUNT is no difference. Assuming that your database cannot be opened normally. Resize FRA to a larger value if disks still have more space available for FRA. Several ways that can solve ORA-19809 are listed in the following: 1. Then check current initialization parameters: SQL> show parameter db_recoveryĭb_recovery_file_dest string d:\oracle\flash_recovery_area\dbnameĭb_recovery_file_dest_size big integer 10G Solutions

Delete files from recovery area using RMAN.

Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.

Consider changing RMAN archived log deletion policy.

Consider changing RMAN retention policy.

Take frequent backup of recovery area using RMAN.

The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded. ORA-19809: limit exceeded for recovery files Cause Let's see the content of this error: Description If you have already shutdown the database, the error prevents you from startup, it could be severe. ORA-00312: online log 1 thread 1: 'd:/oracle/oradata/dbname/redo/redo02.log' ORA-19809: limit exceeded for recovery files ORA-16038: log 2 sequence# 230348 cannot be archived When you meet the following error, you hit the space limit of FRA.

Particularly, if the log archive destination is USE_DB_RECOVERY_FILE_DEST, then you must watch the usage of Fast Recovery Area (FRA) instead to prevent ORA-19809. u01/app/oracle/fra 1.0737E+10 0 0 0 0 3) Configure archive log destination to use flash recovery area.We usually watch the space usage of log archive destination very closely because the database will be suspended if the space is full. NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES CON_ID SQL>alter system set db_recovery_file_dest='/u01/app/oracle/fra' scope=both ĭb_recovery_file_dest string /u01/app/oracle/fraĭb_recovery_file_dest_size big integer 10G SQL> alter system set db_recovery_file_dest_size=10g scope=both

1)Check and confirm Flash Recovery Area is not enabled.