Find us on Google+ Google+

June 27, 2012

Logical Standby Databases

Logical Standby Databases

*** COMING SOON ***




ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY;
ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY;

ALTER DATABASE ACTIVATE LOGICAL  STANDBY DATABASE;

ALTER DATABASE RECOVER TO LOGICAL STANDBY prodc;
ALTER DATABASE RECOVER TO LOGICAL STANDBY KEEP IDENTITY;
ALTER DATABASE START LOGICAL STANDBY APPLY;
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
ALTER DATABASE START LOGICAL STANDBY APPLY SKIP FAILED TRANSACTION;
ALTER DATABASE ABORT LOGICAL STANDBY APPLY;
ALTER DATABASE STOP LOGICAL STANDBY APPLY;

V$LOGSTDBY
V$LOGSTDBY_STATS
V$LOGSTDBY_PROGRESS
DBA_LOGSTDBY_EVENTS
DBA_LOGSTDBY_LOG
DBA_LOGSTDBY_NOT_UNIQUE
DBA_LOGSTDBY_PARAMETERS
DBA_LOGSTDBY_PROGRESS
DBA_LOGSTDBY_SKIP
DBA_LOGSTDBY_SKIP_TRANSACTION
DBA_LOGSTDBY_UNSUPPORTED
dba_apply

EXECUTE DBMS_LOGSTDBY.BUILD;
exec DBMS_LOGSTDBY.APPLY_SET('MAX_SERVERS', 12);
exec DBMS_LOGSTDBY.APPLY_SET('MAX_SGA', 100);
exec DBMS_LOGSTDBY.APPLY_SET('TRANSACTION_CONSISTENCY', 'READ_ONLY');
exec DBMS_LOGSTDBY.APPLY_UNSET('MAX_SGA');
exec dbms_logstdby.instantiate_table('OWNER','TAB1','DBLINK3');
exec dbms_logstdby.purge_session;
exec dbms_logstdby.skip('SCHEMA_DDL','OWNER','TAB1',NULL);
exec dbms_logstdby.skip('DML','OWNER','TAB1',NULL);
exec dbms_logstdby.unskip('DML','OWNER','TAB1');
exec dbms_logstdby.skip_error('NON_SCHEMA_DDL','OWNER','%',NULL);
exec dbms_logstdby.skip_transaction(231, 4,80298);

Related Articles: Logical Standby Databases   Physical Standby Databases    dgmgrl utility