Cloning database is one of the routine DBA activities. Any DBA who administers v arious environments has to periodically synchronize the acceptance / testing / developmen t with the Production data. This frequency of synchronization depends upon the business and application deve lopment teams requirements. Each of the above mentioned process has got its own pros and cons.
Cloning database is one of the routine DBA activities. Any DBA who administers v arious environments has to periodically synchronize the acceptance / testing / developmen t with the Production data. This frequency of synchronization depends upon the business and application deve lopment teams requirements. Each of the above mentioned process has got its own pros and cons.
Cloning database is one of the routine DBA activities. Any DBA who administers v arious environments has to periodically synchronize the acceptance / testing / developmen t with the Production data. This frequency of synchronization depends upon the business and application deve lopment teams requirements. Each of the above mentioned process has got its own pros and cons.
3.1 Introduction Cloning database is one of the routine DBA activities. Any DBA who administers v arious environments and is supporting the application development team for datab ase activities has to periodically synchronize the acceptance/testing/developmen t with the Production data. This frequency of synchronization depends upon the business and application deve lopment teams requirements. Generally this process can be done with the below me ntioned procedures 1) EXPORT/IMPORT utilities 2) DATA PUMP 3) Cold Backup Restoration 4) Hot Backup Recovery Each of the above mentioned process has got its own pros and cons. To state a fe w vital reasons why Hot backup recovery process is chosen widely a) You can recover to the most recent time period. b) Doesnt require outage of the source database c) Requires less time compared to the other process d) Best method for large databases 3.2 Environments 1. Primary or the Source database system 2. Secondary or the Target database system 3.3 Assumption Primary database operated in ARCHIVELOG mode. Secondary database to be created by cloning in a different server Primary and Secondary environment Operating system are same. 3.4 Cloning Process 3.4.1 Steps to be followed in Primary database: 1) Perform HOTBACKUP of all the data files 2) LSN number Login as sys as sysdba Sql> Alter system archive log current; Sql> Archive log list Note down the Current Log Sequence 3) Control file trace In Sql> prompt issue the statement ALTER DATABASE BACKUP CONTROLFILE TO TRACE; You can find the trace file in the udump directory. 3. Overview of the Procedure 3.1 Introduction Cloning database is one of the routine DBA activities. Any DBA who administers v arious environments and is supporting the application development team for datab ase activities has to periodically synchronize the acceptance/testing/developmen t with the Production data. This frequency of synchronization depends upon the business and application deve lopment teams requirements. Generally this process can be done with the below me ntioned procedures 1) EXPORT/IMPORT utilities 2) DATA PUMP 3) Cold Backup Restoration 4) Hot Backup Recovery Each of the above mentioned process has got its own pros and cons. To state a fe w vital reasons why Hot backup recovery process is chosen widely a) You can recover to the most recent time period. b) Doesnt require outage of the source database c) Requires less time compared to the other process d) Best method for large databases 3.2 Environments 1. Primary or the Source database system 2. Secondary or the Target database system 3.3 Assumption Primary database operated in ARCHIVELOG mode. Secondary database to be created by cloning in a different server Primary and Secondary environment Operating system are same. 3.4 Cloning Process 3.4.1 Steps to be followed in Primary database: 1) Perform HOTBACKUP of all the data files 2) LSN number Login as sys as sysdba Sql> Alter system archive log current; Sql> Archive log list Note down the Current Log Sequence 3) Control file trace In Sql> prompt issue the statement ALTER DATABASE BACKUP CONTROLFILE TO TRACE; You can find the trace file in the udump directory.