Inconsistent value of RESETLOGS_CHANGE# after Standby reinstated.
edited Nov 20, 2011 4:41PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered
Hi,
My problems (as I understand it) is that after successful failover and successful reinstatement of new standby
database, redo logs do not applied to standby database because. Value on RESETLOGS_CHANGE#
is inconsistent on Standby database.
There are details:
1. Configuration
Server smphoracledb01 with Primary database DB_UNIQUE_NAME = NVCSOM1A
Server smphoracledb02 with Standby database DB_UNIQUE_NAME = NVCSOM1B
Server smphoracledb03 with Data Guard Observer running.
All servers run Linux with Oracle 11.2.0.1.0.
2. Server with Primary database failed and database failed over to Standby server.
No problem here. Primary database NVCSOM1B is up and running on server smphoracledb02.
My problems (as I understand it) is that after successful failover and successful reinstatement of new standby
database, redo logs do not applied to standby database because. Value on RESETLOGS_CHANGE#
is inconsistent on Standby database.
There are details:
1. Configuration
Server smphoracledb01 with Primary database DB_UNIQUE_NAME = NVCSOM1A
Server smphoracledb02 with Standby database DB_UNIQUE_NAME = NVCSOM1B
Server smphoracledb03 with Data Guard Observer running.
All servers run Linux with Oracle 11.2.0.1.0.
2. Server with Primary database failed and database failed over to Standby server.
No problem here. Primary database NVCSOM1B is up and running on server smphoracledb02.
0