Time for action – changing the Database Guard setting

As we mentioned before, the default Database Guard mode for a logical standby database is set to ALL. Let's try to insert data into the HR.REGIONS table, which is out of the replication scope because of the skip rule we created.

1. Connect the logical standby database with SYS user. Check the Database Guard mode and skip rules with the following query:

   SQL> SELECT GUARD_STATUS FROM V$DATABASE;
   
   GUARD_S
   -------
   ALL
   
   SQL> SELECT OWNER, NAME,STATEMENT_OPT, PROC  FROM DBA_LOGSTDBY_SKIP  WHERE STATEMENT_OPT <> 'INTERNAL SCHEMA';
   
   OWNER    NAME         STATEMENT_OPT   PROC
   -------- ------------ --------------- ------------------
                         DIRECTORY
   HR       %            DML
                         TABLESPACE      SYS.CHANGE_TS_DDL 

   Database Guard mode is ALL and all HR tables are skipped by SQL Apply.

2. Now connect with the HR user and insert a row to the REGIONS table:

   SQL> CONN HR/HR
   Connected.
   SQL> INSERT INTO HR.REGIONS...