Create Standby Database

  1<backup control="" file=""> ;   
  2  
  3Ensure all online archives are archived   
  4SVRMGR &gt; ALTER SYSTEM ARCHIVE LOG CURRENT ;   
  5  
  6d) Backup the current init<sid>.ora of the database.   
  7  
  82.Create Oracle Service for Standby database   
  9  
 10To create a new database as standby database with same <sid> as the primary database. We could create a small one with SYSTEM tablespace initially, using Oracle Database Assistant. It helps creation of the Oracle NT services.   
 11  
 12Use the same Oracle version on creating the database   
 13  
 14Ensure Oracle listener could serve the new Oracle service.   
 15  
 16On NT service, change the oracleStart<sid>?service to manually mode, to avoid it automatically start-up on the NT reboot.   
 17  
 18Shutdown the oracleStart<sid>?service once the above steps done, and ensure the 揙racleService<sid>?service is still running on.   
 19  
 203.Create DB directories   
 21  
 22Pls create the directories for holding the database datafiles, as same as the setting as on primary database.   
 23You should follow the same drives mapping   
 24Pls create the directories for logs, redo logs, pfile, bdump, udump etc, similar to the primary database also.   
 25  
 264.Transfer files to Standby Server   
 27  
 28Transfer all of the hot-backup datafiles to the standby system.   
 29  
 30The file list is   
 31backup standby controlfile   
 32Hot-backup datafiles   
 33All offline archives available on archived directory   
 34backup init<sid>.ora file   
 35  
 36The destination of the transferred files should be specified as:   
 37  
 38Backup standby control file:   
 39Copied to all members of the control files, the exact directory path as specified in backup   
 40init<sid>.ora file.   
 41  
 42Hot-backup datafiles:   
 43Copied to original datafiles location, exactly the same directory path as on primary system.   
 44  
 45All offline archives:   
 46Copied to the DB archive directory, exactly the same directory path as on primary system.   
 47  
 48Backup init<sid>.ora file:   
 49Copied to $ORACLE_HOME/dbs or the IFILE parameter refer to location.   
 50  
 515.Sync Standby Database   
 52  
 535.1 Turn Standby DB on recovery mode   
 54  
 55a. Ensure oracleService<sid>?service started.   
 56b. Mount the DB   
 57  
 58SVRMGR &gt; CONNECT INTERNAL/ <passwd>   
 59SVRMGR &gt; STARTUP NOMOUNT PFILE=<path>/init<sid>.ora   
 60SVRMGR &gt; ALTER DATABASE MOUNT STANDBY DATABASE;   
 61SVRMGR &gt; EXIT;   
 62  
 63We could place the above commands into a STARTUP.SQL? and it will be called   
 64by a batch command startup_standby.bat?. See Appendix for details.   
 65  
 66  
 67You could place a shortcut on the desktop on NT standby server, to depict the job.   
 68  
 695.2 Apply archived logs   
 70  
 71a. Ensure the standby DB in recovery mode.   
 72b. Apply the logs   
 73  
 74SVRMGR &gt; CONNECT INTERNAL/ <passwd>   
 75SVRMGR &gt; SET AUTORECOVERY ON;   
 76SVRMGR &gt; RECOVER STANDBY DATABASE;   
 77SVRMGR &gt; EXIT;   
 78  
 79We could place the above commands into a RECOVER.SQL?script, and it will be called   
 80by a batch recover.bat?. See Appendix for details.   
 81  
 825.3 Continuous Apply archived logs in recovery mode   
 83  
 84Ensure a regular job to copy the primary offline archives to the standby server.   
 85  
 86Pls see aync_log.bat?file for a reference. See Appendix for details.   
 87  
 88You could use WINCRON to schedule a job to copy drive archives from primary site to local   
 89archive directory with 1 hr interval.   
 90  
 91  
 92Perform the apply archived logs in recovery mode?job once new archives arrival   
 93  
 94Pls see sync_log.bat?file for a reference. See Appendix for details.   
 95  
 96You could use WINCRON to schedule the job to apply archives with 1 hr interval.   
 97  
 98  
 99Perform clean job on obsolete offline archives on standby system   
100  
101Pls see archive.cmd ?file for a reference. See Appendix for details.   
102  
103You could use WINCRON to schedule the job to clean obsolete archives with 2 days retention.   
104  
1055.4 Activate Standby Database   
106  
107To activate the standby database, copy the latest offline archive logs from primary server over to the standby system.   
108  
109Apply the archives to the standby database as mentioned on Section 3.2.   
110  
111Activate the standby database   
112SVRMGR &gt; ALTER DATABASE ACTIVATE STANDBY DATABASE ;   
113  
114Shutdown the standby DB to reset file headers and clear all buffers.   
115SVRMGR &gt; SHUTDOWN NORMAL;   
116  
117Open the database. You could start it by NT 揙racleStart<sid>?service and then enable the service to start automatically now.   
118  
119You do not need copy any online redo logs from the primary server to the standby system once it is activated.   
120  
121Take a DB hot-backup after the database opens.   
122  
1235.5 Special Notes   
124  
125Any physical changes that occur on the primary must be accomplished on the standby as well.   
126  
127New datafiles added on primary database, file entries are added to the standby controlfile only.   
128  
129If the standby database can't find the physical datafile, standby recovery will stop with an   
130ORA-1157 error.   
131  
132Use ALTER DATABASE CREATE DATAFILE <path> as <path>; ?to recreate the physical   
133datafile or physically copy the missing datafiles to the standby system.   
134  
135You can add or drop log files on the primary without affecting the standby DB.   
136  
137If you do recreation controlfile?on the primary server, you must also recreate the controlfile for the standby database. Shut down the standby database, and use a current backup standby control file from primary server.   
138  
139  
140Jimi   
141GIT</path></path></sid></passwd></sid></path></passwd></sid></sid></sid></sid></sid></sid></sid></sid></sid></backup>