Using Log Miner (II) - Example



Example 1: Find all modifications in the last archived redo log
  • Mining and source db are the same
  • Using Online catalog as dictionary

Steps: (the various steps are part of a script file logmnr_sql.sh)
  1. Configure supplemental logs and NLS_DATE_FORMAT (optional)
  2. Get user credentials (UserA, UserB, System)
  3. UserA creates table UserA.EMP
  4. UserA updates rows on table UserA.EMP
  5. UserB updates rows on table UserA.EMP
  6. User System:
    • (a) archives current redo log;
    • (b) Add list of log files for mining;
    • (c) starts log miner;
    • (d) query log miner information; and
    • (e) Ends log miner section
(Initial configuration): Enable supplemental logging and set data format
SQL> alter database add supplemental log data;
SQL> alter session set nls_date_format = 'dd-mon-yyyy hh24:mi:ss';
(1) Get user credentials (UserA, UserB, System)
#!/bin/bash
# logmnr_sql.sh

LOGFILE=logminer.log

###############################################################
# Get users credentials
##############################################################

usersystem=system
echo "Enter password for system"
read -s passwds
usera=usera
echo "Enter password for usera"
read -s passwda
userb=userb
echo "Enter password for userb"
read -s passwdb
sid=${ORACLE_SID}
(cont..)
(2) UserA creates table UserA.EMP
(cont..)
###############################################################
# Log in as userA. Recreate EMP table
##############################################################

sqlplus -s /nolog << EndOfSQL >> ${LOGFILE}
connect ${usera}/${passwda} 
whenever sqlerror exit sql.sqlcode;

prompt "Connected: UserA - recreating EMP.."

drop table emp;
create table emp as
  select employee_id as empno,
         first_name || ' ' || last_name as ename,
         department_id as deptno,
         salary as salary
  from hr.employees;
grant select, update on emp to userb;

exit;
EndOfSQL

ERRORCODE=$?

#check the return code from SQL Plus
if [ $ERRORCODE != 0 ]
then
 echo ********************************
 echo "ERROR: SQL*Plus failed with error code: $ERRORCODE"
else
 echo ********************************
 echo "SQL*Plus completed successfully. Error code: $ERRORCODE"
fi
(cont..)
(3) UserA updates some rows on table UserA.EMP
(cont..)
###############################################################
# Log in as usera. update data on table EMP
##############################################################

sqlplus -s /nolog << EndOfSQL >> ${LOGFILE}
connect ${usera}/${passwda} 
whenever sqlerror exit sql.sqlcode;

prompt "Connected: UserA - Updating rows..."

set serveroutput on  
begin
  update emp set salary = salary*1.05 where deptno = 50;
  commit;
  dbms_output.put_line('salaries on dept 50 updated..');  
  declare
   cursor c_emp is
     select empno, ename, deptno, salary from emp
     where deptno = 30
     for update;
  begin
   for c_reg in c_emp loop
     update emp
      set ename = initcap(c_reg.ename)
      where current of c_emp;
     update emp
      set salary = c_reg.salary *1.10
      where current of c_emp;
   end loop;
   commit;
   dbms_output.put_line('names and salaries on dept 30 updated..');  
  end;
end;
/

exit;
EndOfSQL

ERRORCODE=$?

# Check the return code from SQL Plus
if [ $ERRORCODE != 0 ]
then
 echo ********************************
 echo "ERROR: SQL*Plus failed with error code: $ERRORCODE"
else
 echo ********************************
 echo "SQL*Plus completed successfully. Error code: $ERRORCODE"
fi
(cont..)
(4) UserB updates rows on table UserA.EMP
###############################################################
# Log in as userB. update data on table EMP
##############################################################

sqlplus -s /nolog << EndOfSQL >> ${LOGFILE}
connect ${userb}/${passwdb} 
whenever sqlerror exit sql.sqlcode;

prompt "Connected: USERB"

set serveroutput on  
begin
  update usera.emp set salary = salary*1.05 where deptno = 60;
  dbms_output.put_line('SQL%ROWCOUNT: ['|| SQL%ROWCOUNT || '] rows returned');
  commit;
  dbms_output.put_line('salaries on dept 60 updated..');  
  declare
   cursor c_emp2 is
     select empno, ename, deptno, salary from usera.emp
     where deptno = 90
     for update;
  begin
   for c_reg in c_emp2 loop
     update usera.emp
      set ename = initcap(c_reg.ename)
      where current of c_emp2;
     update usera.emp
      set salary = c_reg.salary *1.10
      where current of c_emp2;
   end loop;
   commit;
   dbms_output.put_line('names and salaries on dept 30 updated..');  
  end;
end;
/
exit;
EndOfSQL

ERRORCODE=$?

# Check the return code from SQL Plus
if [ $ERRORCODE != 0 ]
then
 echo ********************************
 echo "ERROR: SQL*Plus failed with error code: $ERRORCODE"
else
 echo ********************************
 echo "SQL*Plus completed successfully. Error code: $ERRORCODE"
