Bug on Bits

ORA-16038: log 1 sequence# 244 cannot be archived  ORA-19809: limit exceeded for recovery files  ORA-00312: online log 1 thread 1  There is a possibility to encounter this issue in oracle database and when this happens you wont be able to open the database. you will be getting this once the  db_recovery_file_dest_size   value  gets exceeded.  However you can fix this one by increasing the  db_recovery_file_dest_size   or by clearing the  obsolete files. To increase the  db_recovery_file_dest_size   size use the following steps. 

If you are an Oracle DBA you will have to come across this topic or might not. However if we have to Chage the archive destination in Oracle Database then this article provides more details on how to proceed. If you are using a spfile then create a pfile as fail safe practice. connect to the database SQL> CREATE PFILE='$ORACLE_HOME/dbs/initORA.ora' FROM SPFILE='SPFILEORA.ORA'; Change the log_archive_dest parameter using SQL> alter system set log_archive_dest='/vol2/oradata/archives' scope=spfile; Shutdown the database SQL> Shutdown immediate start the database; SQL> startup trigger the log change; SQL> alter system switch logfile; Then move to new archive destination directory and check weather archive logs are creating. If creating then the change is successfull otherwise you may need to check the permission for the new log destination and configuration. ===========================================================...

Each and every dba someday will or will not face this situation. But anyway I had to face this scenario. So I decided to blog the steps I followed thinking this might be helpful to some other newbie like me..... 1) Create all the mountpoint as identical to the source 2) Copy all the RMAN backup files to the RMAN source directory 3) Put the DB in to the nomount state    startup nomount 4) set the environment using . oraenv(if linux) 5) connect to RMAN    RMAN taget / 6) Restore the control file    RMAN> restore controlfile from '/BACKUP/RMAN_BACKUP/DB1/c-974303543-20120319-00'; 7) Mount the database    RMAN> Alter database mount 8) select the max sequence using    SQL> select max(sequence#) from v$log; 9) Connect back to the RMAN and execute    RMAN> run    { set until sequence $number;     restore database; } P.S $number is the number found executing the statement...