Verify the Configuration
When the DR setup is complete, immediately validate that the setup is correct by performing a complete switchover or by opening the secondary site for validation. Opening the secondary site for validation will not affect the system running in primary.
Open the Secondary for Validation
Note:
This operation must be done with caution: if there are pending messages or composites in the database when it is converted into snapshot, the standby site’s SOA servers will process them when they start. Check that there are no pending actions in the primary database when converting to snapshot standby. Otherwise, remove records from runtime SOA tables in the standby database after it is converted to snapshot standby database and before starting the secondary site’s SOA servers. See Removing Records from the Runtime Tables Without Dropping the Tables for the steps to validate the standby site without performing a switchover.Note:
ORA-01403: no data found ORA-06512 errorsWhile validating the secondary
site as described here (without performing a complete
switchover, that is, just opening standby in snapshot
standby mode) “ORA-01403: no data found ORA-06512” errors
may show up in the logs of the standby SOA servers. These
errors are related to the SOA auto purge job. These errors
arise because jobs in the database may have db role
dependencies (they are defined to be enabled only when the
database is in primary role). This is an expected and
desired behavior that prevents jobs from being executed
twice (once in primary and once in standby). The SOA auto
purge job is defined with primary role, so it is not shown
in DBA_SCHEDULER_JOBS view when the database is in snapshot
standby mode. The database_role
defined for
each job can be seen in the view DBA_SCHEDULER_JOB_ROLE. In
summary, these errors can be ignored as long as they appear
in the standby system. The scheduler job for SOA auto purge
will be executed on the database if, and only if, the
instance changes its role to PRIMARY.