Database Version: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
OS: HP UX Itanium
We have a primary (on server1) and standby database (on server2). As part of the standard DR test, we did a switchover to standby database on Server 2. Everything worked as normal.
After the test, we failed back the database to (server1).
I am seeing the following:
On Primary:
SQL>archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /XXXXXXXX/arch
Oldest online log sequence 253
Next log sequence to archive 255
Current log sequence 255
SQL>
SQL>SELECT sequence#, first_time, next_time FROM v$archived_log where rownum <10 order by sequence# desc;
SEQUENCE# FIRST_TIM NEXT_TIME
---------- --------- ---------
7162 10-FEB-14 10-FEB-14
7162 10-FEB-14 10-FEB-14
7161 10-FEB-14 10-FEB-14
7161 10-FEB-14 10-FEB-14
7160 10-FEB-14 10-FEB-14
7160 10-FEB-14 10-FEB-14
7159 10-FEB-14 10-FEB-14
7159 10-FEB-14 10-FEB-14
7158 10-FEB-14 10-FEB-14
I am curious to know -
1) Does sequence # change whenever we do a switch over and fail back ?
2) How can we fix the value of ' archive log list' and 'v$archived_log' to be same?
We use RMAN for our database backup.
P.S: I do understand that the database I am running is on a older version of Oracle and I need to upgrade to 11gR2 or 12c. We have some legacy application on this DB that is not supported in other release. We are looking for another alternate solution. In the mean time, I would like to understand what all process does it happen in the internally during switch over and fail back, also fix the issue with v$archived_log ?
Thanks
Cherrish Vaidiyan
Message was edited by: Cherrish