You must modify the initialization file and
then stop and restart the database.
To execute the DBMS_LOGMNR_D.BUILD procedure, you must specify a filename for the
dictionary, the directory pathname for the file, and whether you want the dictionary written to a
flat file or redo log files. To extract the data dictionary to a flat file located in the directory G:\
Oracle\Ora10\database with the filename mydb_dictionary, you issue the following command:
execute DBMS_LOGMNR_D.BUILD
('mydb_dictionary.ora',
'G:\Oracle\Ora10\database',
options=>DBMS_LOGMNR_D.STORE_IN_FLAT_FILE);
You can use DBMS_LOGMNR_D.STORE_IN_FLAT_FILE as the other option.
?–
?–
?–
502 Oracle Database 11g DBA Handbook
Once you have the dictionary stored in a flat file, you can copy it to another platform to
run LogMiner. You may need to run dbmslmd.sql on the other database to establish the correct
environment. The dbmslmd.sql file can be found in the $ORACLE_HOME\rdbms\admin
directory on a Unix system.
Analyzing One or More Redo Log Files
To analyze redo log files using LogMiner, follow these steps:
1. Obtain a list of the available redo log files using V$LOGMNR_LOGS.
2. Start the LogMiner utility using the DBMS_LOGMNR.START_LOGMNR procedure. See
Table 14-2, later in this section, for the START_LOGMNR parameters.
3. Query V$LOGMNR_CONTENTS to see the results.
4. Once you have finished viewing the redo logs, issue the following command to end the
session:
execute DBMS_LOGMNR.
Pages:
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760