fi
(cont..)
(5) Log in as SYSTEM: (a) archives current redo log; (b) Add list of log files for mining; (c) starts log miner; (d) query log miner information; and (e) Ends log miner section
###############################################################
# Log in as SYSTEM. Run Log Miner 
##############################################################
echo "Configuring Log Miner section..."

sqlplus -s /nolog << EndOfSQL >> ${LOGFILE}
connect ${usersystem}/${passwds} 
whenever sqlerror exit sql.sqlcode;

prompt "Connected: SYSTEM"


prompt " (a) Switching current log file.."
alter system archive log current;

prompt "Most recently archived log file is"
set linesize 150
select name, first_change# from v\$archived_log
 where first_time = (select max(first_time) 
                       from v\$archived_log);

prompt "(b) Configuring the list of redo log files to be mined.."

declare
  v_logname varchar2(200);
begin
  select name into v_logname
   from v\$archived_log
   where first_time = (select max(first_time) 
                         from v\$archived_log);
 dbms_logmnr.add_logfile(LOGFILENAME => v_logname, OPTIONS => dbms_logmnr.new);
end;
/

prompt "List of log files added to log miner: "
select   to_char(low_time, 'dd-mon-yy hh24:mi:ss') lowtime,
         to_char(high_time, 'dd-mon-yy hh24:mi:ss') hightime,
         type, filesize/1024/1024 Mb, filename 
from v\$logmnr_logs;

prompt "(c) Starting log miner using online catalog.."
execute dbms_logmnr.start_logmnr(options => dbms_logmnr.dict_from_online_catalog);
prompt "(d) Querying log miner results"

set linesize 150
set pagesize 80
column usr format a10
column osusr format a10
column machine_name format a10
column xid format a12
col operation format a15
col table_name format a10
col sql_redo format a30
col sql_undo format a30

select username as usr,
       os_username as osusr,
       (xidusn ||'.'|| xidslt ||'.'||xidsqn) as xid,
       operation, 
       table_name,
       sql_redo, 
       sql_undo
  from v\$logmnr_contents
  where username in ('USERA', 'USERB');

USR     OSUSR    XID        OPERATION       TABLE_NAME  SQL_REDO                       SQL_UNDO
------  -------- ---------- --------------- ----------  ------------------------------ ------------------------------
USERA   jdoe     10.12.988  START                       set transaction read write;
USERA   jdoe     1.7.928    DDL              EMP        ALTER TABLE "USERA"."EMP" RENA
                                                        ME TO "BIN$sKOUXNE/r7TgQAB/AQE
                                                        yrA==$0" ;
...
USERA   jdoe     1.7.928    DDL              EMP        drop table emp AS "BIN$sKOUXNE
                                                        /r7TgQAB/AQEyrA==$0" ;
...
USERA   jdoe     4.32.983   DDL              EMP       create table emp as
                                                        select employee_id as empno,
                                                        first_name || ' ' ||
                                                        last_name as ename,
                                                        department_id as deptno,
                                                        salary as salary
                                                        from hr.employees;
