Using Database Control to Clone a Database in Font

Printing QR Code 2d barcode in Font Using Database Control to Clone a Database

The Enterprise Manager Clone Database Wizard steps you through the database cloning operation. Here are the main features of the cloning feature: You can clone any Oracle database that is release 8.1.7 or higher. The source database can be in the archivelog or the noarchivelog mode.

You can clone a database while it is open. Database Control uses RMAN internally for the cloning operation. Database Control will back up the data files and restore them in the new location. It will then recover them using archived redo logs. Database Control will create the new instance, a password file, any necessary networking files, and the init.ora file and SPFILE. Database Control will automatically start the new instance in the open mode. Here are the steps for cloning a database using Database Control: 1. Click the Maintenance Tab on the Database Home Page of Database Control. 2. Click on the Clone Database item in the Data Movement section (under the Move Database files group). 3. In the Source Type page, choose the Clone a Running Database Instance option. 4. In the Source Working Directory page, enter your operating system username and password. Click Next. 5. In the Select Destination page, enter the new database name and the destination host name. Click Next. 6. In the Destination Options page, you can customize database file locations if you wish. Click Next. 7. In the Schedule page, you can choose whether you want to clone the database immediately or to schedule it for later. Click Next. 8. In the Review page you can review the source and clone database information, as shown in Figure 16-1. Click the Submit Job button to start the cloning operation.

Figure 16-1. The Clone Database Review page You can check the database cloning status by going to the Logs page, shown in Figure 16-2.

To clone a database manually, you need to first use the operating system to copy all of the source database files to the target location. If you are on the same server, you also have to change the name of the database; if you are on a different server, you can keep the same name for the databases if you wish. You first back up the source database control file to trace (using the ALTER DATABASE BACKUP CONTROLFILE TO TRACE statement) and, using the trace file s contents, create a new control file that will help you create the new clone database. Here s a summary of the steps involved in manually cloning a database. The procedure is simple, with most of the time being consumed by copying the database files from source to target. Assume that your production database is the source database and is named prod and your destination (target) database is named test . 1. Copy the prod database files to the target location. 2. Prepare a text file for the creation of a control file for the new database as follows: SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE; 3. On the target location, create all the directories for the various files. 4. Copy the following four sets of files from the production (source) database to the target database: parameter files, control files, data files, and redo log files. 5. In all the clone database files, change the database name to test. 6. Run the CREATE DATABASE statement, which was prepared with the ALTER DATABASE BACKUP CONTROLFILE TO TRACE statement. 7. Create the control file for the test database using the following statement: SQL> CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS NOARCHIVELOG You ll now have a new database called test that has a new control file pointing to the copied (target) version of the production database.