How to analyze Oracle archive logs

With logminer analysis, you can get the original operation SQL statement, want to see the source **, tomcoding

In Object Explorer, "Manage", "SQLSserver Logs", and then double-click "Current DateTime."

View logs related to the job.

In Object Explorer, sqlserver, right-click Pose Karma, and then click View History, the Job History and SQL logs are displayed.

View logs related to the maintenance plan.

In Object Explorer, Manage, right-click Maintenance Plans, and then click View History, the Maintenance Plans, Job History, and SQL logs are displayed.

For important production services, it is recommended to enable the archiving splitting mode, through the archiving of ** logs, you can restore the code data when the data is lost, some operations can only be implemented in the archive mode, and the content of the analysis log can be blinded.

To enable the archiving function for a non-archival database, perform the following steps:

1)sql2)sql3)sql4)sql5)sql6)sql7)sql

An archive log is a backup of the redo log, and the redo log records all changes to the data (DML, DDL, or structural changes made by the administrator to the data, etc.), which can be restored by the user's data or other files by the user.

Database backup can be divided into many kinds, commonly used exp and rman, etc., rman backup needs to turn on the archive state, that is, rman backup and archive logs are closely related, rman backup can back up control files, data files, redo log files and other files, more comprehensive.

On the other hand, the exp logical backup is the data in the data file.

The difference is that exp can only restore data from the database, while archive logs can restore data and other files (using RMAN backup).

Archive logs need to be used in conjunction with RMAN backups, and cannot be compared with database backups separately, which makes little sense.

The recovery of a database is a two-step process.

1. Restore the backup file to the point in time of the last backup;

2. Restore from the point in time of 1 to the point in time when the database is shut down based on the archive logs and online redo logs.

Archiving logs record changes to database data, while database backups back up a complete database and retaining the complete data for restoration in case the database file is corrupted.