..
USERA   jdoe     4.23.984   START                       set transaction read write;
USERA   jdoe     4.32.983   DIRECT INSERT    EMP        insert into "USERA"."EMP"("EMP delete from "USERA"."EMP" wher
                                                        NO","ENAME","DEPTNO","SALARY") e "EMPNO" = '198' and "ENAME"
                                                        values ('198','Donald OConnel  = 'Donald OConnell' and "DEPTN
                                                        l','50','2600');               O" = '50' and "SALARY" = '2600
                                                                                       ' and ROWID = 'AAASdlAAEAAAAMb
                                                                                       AAA';

...
USERA   jdoe     4.32.983   DIRECT INSERT   EMP         insert into "USERA"."EMP"("EMP delete from "USERA"."EMP" wher
                                                        NO","ENAME","DEPTNO","SALARY") e "EMPNO" = '197' and "ENAME"
                                                        values ('197','Kevin Feeney',  = 'Kevin Feeney' and "DEPTNO"
                                                        '50','3000');                  = '50' and "SALARY" = '3000' a
                                                                                       nd ROWID = 'AAASdlAAEAAAAMbABq
                                                                                       ';
...
USERA   jdoe     10.31.988  DDL             EMP         grant select, update on emp to
                                                        userb;
...
USERA   jdoe     10.31.988  UPDATE          OBJ$        update "SYS"."OBJ$" set "OBJ#" update "SYS"."OBJ$" set "OBJ#"
                                                        = '75621', "DATAOBJ#" = '7562  = '75621', "DATAOBJ#" = '7562
                                                        1', "TYPE#" = '2', "CTIME" = T 1', "TYPE#" = '2', "CTIME" = T
                                                        O_DATE('22-NOV-10', 'DD-MON-RR O_DATE('22-NOV-10', 'DD-MON-RR
                                                        '), "MTIME" = TO_DATE('22-NOV- '), "MTIME" = TO_DATE('22-NOV-
                                                        10', 'DD-MON-RR'), "STIME" = T 10', 'DD-MON-RR'), "STIME" = T
                                                        O_DATE('22-NOV-10', 'DD-MON-RR O_DATE('22-NOV-10', 'DD-MON-RR
                                                        '), "STATUS" = '1', "FLAGS" =  '), "STATUS" = '1', "FLAGS" =
                                                        '0', "OID$" = NULL, "SPARE1" = '0', "OID$" = NULL, "SPARE1" =
                                                        '6', "SPARE2" = '1' where "OB  '6', "SPARE2" = '1' where "OB
                                                        J#" = '75621' and "DATAOBJ#" = J#" = '75621' and "DATAOBJ#" =
                                                        '75621' and "OWNER#" = '92' a  '75621' and "OWNER#" = '92' a
                                                        nd "TYPE#" = '2' and "CTIME" = nd "TYPE#" = '2' and "CTIME" =
                                                        TO_DATE('22-NOV-10', 'DD-MON-  TO_DATE('22-NOV-10', 'DD-MON-
                                                        RR') and "MTIME" = TO_DATE('22 RR') and "MTIME" = TO_DATE('22
                                                        -NOV-10', 'DD-MON-RR') and "ST -NOV-10', 'DD-MON-RR') and "ST
                                                        IME" = TO_DATE('22-NOV-10', 'D IME" = TO_DATE('22-NOV-10', 'D
                                                        D-MON-RR') and "STATUS" = '1'  D-MON-RR') and "STATUS" = '1'
                                                        and "FLAGS" = '0' and "OID$" I and "FLAGS" = '0' and "OID$" I
                                                        S NULL and "SPARE1" = '6' and  S NULL and "SPARE1" = '6' and
                                                        "SPARE2" = '1' and ROWID = 'AA "SPARE2" = '1' and ROWID = 'AA
                                                        AAASAABAAAU6JAAi';             AAASAABAAAU6JAAi';
..
USERA   jdoe     10.31.988    COMMIT                    commit;
USERA   jdoe     7.26.985     START                     set transaction read write;
...
USERA   jdoe     3.23.1299    START                     set transaction read write;
USERA   jdoe     3.23.1299    UPDATE    EMP          update "USERA"."EMP" set "SALA update "USERA"."EMP" set "SALA
                                                        RY" = '2730' where "EMPNO" = ' RY" = '2600' where "EMPNO" = '
                                                        198' and "ENAME" = 'Donald OCo 198' and "ENAME" = 'Donald OCo
                                                        nnell' and "DEPTNO" = '50' and nnell' and "DEPTNO" = '50' and
                                                        "SALARY" = '2600' and ROWID =  "SALARY" = '2730' and ROWID =
                                                        'AAASdlAAEAAAAMbAAA';          'AAASdlAAEAAAAMbAAA';
...
USERA   jdoe     3.23.1299    UPDATE    EMP          update "USERA"."EMP" set "SALA update "USERA"."EMP" set "SALA
                                                        RY" = '2250' where "EMPNO" = ' RY" = '3000' where "EMPNO" = '
                                                        197' and "ENAME" = 'Kevin Feen 197' and "ENAME" = 'Kevin Feen
                                                        ey' and "DEPTNO" = '50' and "S ey' and "DEPTNO" = '50' and "S
                                                        ALARY" = '3000' and ROWID = 'A ALARY" = '2250' and ROWID = 'A
                                                        AASdlAAEAAAAMbABq';            AASdlAAEAAAAMbABq';

USERA   jdoe     3.23.1299   COMMIT                     commit;
USERA   jdoe     1.12.927    START                      set transaction read write;
USERA   jdoe     1.12.92     SELECT_FOR_UPDATE EMP      select * from "USERA"."EMP" wh
                                                     ere ROWID = 'AAASdlAAEAAAAMbAA
                                                        X' for update;
...
USERA   jdoe     1.12.927    UPDATE       EMP           update "USERA"."EMP" set "ENAM update "USERA"."EMP" set "ENAM
                                                        E" = 'Den Raphaely' where "EMP E" = 'Den Raphaely' where "EMP
                                                        NO" = '114' and "ENAME" = 'Den NO" = '114' and "ENAME" = 'Den
                                                        Raphaely' and "DEPTNO" = '30'  Raphaely' and "DEPTNO" = '30'
                                                        and "SALARY" = '11000' and RO  and "SALARY" = '11000' and RO
                                                        WID = 'AAASdlAAEAAAAMbAAX';    WID = 'AAASdlAAEAAAAMbAAX';
...
USERA   jdoe     1.12.927    UPDATE       EMP           update "USERA"."EMP" set "SALA update "USERA"."EMP" set "SALA
                                                        RY" = '2750' where "EMPNO" = ' RY" = '2500' where "EMPNO" = '
                                                        119' and "ENAME" = 'Karen Colm 119' and "ENAME" = 'Karen Colm
                                                        enares' and "DEPTNO" = '30' an enares' and "DEPTNO" = '30' an
                                                        d "SALARY" = '2500' and ROWID  d "SALARY" = '2750' and ROWID
                                                        = 'AAASdlAAEAAAAMbAAc';        = 'AAASdlAAEAAAAMbAAc';

USERB   jdoe     1.12.927    COMMIT                     commit;
...
USERB   jdoe     8.21.1521   START                      set transaction read write;
USERB   jdoe     6.16.1306   UPDATE       EMP           update "USERA"."EMP" set "SALA update "USERA"."EMP" set "SALA
                                                        RY" = '9450' where "EMPNO" = ' RY" = '9000' where "EMPNO" = '
                                                        103' and "ENAME" = 'Alexander  103' and "ENAME" = 'Alexander
                                                        Hunold' and "DEPTNO" = '60' an Hunold' and "DEPTNO" = '60' an
                                                        d "SALARY" = '9000' and ROWID  d "SALARY" = '9450' and ROWID
                                                        = 'AAASdlAAEAAAAMbAAM';        = 'AAASdlAAEAAAAMbAAM';
...
USERB   jdoe     6.16.1306    COMMIT                    commit;
USERB   jdoe     4.5.983      START                     set transaction read write;
USERB   jdoe     4.5.983      SELECT_FOR_UPDA EMP       select * from "USERA"."EMP" wh
                                           TE           ere ROWID = 'AAASdlAAEAAAAMbAA
...
USERB   jdoe     4.5.983      UPDATE     EMP         update "USERA"."EMP" set "ENAM update "USERA"."EMP" set "ENAM
                                                        E" = 'Steven King' where "EMPN E" = 'Steven King' where "EMPN
                                                        O" = '100' and "ENAME" = 'Stev O" = '100' and "ENAME" = 'Stev
                                                        en King' and "DEPTNO" = '90' a en King' and "DEPTNO" = '90' a
                                                        nd "SALARY" = '24000' and ROWI nd "SALARY" = '24000' and ROWI
                                                        D = 'AAASdlAAEAAAAMbAAJ';      D = 'AAASdlAAEAAAAMbAAJ';
...
USERB   jdoe     4.5.983      COMMIT                    commit;
...
188 rows selected.

(e) End the Log Miner Section
prompt "(e) Ending log miner section.."
execute dbms_logmnr.end_logmnr();
exit;
EndOfSQL


ERRORCODE=$?

# Check the return code from SQL Plus
if [ $ERRORCODE != 0 ]
then
 echo ********************************
 echo "ERROR: SQL*Plus failed with error code: $ERRORCODE"
else
 echo ********************************
 echo "SQL*Plus completed successfully. Error code: $ERRORCODE"
fi

Using the Log Miner (I)



Using the LogMiner
  • First appeared in Oracle 8i
  • Log Miner allows for analysis of online and archived redo log files.
  • LogMiner provides a well-defined, easy-to-use, and comprehensive relational interface to redo log files

Enhancements in Oracle 11g
  • LogMiner was integrated with OEM
  • Also integrated with the new flashback transaction feature
  • Can be used from command line or through OEM

Possible uses:
  • Find out when a logical error happened and who did it.
  • This information in turn can be used to determine when to initiate time-based or change-based recovery (V$LOGMNR_CONTENTS)
  • Determine what actions are needed to perform fine-grained recovery at the transaction level (flashback transaction)
  • Support for trend analysis (find out which databases get most DMLs)
  • Support on post-facto auditing.
  • Useful to find out who has updated a given table (or set of tables).
  • Explore what happens when a DML/DDL is issued against the database

Configuring the Log Miner
Four objects are used in a LogMiner configuration:
  1. The Source database
  2. The Mining database
  3. The LogMiner dictionary - used to translate internal object identifiers to object names and external data formats.
  4. Redo log files that will be analyzed

Managing LogMiner operation:
  • Use SYS.DBMS_LOGMNR and SYS.DBMS_LOGMNR_D packages to (a) select redo log files for analysis, (b) begin and (c) end log miner section.
  • Use V$LOGMNR_CONTENTS view to query the contents of redo logs.
  • You must be connected as SYS or have EXECUTE_CATALOG_ROLE role

DBMS_LOGMNR package subprograms:
SQL> dbms_logmnr.add_logfile(LOGFILENAME => logname, OPTIONS => dbms_logmnr.new);
-- Add redo log file to a list of redo logs for LogMiner to process.
    OPTIONS:
    • new -- implicit call to dbms_logmnr.end_logmnr and start a new log miner session. Creates a new list and add the redo log.
    • addfile -- Adds the redo log to the existing list
SQL> dbms_logmnr.remove_logfile(LOGFILENAME => logname);
-- Remove redo from list
SQL>  dbms_logmnr.start_logmnr(OPTIONS => dbms_logmnr.dict_from_online_catalog);
-- Initialized the LogMiner
    OPTIONS:
    • committed_data_only
      • Return committed statements only. (none rolled back or in progress)
      • Group statements of a committed transaction.
      • Transactions returned in order.
    • skip_corruption
      • skips corruptions in the redo log (redo log block corruption)
    • ddl_dict_tracking
      • Used when dictionary is in a flat file. Updates dict references as DDL are processed
    • dict_from_online_catalog
      • directs log miner to use the online dictionary of the database when translating object names
    • dict_from_redo_logs
    • no_sql_delimiter
      • Useful if you want to use the reconstructed statements directly in a open cursor
    • no_rowid_in_stmt
    • print_pretty_sql
    • continuous_mine
      • Instructs log miner to add redo log files, as needed, until find the data on the specified SCN or timestamp
    • string_literals_in_stmt
SQL> dbms_logmnr.end_logmnr();
-- Finishes a LogMiner session
Requirements to use LogMiner
  1. Source and Mining databases
    • Both must run on the same platform
    • mining db can be the same or separate from source db
    • mining db must be same or later release of the source db
    • mining db must use same characterset (or superset) of source db
  2. LogMiner dictionary
    • Must be produced from the source db
    • Used to translate redo log information into a meaningful format
    • Used to display table and column names instead of their internal IDs.
    • Without a dictionary, LogMiner also display all values in hexadecimal format.
  3. Redo Logs
    • must be produced by the same source db
    • associated with the same database RESETLOGS SCN
    • Must be from oracle 8.0 or later (mostly 9i or later)
  4. Supplemental Logging
    • must be enabled before redo logs are generated
    • Enable with: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
    • Logs the extra information necessary to reconstruct the SQL statement as well
      as one to revert the original action.
    • Without supplemental logging instance and media recovery is possible, but log mining,
      or reconstruction of the original SQL statement, is not possible.
SQL> select supplemental_log_data_min,supplemental_log_data_pk, 
     supplemental_log_data_fk, supplemental_log_data_all
     from v$database;

SUPPLEMENTAL_LOG_DATA_MIN SUPPLEMENTAL_LOG_DATA_PK SUPPLEMENTAL_LOG_DATA_FK SUPPLEMENTAL_LOG_DATA_ALL 
------------------------- ------------------------ ------------------------ ------------------------- 
YES                       YES                      YES                      NO                       
About the LogMiner dictionary
Used to translate the information in the redo log files into object names and display the data in alpha numeric, instead of hexadecimal format.
(a) You can use the online catalog of the source database
  • For this, the source database must be online and available
  • To use the online catalog: SQL> execute dbms_logmnr.start_logmnr( options => dbms_logmnr.dict_from_online_catalog);
(b) Can be extracted from source database into the redo log files
  • Used when the source database is not available
  • In order to extract dictionary information, the source database must be (1) open, (2) in archivelog mode, (3) with enabled archiving.
  • To extract dictionary: SQL> execute dbms_logmnr_d.build( options => dbms_logmnr_d.store_in_redo_logs);
  • The dictionary information is stored in the archived redo logs. To find out which:
    • SQL> select name from v$archived_log where dictionary_begin = 'YES';
    • SQL> select name from v$archived_log where dictionary_end = 'YES';
(c) Can be extracted from source db to flat file
  • Available for backward compatibility only. no trasactional consistency.



Example 1: Find all modifications in the last archived redo log
  • Mining and source db are the same
  • Using Online catalog as dictionary

Oracle Flashback Technology (I)




Oracle Flashback technology
Logical Flashback (do not depend on RMAN, rely on undo data)
Physical flashback
New on Oracle 11g:



  • Oracle Flashback features use the Automatic Undo Management to obtain metadata and transaction historical data.
  • Undo data is persistent and survives database shutdown.
  • You can use the Flashback options to
    • recover data from user errors,
    • compare table data at two points in time,
    • view transaction actions (the set of actions performed in a given transaction).
    • Undo table drops
    • Revert the entire database to a previous point in time.

Configuring the database for Flashback options
Database must be configured for Automatic Undo Management (default on 11g).
For this you need:
  • (1) Size undo tablespace; and
  • (2) Enable automatic undo management

(Step 1) Create or resize the undo tablespace appropriately
The Undo tablespace must have enough space to keep the data required for flashback operations
(a) check the size of the existing undo tablespaces

SQL> select t.tablespace_name, t.status, t.contents, t.extent_management, 
            t.allocation_type,   t.retention, s.sizemb 
     from dba_tablespaces t, 
           (select tablespace_name, sum(bytes)/1024/1024 sizemb  
              from dba_data_files
              group by tablespace_name) s
     where t.tablespace_name = s.tablespace_name
     and t.contents = 'UNDO';

TABLESPACE_NAME                STATUS    CONTENTS  EXTENT_MANAGEMENT ALLOCATION_TYPE RETENTION   SIZEMB                 
------------------------------ --------- --------- ----------------- --------------- ---------   ---------------------- 
UNDOTBS1                       ONLINE    UNDO      LOCAL             SYSTEM          NOGUARANTEE 60      

(b) Check the current retention period: 
Query v$undostat to check the amount of time (seconds) for which undo will not be recycled.
    
SQL> select to_char(begin_time, 'dd-MON  hh:mi') begin_time, 
       to_char(end_time, 'dd-MON  hh:mi') end_time, 
       tuned_undoretention undoretention_sec
from v$undostat;

BEGIN_TIME    END_TIME      UNDORETENTION_SEC      
------------- ------------- ---------------------- 
19-OCT  09:51 19-OCT  09:58 1911     --  At current workload, undo is preserved for about 30 minutes
19-OCT  09:41 19-OCT  09:51 1608                   
...
19-OCT  03:11 19-OCT  03:21 1787                   
19-OCT  03:01 19-OCT  03:11 1183       
(Step 2) Enable automatic undo management (undo parameters)
  • UNDO_MANAGEMENT = [ AUTO (default) | MANUAL ]
  • UNDO_TABLESPACE - specifies the name of the undo tablespace
  • UNDO_RETENTION - specifies the minimum amount of time that Oracle attempts to retain old undo information before overwriting it.
    • The value for UNDO_RETENTION is ignored for a fixed size undo tablespace
    • If AUTOEXTEND is enabled, database attempts to honor UNDO_RETENTION.
    • 'snapshot too old' errors indicate that undo retention is not enough for flashback operations.
    • To accomodate Oracle Flashback features, you can set the UNDO_RETENTION parameter to a value equal to the longest expected Oracle Flashback operation.
    • If retention is very important, use ALTER TABLESPACE...RETENTION GUARANTEE. Here the database never overwrites unexpired undo data even if it means that transactions fail due to lack of undo space.
    • To set: ALTER SYSTEM SET UNDO_RETENTION = 2400;
(a) check instance parameters

SQL> select name, value, isdefault, description
     from v$parameter
     where name like '%undo%';

NAME            VALUE    ISDEFAULT DESCRIPTION
--------------- ------   --------- ---------------------------------------------------
undo_management AUTO     TRUE      instance runs in SMU mode if TRUE, else RBU mode -- default: AUTO (11g), Manual (before 11g).
undo_tablespace UNDOTBS1 FALSE     use/switch undo tablespace
undo_retention  900      TRUE      undo retention in seconds


Notes on Flashback Query
  • Flashback query can be used with remote tables (table@dblink)
  • Queries on V$ views ALWAYS return current data
  • Flashback query can be used with static dictionary views
  • To query past data at a precise time, use an SCN.
  • With timestamp, the actual time queried might be up to 3 seconds earlier than the time you specify.
  • Oracle Flashback Drop - Reverse the effects of DROP TABLE

Using FLASHBACK QUERY
  • Use SELECT.. AS OF [ TIMESTAMP timestamp| SCN scn ]
  • The query returns committed data as it existed at that point.
  • To use flashback query on a table, the user needs to have FLASHBACK and SELECT privileges on that object.
Case:
(1) Some rows from emp table are deleted by mistake at 11 AM.
(2) Error discovered at 11:20AM.
(3) Use Flashback query to see the data as it was before the 11am delete.
(1) Check table rows at 11:00AM
SQL> select current_scn, to_char(systimestamp, 'mm-dd-yy  HH24:mi:ss') time
     from v$database;

CURRENT_SCN            TIME               
---------------------- ------------------ 
1385809                12-08-10  11:00:22

SQL> select employee_id, last_name,  salary
     from hr.emp
     where department_id =30;

EMPLOYEE_ID            LAST_NAME                 SALARY                 
---------------------- ------------------------- ---------------------- 
114                    Raphaely                  11000                  
...
119                    Colmenares                2500    


(2) At 11:20, rows are incorrectly deleted from emp.

SQL> delete from hr.emp where department_id=30;
SQL> commit;
SQL> select current_scn, to_char(systimestamp, 'mm-dd-yy  HH24:mi:ss') time
     from v$database;
CURRENT_SCN            TIME               
---------------------- ------------------ 
1386301                12-08-10  11:20:03

SQL> select employee_id, last_name,  salary
     from hr.emp
     where department_id =30;

EMPLOYEE_ID            LAST_NAME                 SALARY                 
---------------------- ------------------------- ---------------------- 

(3) Use flashback query to see emp as it was at 11 AM

SQL> select employee_id, last_name, salary
     from hr.emp AS OF TIMESTAMP to_timestamp('12-08-10 11:00:00', 'mm-dd-yy HH24:MI:SS')
     where department_id = 30;

EMPLOYEE_ID            LAST_NAME                 SALARY                 
---------------------- ------------------------- ---------------------- 
114                    Raphaely                  11000                  
...
119                    Colmenares                2500    

(4) Alternatively you can use the SCN 

SQL> select employee_id, last_name, salary
     from hr.emp AS OF SCN 1385809
     where department_id = 30;

EMPLOYEE_ID            LAST_NAME                 SALARY                 
---------------------- ------------------------- ---------------------- 
114                    Raphaely                  11000                  
...
119                    Colmenares                2500 

(5) Restore the data copying it from the earlier version of the table:

SQL> insert into hr.emp 
       (select * 
        from hr.emp AS OF TIMESTAMP to_timestamp('12-08-10 11:00:00', 'mm-dd-yy HH24:MI:SS')
        where department_id = 30 );

6 rows inserted.

Using Flashback Version Query
  • You can retrieve the different versions of a given row that existed during a given time interval.
  • Use VERSIONS { BETWEEN {SCN | TIMESTAMP} start AND end}
  • Returns one row for each version of the existed at any time in the specified interval
(a) check the initial values of the row data, current scn and timestamp
SQL> select employee_id, first_name, last_name, salary, commission_pct
     from hr.emp
     where employee_id = 116;

EMPLOYEE_ID            FIRST_NAME           LAST_NAME                 SALARY                 COMMISSION_PCT         
---------------------- -------------------- ------------------------- ---------------------- ---------------------- 
116                    Shelli               Baida                     2900                                          
                     
SQL> select current_scn, to_char(systimestamp, 'mm-dd-yy  HH24:mi:ss') time
     from v$database;

URRENT_SCN            TIME               
---------------------- ------------------ 
1400261                12-08-10  16:15:20

(b) update salary, and commission
SQL> update hr.emp
     set salary = salary*1.5
     where employee_id = 116;
SQL> commit;

SQL> update hr.emp
     set commission_pct = .12
     where employee_id = 116;
SQL> commit;

(c) Query table emp pseudocolumns (generated by the supplemental logging)
SQL> select versions_startscn as ver_startscn, 
            versions_starttime as ver_startime, 
            versions_endscn as ver_endscn, 
            versions_endtime as ver_endtime,
            versions_xid as ver_xid, 
            versions_operation as oper,
            employee_id as emp_id, salary, commission_pct as comm_pct
      from hr.emp
        versions between timestamp
             to_timestamp('12-08-10 16:14:00', 'mm-dd-yy HH24:MI:SS')
        and  to_timestamp('12-08-10 16:16:30', 'mm-dd-yy HH24:MI:SS')
     where employee_id = 116;

VER_STARTSCN VERS_STARTTIME        VER_ENDSCN  VER_ENDTIME            VER_XID          OPER EMP_ID  SALARY   COMM_PCT 
------------ --------------------- ----------- ---------------------- ---------------- ---- ------- -------- -------- 
1400294      08-DEC-10 04.16.13 PM  1400301    08-DEC-10 04.16.25 PM  0A00100044030000 U    116     4350     0.12 
1400273      08-DEC-10 04.15.49 PM  1400294    08-DEC-10 04.16.13 PM  0A00030043030000 U    116     4350
                                    1400273    08-DEC-10 04.15.49 PM                        116     2900
The pseudo columns are:
VERSIONS_[ STARTSCN | STARTTIME ] Display the SCN or TIMESTAMP when row took on this value.
If the row was created before the lower bound SCN ot TIMESTAMP, a NULL is returned.
VERSIONS_[ ENDSCN | ENDTIME ] Display the last SCN and TIMESTAMP when row had this value.
If the value is still current at the upper bound SCN or TIMESTAMP a NULL is returned.
VERSIONS_XID ID of the transaction that created the row version.
VERSIONS_OPERATION Operation performed by the transaction ((I)nsert, (U)pdate or (D)elete)


Using Flashback Transaction Query
  • Extension to the Flashback Query Version option
  • Used to retrieve information for a given transaction or for all transactions in a given time interval.
  • The transaction IDs (listed in the VERSIONS_XID column) are used to query the FLASHBACK_TRANSACTION_QUERY view
  • The database must have at least minimal supplemental logging enabled
(a) Query the transaction that updated salary of employee_id 116.
col logon_user format a10
col table_name format a10
col table_owner format a10
col operation format a10
col undo_sql format a50

SQL> select logon_user, operation, table_name, 
       to_char(start_timestamp, 'mm-dd-yy hh24:MI:ss') time, row_id, undo_sql
     from flashback_transaction_query
     where xid = hextoraw('0A00030043030000');

LOGON_USER OPERATION  TABLE_NAME TIME               ROW_ID              UNDO_SQL
---------- ---------- ---------- ------------------ ------------------- --------------------------------------------------
SYSTEM     UPDATE     EMP       12-08-10 16:15:46  AAASNxAAEAAAAJHAAB  update "HR"."EMP" set "SALARY" = '2900' where
                                                                         ROWID = 'AAASNxAAEAAAAJHAAB';
SYSTEM     BEGIN

Example: check the various actions performed by a given transaction
SQL> select current_scn from v$database;

CURRENT_SCN            
---------------------- 
1424010

SQL> create table emp
     (empno number, 
      empname varchar2(10),
      salary number);

SQL> select current_scn from v$database;
SQL> insert into emp values (1, 'John', 20000);
SQL> commit;

SQL> update emp set salary = salary*1.2 where empno=1;
SQL> commit;

SQL> delete from emp where empno = 1;
SQL> commit;

SQL> insert into emp values (1, 'Jack', 45000);   -- transaction performs multiple actions 
SQL> update emp set salary = salary*1.05;
SQL> commit;

SQL> update emp set salary = salary + 3320;
SQL> commit;

SQL> select current_scn from v$database;

CURRENT_SCN            
---------------------- 
1424312

(a) To retrieve the various versions of the row: 
SQL> select versions_xid xid, versions_startscn start_scn,
        versions_endscn end_scn, versions_operation operation,
        empname, salary
     from emp
       versions between scn minvalue and maxvalue
     where empno = 1;
/
XID              START_SCN              END_SCN                OPERATION EMPNAME    SALARY                 
---------------- ---------------------- ---------------------- --------- ---------- ---------------------- 
0200060044040000 1424201                                       U         Jack       50570                  
0600080064040000 1424197                1424201                I         Jack       47250                  
05000A006F040000 1424192                                       D         John       24000                  
                                        1424192                          John       24000


(b) The transaction '0600080064040000' inserted the new record with a wrong name. 
To audit all the changes made by this transaction: 

SQL> select xid, start_scn, commit_scn, operation, logon_user, undo_sql
     from flashback_transaction_query
     where xid = hextoraw('0600080064040000')

XID              START_SCN  COMMIT_SCN OPERATION  LOGON_USER UNDO_SQL
---------------- ---------- ---------- ---------- ---------- --------------------------------------------------
0600080064040000 1424195    1424197    UPDATE     SYSTEM     update "SYSTEM"."EMP" set "SALARY" = '45000' where
                                                             ROWID = 'AAASXdAABAAAVBJAAB';

0600080064040000 1424195    1424197    INSERT     SYSTEM    delete from "SYSTEM"."EMP" where ROWID = 'AAASXdAA
                                                            BAAAVBJAAB';

0600080064040000    1424195    1424197 BEGIN   SYSTEM


Using Flashback Table

Flashback Table x Flashback Drop
  • FLASHBACK TABLE to SCN uses undo data to revert DMLs:
    • Delete rows inserted since scn_num
    • Update back rows modified since scn_num
    • Insert rows deleted since scn_num
  • FLASHBACK TABLE to BEFORE DROP uses a recycle bin to restore dropped table.
  • None of them, however, recover TRUNCATED rows.
  • For this you need to use FLASHBACK DATABASE

Allows point-in-time recovery for a table:
  • restore point specified by timestamp or SCN
  • table can stay online while operation executes
  • maintains all table attributes (indexes, triggers, constraints, etc)
  • maintains any remote state in a distributed environment
  • maintains data integrity specified by constraints

Requisites:
  • User must have FLASHBACK ANY TABLE or FLASHBACK object privilege on the table
  • Must have SELECT, INSERT, DELTE and ALTER privileges on the table
  • Must have SELECT ANY DICTIONARY or FLASHBACK ANY TABLE system privilege or SELECT_CATALOG_ROLE role

For an object to be eligible to be flashed back:
  • Object MUST NOT be: part of a cluster, materialized views, AQ tables, static data dictionary tables, system tables, remote tables, object tables, nested tables, or individual partitions or subpartitions.
  • Table structure must not have been changed between now and the point of restore
  • Row movement must be enabled (rowids will change)
  • Enough undo data to perform flashback exists on the undo tablespaces.

(a) enable row movement

SQL> alter table emp enable row movement;

SQL> select * from emp;
EMPNO                  EMPNAME    SALARY                 
---------------------- ---------- ---------------------- 
1                      Jack       50570        

(b) check current scn (before flashback)

SQL> select current_scn from v$database;
CURRENT_SCN            
---------------------- 
1426179

(c) Insert and update data row data

SQL> Insert into emp values (2, 'Mary', 2000);
SQL> commit;
SQL> select current_scn from v$database;

CURRENT_SCN            
---------------------- 
1426185 

SQL> insert into emp values(100, 'Joseph', 450);
SQL> commit;
SQL> select current_scn from v$database;

CURRENT_SCN            
---------------------- 
1426200   

SQL> update emp set salary = salary*2;
SQL> commit;
SQL> select current_scn from v$database;

CURRENT_SCN            
---------------------- 
1426208 

(d) ensure that enough undo data exists to flashback the table

SQL>  select name, value/60 minutes_retained
      from v$parameter
      where name = 'undo_retention';

NAME              MINUTES_RETAINED       
----------------- ---------------------- 
undo_retention    80                     
 
(e) determine whtehr the table has dependencies on other tables. 
If dependencies exist, these may need to be flashbacked also

SQL>  select other.owner, other.table_name
    from sys.all_constraints this
         sys.all_constraints other
    where this.owner = 'SYSTEM'
    and   this.table_name = 'EMP'
    and   this.r_owner = other.owner
    and   this.r_constraint_name = other.constraint_name
 and   this.constraint_type = 'R';


(f) Check new data

SQL>  select * from emp;

 EMPNO                  EMPNAME    SALARY                 
---------------------- ---------- ---------------------- 
2                      Mary       4000                   
1                      Jack       101140                 
100                    Joseph     900  


(g) flashback table to point in time (SCN) before  data modification

SQL> flashback table emp to scn 1426179;

SQL> select * from emp;

EMPNO                  EMPNAME    SALARY                 
---------------------- ---------- ---------------------- 
1                      Jack       50570                  


(h) flashback table forward to after data modification

SQL> flashback table emp to scn 1426208;

SQL>  select * from emp;
 EMPNO                  EMPNAME    SALARY                 
---------------------- ---------- ---------------------- 
2                      Mary       4000                   
1                      Jack       101140                 
100                    Joseph     900