Rman simple analysis
Http://www.itpub.net/245264.html
Rman simple analysis
In my last article we demonstrated rman for backup and recovery of a specific example. (Reference: http://www.dbanotes.net/Oracle/Rman…lfile_howto.htm)
Rman of the specific call dbms_backup.restore End î¼ shoot Yun ü îŠ î“ª ebug analysis out.
By setting debug mode, we could track a large number of Log, so as to provide some of that. Assume that we submit the following order:
Rman target / debug trace = d: / rman_trace.log
We have to see through the log, rman state database to determine:
DBGSQL: EXEC SQL AT TARGET select decode (status, 'OPEN', 1,0) into: $ instance b1 from v
DBGSQL: sqlcode = 0
DBGSQL:: b1 = 1
Determine whether the database is in the open state. Then, you want to access the database compatible parameter values.
Next call dbms_backup_restore determine rman version available information. The corresponding parameters are as follows:
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 not very familiar with?
Below the getPackageVersion function call dbms_rcvman
($ ORACLE_HOME / rdbms / admin / recover.bsq dbms_rcvman create, and can be related to the Notes) Access package versions available information.
08.00.04 to 09.02.00
Rman V will be for the next $ database, gain name, resetlogs_time, resetlogs_change #, dbid information.
Below this more important x $ kcccp (Kernel Cache Checkpoint Progress) to the inspection record:
SQL similar to the following:
Select nvl (max (cpmid), 0) from x $ kcccp where cpsta = 2
Upon completion of these operations, from v $ rman option of access to relevant information, including: 'Parallel backup and recovery', 'Incremental backup and
Recovery ',' Duplexed backups', 'Block Media Recovery,' 'Point-in-time tablespace recovery' through which to judge whether these databases
Function.
Log in and then display connections to the target database.
Analysis of the process is not complicated, but in relation to the depth of the order will have a lot of Log, we must have some patience to continue. In the failure of the rman,
Debug mode settings analysis is a very effective approach. If possible in the case, after the article I will give you a few examples to illustrate.
Reference
Dbmsbkrs.sql and prvtbkrs.plb document describes Notes (which can be in your system $ ORACLE_HOME / rdbms / admin / find.)
"Oracle 9i RMAN backup and recovery technology" Tsinghua Publisher 2.12 from the beginning to the end of the process of p41 rman
Steve Adams's Q + A http://www.ixora.com.au/q + a/0102/06135327.htm








0 Comments to “Rman simple analysis”
No Comments. Send your comment.
Leave a Reply
You must be logged in to post a comment.