RMAN: Keep archive redo in FRA, is this recommand? I asked Mr.Kamran Agayev
If you’re going to analyze the archived redo log files in the future using LogMiner utility, then you can either keep them at FRA, or move them to tapes or somewhere else
If you’re not going to analyze the archived redo log files, just take their backup daily using RMAN and delete them automatically .
Configuring Archive redo logs to go to FRA :
C:\Documents and Settings\AZAR>set oracle_sid=riyadh
C:\Documents and Settings\AZAR>sqlplus
SQL*Plus: Release 10.2.0.1.0 – Production on Sat Dec 26 14:18:22 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: / as sysdba
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – Production
With the Partitioning, OLAP and Data Mining options
SQL> alter system set log_archive_dest_1=’LOCATION=USE_DB_RECOVERY_FILE_DEST’;
SQL> show parameter log_archive_dest_state_1
NAME TYPE VALUE
———————————— ———– ——————————
log_archive_dest_state_1 string enable
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 4
Next log sequence to archive 6
Current log sequence 6
SQL> alter system switch logfile;
ORA-00257: archiver error.Connect internal only, until freed.
This message indicates that the location specified for archived redo logs is possibly full ,so you need to increase space.
SQL> select name from v$archived_log order by completion_time;
8 rows selected.
>> shall we keep archive log files in FRA? Is this recommand?
Yes. You have to take backup of FRA archive log (if your using)
Using RMAN try to take backup and then remove to avoid database hang stage.