http://www.itpub.net/245264.html
Simple analysis of RMAN operation
In my previous article, I demonstrate a specific example of RMAN backup recovery. (Reference: http://www.dbanotes.net/oracle/rman...lfile_howto.htm) RMAN is analyzed for some specific calls of dbms_backup.restore. By setting the DEBUG mode, we can track a large number of logs to provide a certain description for analysis. Assuming us to submit the following command: rman target / debug trace = d: /rman_trace.log By viewing the log us, RMAN first determines the status: DBGSQL: Exec SQL At Target Select Decode (Status, 'Open', 1, 0 ) INTO: B1 from V $ INSTANCE DBGSQL: SQLCODE = 0dbgsql:: b1 = 1 Judging whether the database is in the OPEN state. Then, go to get the compatible parameter value of the database. Next, call DBMS_BACKUP_RESTORE to determine version information available for RMAN. Corresponding to the following parameters: protocol_version_number_min NUMBER: = 8; protocol_release_number_min NUMBER: = 0; protocol_update_number_min NUMBER: = 4; protocol_version_number_max NUMBER: = 9; protocol_release_number_max NUMBER: = 2; protocol_update_number_max NUMBER: = 0; 804-920, available within this range 804? 920? Is it very familiar? Call the DBMS_RCVMAN's getPackageVersion function ($ ORACLE_HOME / RDBMS / Admin / Recover.BSQ Create DBMS_RCVMAN, and get relevant comments) Get the version available information of the package. 08.00.04 to 09.02.00 Next RMAN will query V $ dataBase, get information from Name, ResetLogs_Time, ResetLogs_change #, DBID. Below this more important, get checkpoint records in X $ KCCCP (Kernel Cache Checkpoint Progress: SQL: SELECT NVL (MAX (CPMID), 0) from x $ kcccp where cpsta = 2 After these operations, RMAN V $ OPTION Get related information, including: 'Parallel Backup and Recovery', 'Incremental Backup and Recovery', 'Duplexed Backups', 'Block Media Recovery', 'Point-in-Time TableSpace Recovery', to determine databases Whether it has these functions. Then the LOG is displayed to the target database. The analysis process is not complicated, but it will produce a large number of logs when they involve in-depth orders, and have certain patience to continue. When there is a fault in RMAN, it is a very effective way to analyze the Debug mode. If possible, I will give a few examples in the subsequent article.
