START_LOGMNR package.
For example, the following command analyzes log files over a range of times:
execute DBMS_LOGMNR.START_LOGMNR(
DictFileName => '/oracle/dictionary.ora',
StartTime => TO_DATE('01-SEP-2007 12:45:00', DD-MON-YYYY HH:MI:SS')
EndTime => TO_DATE('01-OCT-2007 00:00:00', DD-MON-YYYY HH:MI:SS'));
NOTE
Using the timestamp will not ensure ordering of the redo records.
You must use the SCN numbers to ensure the order of the records.
You can use SCN values to filter data as follows:
execute DBMS_LOGMNR.START_LOGMNR(
DictFileName => '/oracle/dictionary.ora',
StartScn => 125,
EndScr => 300);
If you do not enter start and end times or a range of SCN numbers, the entire file is read for every
select statement that you issue.
To look at the redo and undo code, you select the SQL_REDO and SQL_UNDO columns as
follows:
select sql_redo, sql_undo
from V$LOGMNR_CONTENTS;
You can use the OEM Server Manager Console to launch the Java-based LogMiner Viewer to
view redo and archived redo logs. To launch the LogMiner Viewer on a Windows platform, use
the Start | Programs | Oracle_Home | Oracle Enterprise Manager Console option. Once you have
connected to the Java-based OEM Server Console (Oracle Database 10g and earlier), select the
database on which you want to run the LogMiner Viewer. Ensure that the database has been started.
To start the LogMiner Viewer, highlight the database and right-click. Move the cursor to the
Related Tools option and then move to the LogMiner Viewer option.
Pages:
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763