I'm not 100% sure what you are questioning then, but hopefully this helps. When you create a database via duplication it gets it own new DBID because it is a new unique database. When you create a standby database via duplication it retains the same DBID as the primary (target) because essentially it is a physical copy of that database and must stay that way. The RMAN catalog identifies a database by the DBID, so therefore you do not have to register the standby. This is because the standby can become the primary at any time and vice-versa. I hope that helps, Jed. From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of April Sims Sent: Thursday, September 02, 2010 9:53 AM To: oracle-l@xxxxxxxxxxxxx Subject: Creating Standby with RMAN documentation Can anyone else clarify this entry in the documentation? The part I am questioning is the "not register" statement. This is in the appendix F Creating a Standby Database with Recovery Manager "A standby database, unlike a duplicate database created by DUPLICATE without the FOR STANDBY OPTION, does not get a new DBID. Thus, you should not register the standby database with your recovery catalog." http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/rcmbackp. htm#SBYDB4988 thanks, -- April Sims SELECT IOUG Contributing Editor http://aprilcsims.wordpress.com http://www.twitter.com/aprilcsims Oracle Database 11g - Underground Advice for Database Administrators http://www.amazon.com/Oracle-Database-Underground-Advice-Administrators/ dp/1849680000/ref=sr_1_1?ie=UTF8&s=books&qid=1272289339&sr=8-1#noop https://www.packtpub.com/oracle-11g-database-implementations-guide/book OCP 8i, 9i, 10g DBA Southern Utah University aprilcsims@xxxxxxxxx