Oracle: Free space in Fast-Recovery-Area (FRA)

Sooner or later I guess every DBA will be faced with this error-message

ORA-00257: archiver error. Connect internal only, until freed.

and angry phone-calls from users complaining about a hanging database.

The reason for this error is a lack of space for archiving redologs.

When using a FRA and a proper set up backup that deletes obsolete files automatically, you propably only have two options:

  • Increase the FRA-Size by changing the parameter “db_recovery_file_dest_size” and/or
  • Relocate the FRA-Directory to another disc by changing the parameter “db_recovery_file_dest”
  • If space is available, both options are done quick and easy and get you out of your mess instantly. So don’t panic – and beware of deleting e.g. some archive-logs on OS-Level. As laid out in my post “Oracle: How to tell DB about manually freed space in FRA“, the latter won’t get you further and may even worsen your situation.

    To increase the FRA-Size do this:

    alter system set db_recovery_file_dest_size=100g scope=both;
    

    To change to FRA-Location do this:

    alter system set db_recovery_file_dest='/usr4/oracle/fast_recovery_area' scope=both;
    

    Changing the FRA-Location is not complicated as stated here: “Oracle: Relocate Fast-Recovery-Area (FRA)

    Advertisements

    Leave a Reply

    Fill in your details below or click an icon to log in:

    WordPress.com Logo

    You are commenting using your WordPress.com account. Log Out / Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out / Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out / Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out / Change )

    Connecting to %s

    %d bloggers like this: