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
…
Archiving not possible: No primary destinations errors
【声明】:本博客不参与任何交易,也非中介,仅记录个人感兴趣的主机测评结果和优惠活动,内容均不作直接、间接、法定、约定的保证。访问本博客请务必遵守有关互联网的相关法律、规定与规则。一旦您访问本博客,即表示您已经知晓并接受了此声明通告。
相关推荐
- NoClassDefFoundError:....KeyedObjectPoolFactory
- BAT都在用的数据库
- mysql主备复制I/O线程不能同步问题
- no buffer space available、由于系统缓冲空间不足或队列已满,不能执行套接字上的操作
- oracle 12c ORA-28040: No matching authentication protocol 处理办法
- libz.so.1: cannot open shared object file: No such file or directory
- 查询的时候绕过查询缓存SQL_NO_CACHE
- (一)、根据teacher_no统计星期的上课数