| How to resolve ORA-16401: archivelog rejected by RFS [message #521768] |
Thu, 01 September 2011 20:50  |
kytemanaic
Messages: 55
Registered: February 2009
|
Member |
|
|
Hi,
initial configuration:
cta: physical standby
ctastd: primary
I cancel my failover at cta half way,
from http://download.oracle.com/docs/cd/B193 ... m#i1026491
Quote:
Step 4 Initiate a failover on the target physical standby database.
Issue the following statement to initiate the failover:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH FORCE;
during the above process it took too long so I opened up another session and cancel the above process
SQL>alter database recover managed standby database cancel;
the data guard configuration is left as it is, i.e.
cta: physical standby
ctastd: primary
I discover the following findings in the alertcta.log, i.e. in cta database,
Primary database is in MAXIMUM PERFORMANCE mode
RFS[8]: Successfully opened standby log 4: 'D:\ORA102\CTA\REDO04.LOG'
Thu Sep 01 10:38:08 2011
Errors in file d:\ora102\cta\udump\cta_rfs_536.trc:
ORA-16401: archivelog rejected by RFS
I've googled around and find the following
from http://dbaforums.org/oracle/lofiversion ... 12859.html
Quote:
ORA-16401: archivelog rejected by RFS
Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.
Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.
it seems to be that there are multiple primary database, but it is not based on the information from v$database
Right now the physical standby database cannot received any archive logs from the primary.
I've checked the database_role in both servers, they are as they are designated.
from the physical standby database
SYS@cta>select db_unique_name, database_role, switchover_status from v$database;
DB_UNIQUE_NAME DATABASE_ROLE SWITCHOVER_STATUS
------------------------------ ---------------- --------------------
CTA PHYSICAL STANDBY NOT ALLOWED
SYS@cta>alter database recover managed standby database disconnect from session
;
Database altered.
SYS@cta>select db_unique_name, database_role, switchover_status from v$database;
DB_UNIQUE_NAME DATABASE_ROLE SWITCHOVER_STATUS
------------------------------ ---------------- --------------------
CTA PHYSICAL STANDBY SESSIONS ACTIVE
from the primary database
SYS@ctastd>startup nomount
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1295632 bytes
Variable Size 83888880 bytes
Database Buffers 79691776 bytes
Redo Buffers 2895872 bytes
SYS@ctastd>alter database mount;
Database altered.
SYS@ctastd>select db_unique_name, database_role, switchover_status from v$databa
se;
DB_UNIQUE_NAME DATABASE_ROLE SWITCHOVER_STATUS
------------------------------ ---------------- --------------------
CTASTD PRIMARY TO STANDBY
SYS@ctastd>alter database open;
Database altered.
SYS@ctastd>select db_unique_name, database_role, switchover_status from v$databa
se;
DB_UNIQUE_NAME DATABASE_ROLE SWITCHOVER_STATUS
------------------------------ ---------------- --------------------
CTASTD PRIMARY TO STANDBY
SYS@ctastd>
the standby is always busy, i.e. SESSIONS ACTIVE
so how do I resolve the above issue, i.e make sure the archived logs are shipped and apply over to physical standby.
I'm using Oracle 10.2.0.4 and os is windows.
thanks a lot!
[Updated on: Fri, 02 September 2011 00:52] by Moderator Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
