Archivelog full

Question

Hi,
11.2.0.1
When you db encounters "archive log full waiting to be freed", is there a way to resolve it without shutting down the db? Thanks.
vk82 Oct 9, 2013 9:35 AM
In case if your DB is Production. How will you continue to operate your DB in no archivelog mode.
The solution for above mentioned problem is either:
SQL> Shutdown abort;
SQL> Startup Mount;
1) Change your Archiving Destination by :
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST='NEW_PATH_LOCATION'
or
2) Increase the size of Archiving Destination by first determining the size of the Archiving destination which intially you have:-
SQL> SELECT NAME,(space_limit/1048576),(space_used/1048576) from v$recovery_file_dest;
And after that increase the space according to above output:-
SQL> alter system set db_recovery_file_dest_size=more_size_than_getting_size_above scope=both;
SQL> Alter database open;
Now
SQL> Shutdown immediate;
SQL> Startup;
or
3) Zip the archive logs and move it to anyother destination but be careful to preserve this you require all this archivelogs during recovery.

Answer 1

ozgurumut wrote:
Hi,
As I understand , you need to manage disk space of archivelog field. You can make with script or RMAN config.
Firstly, You may try RMAN Configuration like on below;
RMAN> Crosscheck archivelog all;
RMAN> Delete exprired archivelog all;
Secondly , You can use shell script (contains oracle command).
1. find <archivelog location> -name '*.log' -mtime +10 -exec rm -rf {} \;
2. RMAN> Crosscheck archivelog all;
3. RMAN> Delete exprired archivelog all;
#!/bin/sh
ORACLE_HOME=/u01/app/oracleths/product/11.2; export ORACLE_HOME
ORACLE_SID=test; export ORACLE_SID
PATH=.:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/proc/lib:/usr/ucb:/usr/lib:/usr/ucblib:/opt/bin:/bin:/usr/bin:/GNU/bin/make
export PATH
find <archivelog location> -name '*.log' -mtime +10 -exec rm -rf {} \;
$ORACLE_HOME/bin/rman target / << EOF
Crosscheck archivelog all;
Delete exprired archivelog all;
exit
EOF
Finally, you should put to crontab . And it will work...
Far better would be to construct the backup procedure to let rman manage it all -- FRA or not.
rman> backup database [options]
rman> backup archivelog delete [options]
rman> delete noprompt obsolete.
and for a bit of extra insurance against 'unauthorized maintenance'
rman> crosscheck archivelog all;
rman> delete noprompt expired archivelog;
rman> crosscheck backup;
rman> delete noprompt expired backup;
schedule it however you want.  All your backup, all your housekeeping, in one place, managed exclusively by rman.