LogMiner in its original form has had some limitations associated with its use. With the
original approach, you could only review one log file at a time, and the interface to the tool was
cumbersome to use. In Oracle9i, a major overhaul of the interface has been implemented, and
the functionality has been greatly enhanced, including a LogMiner Viewer for use with the Oracle
Enterprise Manager. Both the manual approach to using LogMiner and the OEM LogMiner Viewer
are presented within this section.
How LogMiner Works
To run the LogMiner utility, you must have either the EXECUTE privilege on the DMBS_LOGMNR
package or the EXECUTE_CATALOG_ROLE role. LogMiner requires a data dictionary to fully
translate the redo log file contents and translate internal object identifiers and datatypes to object
names and external data formats. If a data dictionary is not available, LogMiner will return the
data in hex format and the object information as internal object IDs.
You have three choices for obtaining a data dictionary for LogMiner use:
Chapter 14: Miscellaneous High Availability Features 501
Extract the data dictionary information to a flat file.
Extract the data dictionary to redo log files.
Use the online data dictionary from the current database.
The LogMiner analysis usually requires that the data dictionary in use was generated from the
same database that generated the redo log files. However, if you are using a flat file format or are
using the data dictionary from redo log files, you can analyze the redo log files either from the
database on which LogMiner is running or from another database.
Pages:
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758