This
option works only if a block in the actual redo log
file is corrupted and does not work if the corruption
is in the header block.
DDL_DICT_TRACKING Enables LogMiner to update the internal data
dictionary if a DDL event occurs, to ensure that
SQL_REDO and SQL_UNDO information is
maintained and correct.
DICT_FROM_ONLINE_CATALOG Instructs LogMiner to use the online data dictionary
instead of a flat file or redo log file stored dictionary.
DICT_FROM_REDO_LOGS Instructs LogMiner to use the data dictionary stored
in one or more redo log files.
NO_SQL_DELIMITER Instructs LogMiner not to place the SQL delimiter (;)
at the end of reconstructed SQL statements.
NO_ROWID_IN_STMT Instructs LogMiner not to include the ROWID clause
in the reconstructed SQL statements.
PRINT_PRETTY_SQL Instructs LogMiner to format the reconstructed SQL
for ease of reading.
CONTINUOUS_MINE Instructs LogMiner to automatically add redo log
files to find the data of interest. Specify the starting
SCN, date, or the first log to mine. LogMiner must
be connected to the same database instance that is
generating the redo log files.
TABLE 14-2 Values for the START_LOGMNR Options
504 Oracle Database 11g DBA Handbook
You can specify the location of the data dictionary file as follows:
execute DBMS_LOGMNR.ADD_LOGFILE(
DictFileName=> '/oracle/ora10/dictionary.ora',
After you??™ve told LogMiner the location of the data dictionary and added the redo log files,
you can begin analyzing the redo log files using the DBMS_LOGMNR.
Pages:
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762