Usually developing a J2EE application (sure, it may be not necessary J2EE, but it is so in my case, so I will consider that) you have several environments - at least they are: Development Environment, Test Environment and Production Environment. Production usually contains the most actual 'runtime' information. As for development and test environments it is usually appreciated they would have actual data too. So it's obvious that you need to clone the production database.
You can do that using:
-'cold' cloning: database must be properly shutted down. Then you just copy all datafiles (+ probably redo logs) using OS means. (full step-by-step tutorial on 'cold' cloning you can find at http://www.dba-oracle.com/oracle_tips_db_copy.htm)
-'hot' cloning: This method is used when you cannot afford to shutdown the database. You do not have to shutdown the database, but you must switch database to 'backup mode'. I found a nice step-by-step tutorial how to do it: http://www.shutdownabort.com/quickguides/clone_hot.php
The common incorrect method: to do a database clone without shutdown or switching the database to 'backup mode'. I swallowed this bait too for the first time I cloned the database and hope this caution will help somebody :)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment