-dbms_logmnr log excavator, analyze the tools for database recruit logs - can analyze online weight logs, more suitable for archive redo log documents. DBMS_Logmnr is the new package provided by Oracle in Oracle8i. It is mainly used to analyze the log file file (including Online Redo Log File, Archived Log File), and the information in the log file is used to V $ logmnr_contents, thereby obtaining historical information for Oracle database operations. It can not only analyze Oracle8i's log file, but also analyze the log file of Oracle8. Information mainly includes what changes have been made during database data in your analysis time limit, which is executed. 1. Create a data dictionary file to make more convenient reading log information premise: UTL_FILE, you need to perform DBMS_LOGMNR_D (default: execute_catalog_role has permission) Begin sys.dbms_logmnr_d.build ('oratom_dic.bat', 'E: / UTL '); end; / 2. Create log file list begin sys.dbms_logmnr.dd_logfile (' D: /oracle/oradata/oRatom/redo03.logw); end; / 3 . Use the logminer for log analysis
Parameter Parameter Type Default Meaning STARTSCN Digital (NUMBER) 0 Analysis of SCN ≥ STARTSCN Log File Some endscn Digital (Number) 0 Analysis of the SCN ≤ENDSCN Log file section STARTTIME Date (DATE) 1998- 01-01 Analysis of the Time Stamp ≥ StartTime Log File Some EndTime Date (DATE) 2988-01-01 Analysis Refocular Log Time Stamp ≤ENDTIME log file section DictFileName Character type (varchar2) Dictionary file, this The file contains a snapshot of a database directory. Using this file can make the analysis result is a text form that can be understood, not 16 in-system inside.
Options binary_integer 0 system debug parameters, actually rarely
Begin sys.dbms_logmnr.start_logmnr (DictFileName => 'E: /UTL/Oratom_dic.bat'); end; / 4. Observation analysis results (V $ logmnr_contents) SELECT SCN, SQL_REDO from V $ logmnr_contents; 5. Termination Log Analysis Transaction At this time, the PGA memory area is cleared, and the analysis results are also no longer existed, and execute sys.dbms_logmnr.end_logmnr;