If your application ensures the rows in a table are unique, you can create a disabled primary key RELY constraint on the table. Use ALTER TABLE command to add a disabled primary-key RELY constraint. The following example creates a disabled RELY constraint on a table named mytab, for which rows can be uniquely identified using the id and name columns: Create a Physical Standby Database and make sure that there is no error in remote archiving to Standby from Primary Database. Use following query on Standby to check:There should not be any difference in Last Seq Received and Last Seq Applied on Physical Standby. Change VALID_FOR in LOG_ARCHIVE_DEST_1 on Primary to (ONLINE_LOGFILES,ALL_ROLES) Set LOG_ARCHIVE_DEST_3 for logs which will received on Standby from PrimaryNote: LOG_ARCHIVE_DEST_3 only takes effect when the primary database is transitioned to the logical standby role.The DBMS_LOGSTDBY.BUILD procedure waits for all existing transactions to complete. Long-running transactions executed on the primary database will affect the timeliness of this command.For db_name, specify a database name to identify the new logical standby database. If you are using a spfile for standby, then command will update the db_name parameter otherwise it will issues a message reminding you to set the name of the DB_NAME parameter after shutting down the database.This step is required in 10.2 only and should not be performed in 11g.
