This content has been marked as final. Show 2 replies
Is your DB in archive log mode? If enabled do you have enough space for archival destination? If you archival destination is full then delete few archivelogs to reclaim some space.
If your redo log size is too small to handle your current redo log switch frequency then bigger redo log size will work in this case. Increase redo log size to 600M.
If automatic archival is disabled, run the following command
ALTER SYSTEM ARCHIVE LOG ALL;
it is better if you set as well LOG_ARCHIVE_START parameter into init.ora
MED1 - Can not allocate log, archival requiredIt seems that all the online redo logs are full and you need to empty them. This can happeen due to two reasons
1) archivelog destination is full
2)archiving is disabled although the database is in archive log mode
increased log_archive_max_process=10These solution will not help you. See if the sufficient empty space is there at log_archive_destination. If it is there it may happen that archive log files were removed by OS commands and database has no knowledge about the removal. In this case connect to RMAN and crosscheck archivelogs, delete the expired. This will let the database archive all redo logs once you execute the command 'ALTER SYSTEM SWITCH LOGFILE' . If enough space is not there backup the old archivelog and delete them as described above. If archiving is disabled the enable them executing the command 'ALTER SYSTEM set log_archive_dest_state_1=enable'
increased redlogs form 300Mb to 500Mb with additional groups..
Please advise if this is the correct solution ?