oracle 分析日志（Oracle分析日志）.docVIP

oracle 分析日志（Oracle分析日志） A LogMiner analysis, how to explain From the current point of view, the analysis method is to use only the Oracle log provided by Oracle LogMiner to Oracle, all changes are recorded in the database log, but the original log information we cannot understand, but LogMiner is let us read log information tool. From this point of view, it is similar to tkprof, one is used to analyze the log information, a file format is tracking. Through the analysis of the log, we can achieve the following purposes: 1, identify the database logical change; 2 reconnaissance, misoperation and correct user; 3, implementation of post audit; 4, perform change analysis. Not only that, the information recorded in the log database also includes: the history of changes, change type (INSERT, UPDATE, DELETE, DDL etc.), change the corresponding SCN number, and performs these operations such as user information, LogMiner log analysis, the reconstruction of the equivalent SQL statement and UNDO statement (recorded in the V$LOGMNR_CONTENTS view SQL_REDO and SQL_UNDO). To note here is that the statement is equivalent, but not the original SQL statement, for example: our initial implementation of the delete a where C1 cyx; and LogMiner, reconstruction is equivalent to 6 DELETE statements. So we should realize the display in the V$LOGMNR_CONTENTS view is not the original reality, from the perspective of the database which is easy to understand, it is a record of $operation is the same as delete a where C1 cyx; statement, in different environments, the actual number of records deleted may vary, so records of such statements is actually not what practical significance, LogMiner reconstruction is a single statement into a binary operation in the actual case. In addition because the object is not the original Oracle record in the redo log (such as table and the column name), but just their internal number in the Oracle database (table is for them in the database object ID, and for the