If space ran out in an archive destination, after you fix the problem, you may still recieve the following error in your alert_log:

ARC1: Archiving not possible: No primary destinations

A quick way to solve this is to modify your archive destination with the reopen parameter. This parameter specifies the minimum number of seconds before redo transport services should try to reopen a failed destination.


SQL> show parameter log_archive_dest_1


NAME TYPE VALUE
------------------------------------ ------- ------------------------------
log_archive_dest_1 string location=/db/orcl/archive


SQL> alter system set log_archive_dest_1='location=/db/orcl/archive reopen=5' scope=both;

System altered.

Following that modification you should start seeing successful archive messages in your alert_log.

ARC1: Beginning to archive log# 1 seq# 115127
...
ARC0: Completed archiving log# 1 seq# 115127
...

文章标题：Archivingnotpossible:Noprimarydestinationserrors
URL链接：http://azwzsj.com/article/pjhidh.html