php5.6 oracle11,解决ORA-16055: FAL request rejected

这两天折腾rac-单节点的DG

平台如下：rhel 5.6 64 oracle：10.2.0.5-64

做的快结束的时候，遇到如下问题，郁闷了很久，以致我今天晚上彻夜解决此问题：

错误如下：

pri:

Sat Jun 15 03:05:39 CST 2013

ORACLE Instance yesno1 - Archival Error. Archiver continuing.

FAL[server, ARC1]: FAL archive failed, see trace file.

Sat Jun 15 03:05:39 CST 2013

Errors in file /u01/app/oracle/admin/yesno/bdump/yesno1_arc1_20232.trc:

ORA-16055: FAL request rejected

ARCH: FAL archive failed. Archiver continuing

Sat Jun 15 03:05:39 CST 2013

ORACLE Instance yesno1 - Archival Error. Archiver continuing.

FAL[server, ARC1]: FAL archive failed, see trace file.

Sat Jun 15 03:05:39 CST 2013

Errors in file /u01/app/oracle/admin/yesno/bdump/yesno1_arc1_20232.trc:

ORA-16055: FAL request rejected

ARCH: FAL archive failed. Archiver continuing

Sat Jun 15 03:05:39 CST 2013

ORACLE Instance yesno1 - Archival Error. Archiver continuing.

FAL[server, ARC1]: FAL archive failed, see trace file.

Sat Jun 15 03:05:39 CST 2013

Errors in file /u01/app/oracle/admin/yesno/bdump/yesno1_arc1_20232.trc:

ORA-16055: FAL request rejected

ARCH: FAL archive failed. Archiver continuing

Sat Jun 15 03:05:39 CST 2013

ORACLE Instance yesno1 - Archival Error. Archiver continuing.

FAL[server, ARC1]: FAL archive failed, see trace file.

TRACE文件内容如下：

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

其他什么也没了

stb：

MRP0: Background Managed Standby Recovery process started (yesno)

Managed Standby Recovery not using Real Time Apply

parallel recovery started with 15 processes

Sat Jun 15 03:04:48 CST 2013

Waiting for all non-current ORLs to be archived...

Media Recovery Waiting for thread 1 sequence 17136

Fetching gap sequence in thread 1, gap sequence 17136-17229

Sat Jun 15 03:04:48 CST 2013

Completed: ALTER DATABASE RECOVER  managed standby database disconnect from session

Sat Jun 15 03:06:23 CST 2013

FAL[client]: Failed to request gap sequence

GAP - thread 1 sequence 17136-17229

DBID 423650287 branch 770684126

FAL[client]: All defined FAL servers have been attempted.

-------------------------------------------------------------

Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization

parameter is defined to a value that is sufficiently large

enough to maintain adequate log switch information to resolve

archivelog gaps.

-------------------------------------------------------------

到metalink上也没找到好的解决建议，网上搜了下，有的说归档空间问题，此处非也，权限问题，此处更非也

最后的解决方法如下，说出来都觉得可笑：

在pri上先执行：

ALTER SYSTEM SET log_archive_dest_state_2='DEFER' SCOPE=BOTH;

然后用：

alter system switch logfile；

执行几次，再执行：

ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;

问题解决。

Sat Jun 15 03:08:18 CST 2013

Thread 1 advanced to log sequence 17236 (LGWR switch)

Current log# 4 seq# 17236 mem# 0: +DATA/yesno/onlinelog/redo4.1.log

Sat Jun 15 03:08:52 CST 2013

Thread 1 advanced to log sequence 17237 (LGWR switch)

Current log# 1 seq# 17237 mem# 0: +DATA/yesno/onlinelog/redo1.1.log

Sat Jun 15 03:09:05 CST 2013

Thread 1 cannot allocate new log, sequence 17238

Checkpoint not complete

Current log# 1 seq# 17237 mem# 0: +DATA/yesno/onlinelog/redo1.1.log

Sat Jun 15 03:09:19 CST 2013

Thread 1 advanced to log sequence 17238 (LGWR switch)

Current log# 2 seq# 17238 mem# 0: +DATA/yesno/onlinelog/redo2.1.log

Sat Jun 15 03:11:03 CST 2013

Using STANDBY_ARCHIVE_DEST parameter default value as +DATA/yesno/archivelog

Sat Jun 15 03:11:03 CST 2013

ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;

Sat Jun 15 03:11:39 CST 2013

Sat Jun 15 03:11:39 CST 2013

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Sat Jun 15 03:12:09 CST 2013

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

到哪找地说理去！！！

还真有大牛给出了解释：

正常配置DG，先配置LOG_ARCHIVE_CONFIG，然后再配置LOG_ARCHIVE_DEST_N参数既可。

如果出现了这个问题，只需要通过参数LOG_ARCHIVE_DEST_STATE_N暂停日志，随后在启用，Oracle就会重新分析LOG_ARCHIVE_DEST_N中的配置

总结下，也就是oracle没有分析出LOG_ARCHIVE_DEST_N中的配置，导致了ORA-16055: FAL request rejected问题出现，日志无法正常传输。

姑且如此吧，睡觉。明天一早还要进行数据库迁移，另外一家客户。