Regarding to heavy duty On Database , Database start Generates Archive log with time size for flash recovery become full , so what i have to do :
first you will not be able login for database or rman
-Go to archivelog detestation and delete archivelog (old first) , if you have space on your server you can move them from direcotry to another .
-Flash Recovery On ASM , Follow the below steps
now you are inside ASM head to Archivelog destation and delete archive log manually (old first )
Step 2 :
Now you will be able to login to rman :
ALLOCATE CHANNEL c1 DEVICE TYPE DISK FORMAT '/u01/';
backup archivelog all delete input ;
release c1 ; }
Now you clean Archivelog .
THis solution for Both Cluster and Single Node Database
Published by Osama Mustafa
Osama considered as one of the leaders in Cloud technology, DevOps and database in the Middle-East. I have more than ten years of experience within the industry. moreover, certfied 4x AWS , 4x Azure and 6x OCI, have also obtained database certifications for multiple providers.
In addition to having experience with Oracle database and Oracle products, such as middle-ware, OID, OAM and OIM, I have gained substantial knowledge with different databases.
Currently, I am architecting and implementing Cloud and DevOps. On top of that, I'm providing solutions for companies that allow them to implement the solutions and to follow the best practices.
View all posts by Osama Mustafa
2 thoughts on “Unable to login to Database Because Archivelog”
Thank you osama for sharing;-).i have one question:how proactively monitoring the size of flash recovry area to avoid this problem ?
Check new Post