Oracle live cfg database copy - best practice?

[Adam G]

Hi,

I am considering using RMAN in Oracle to take a dump/copy of a "live" Production database.  I want to ensure that, whatever method is used, the operations of the cfg db are not affected.  Does anyone know the "Best Practice" way of taking a full copy of the cfg db without having to bring it off-line or affect it's "live" status/operations?

Thanks!

[pattadon]

with RMAN, I think you may need to stop the configuration DB and let's the production running in read-only mode.
otherwise you may need a third party tool like Golden Gate.

Another solution is you need to implement the Data guard and maintain the Oracle Archive log after you imported RMAN on secondary at first time.

[Dionysis]

RMAN will take a copy of the DB without any problems, it's how any backup of an Oracle database works.  You could also use Data Pump, or the config utility.

All depends what the purpose of the copy is.  If it's for backup / restore purposes, go with RMAN, if it's for Genesys support purposes, go with either the config utility or one of the Oracle export tools, "exp" or "Data Pump".  Whether you use exp or pump will depend on what version of Oracle you have, and how large the export is.  I find "exp" to be the simplest way.

Golden Gate is a real time replication tool so you can have 2 copies of the DB working in read/write mode, it's not really an export tool.

[Adam G]

Thanks everyone - lots of food for thought!