数据库的日志文件（Database log file）.docVIP

数据库的日志文件（Database log file） Analyze the Oracle database log file (1) As Oracle DBA, we sometimes need to track malicious operation of data deletion or users, we not only need to find out these operations database account, also need to know the operation by which client (IP address) issued. To solve these problems, one of the most effective, practical and low-cost methods is to analyze the log files of the Oracle database. This article will make a deep discussion about Oracle log analysis technology. How to analyze, that is, LogMiner interpretation 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 log information, and the other is to format trace files. Through the analysis of logs, we can achieve the following objectives: 1. Identify logical changes to the database; 2, to detect and correct the users misoperation; 3, the implementation of ex 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). What we need to note here is the equivalent statement, not the original SQL statement, for example: we initially implemented the delete a where lt C1; cyx; and the LogMiner refactoring was equivalent to the 6 DELETE statement. 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