This section will show you an example of creating a standby database. This Create Standby Database process (setup) is also referred to as CSD.
| Note | ||
|---|---|---|
| ||
Creating a standby database is performed on the primary server (primary node). If you are using Oracle RAC, you only need to run the Create Standby Database (CSD) process from one of the primary nodes (1st node recommended). But you must have a DDC file already created on both primary nodes. |
The example below will show you how to create a standby database running on standby server "dbvlin102" from the primary database called "proddb" running on the primary server "dbvlin101".
...
Windows only:
Start the "Dbvisit Standby command console" from the Start Menu ->Programs -> Dbvisit -> Standby.
This will start a Command Line with your session already in the DBVISIT_BASE/standby directory.
...
| Note |
|---|
It is possible to create a standby database using a normal filesystem while the primary database is making use of ASM. Please check: "Section - Primary on ASM and Standby using Filesystem" For critical production (primary) and standby environments it is always recommended to create the standby environment the same as the primary. |
...
In the above example, we agree with the parameters as specified, and specify option 1 after which the parameters are reviewed. If you do want to adjust the parameter use option 2 to edit specific parameters. Remember you can always adjust some of the parameters once the standby database creation is complete.specify option 1 after which the parameters are reviewed. If you do want to adjust the parameter use option 2 to edit specific parameters. Remember you can always adjust some of the parameters once the standby database creation is complete.
| Note |
|---|
When running a primary database using ASM and you are looking at creating a standby database using a normal Filesystem based storage, you need to make sure you review the following parameters:
When using ASM these values can be set to specific ASM disk groups on the primary server. But when you are creating the standby database, you need to update these parameters to reflect the standby filesystem structure. Example, this is the parameters on a primary database using ASM:
Now when creating the standby database, you will lets say use d:\oracle\oradata as your primary datafile location (the database files will be created in d:\oracle\oradata\DB_NAME example d:\oracle\oradata\prod where prod is the database name). And with regards to the Flash/Fast recovery area you might be using d:\oracle\fast_recovery_area. The following adjustments to the db_create_file_dest and db_recovery_file_dest should be made:
If you have the db_create_online_log_dest_n values set you have to adjust them as well.
|
Step 9:
It is possible to use TRANSPORTABLE MEDIA for very large databases or slow networks. When using this option, a backup of the primary database will be created on local storage (can be attached storage such as an external drive, but this must be mounted/made available by the system administrator). Once the backup is complete, it can be shipped (courier or other methods) to the standby site where it is then attached to the standby server. Once attached you can restart the Dbvisit Standby creation to complete the creation of the standby using this backup. This method is recommended for very large databases as well as when there is an extremely slow network between the primary and standby servers.
...
To create the standby database, temporary locations on both primary and standby server must be specified, to hold a database backup.
| Note |
|---|
Make sure this temporary backup location exist on both the primary and standby servers and can hold a full compressed (RMAN Compressed) backup of the primary database |
...
Apply your license key (or the demo licence licence key provided on software download), example:
| No Format |
|---|
oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit -lic proddb EB57I-DYK7K-9PI2V-1SH0D-AAWGR-2WEDY-ZJJ0F ============================================================= Dbvisit Standby Database Technology (7.0.04.11735) (pid 11331) dbvisit started on dbvlin101: Mon Jan 27 22:46:59 2014 () ============================================================= Dbvisit Standby license information for: proddb customer_seq=1 customer_key_seq=0 license_type=DEMO (0) expiry_date=2014-02-10 =>Update with license key: EB57I-DYK7K-9PI2V-1SH0D-AAWGR-2WEDY-ZJJ0F? <Yes/No> [Yes]: Yes License updated. Status: Valid ============================================================= dbvisit ended on dbvlin101: Mon Jan 27 22:47:03 2014 ============================================================= |
...
| Note |
|---|
The key needs to be applied only on Primary and above is just an example/demo key. |
Now that Once the license key is applied on the primary, run Dbvisit Standby as normal on Primary:
| No Format |
|---|
oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit proddb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11735) (pid 11392)
dbvisit started on dbvlin101: Mon Jan 27 22:47:56 2014 ()
=============================================================
>>> Obtaining information from standby database (RUN_INSPECT=Y)...
>>> Sending heartbeat message... - done.
>>> Checking Dbvisit Standby for configurational differences between dbvlin101 and
dbvlin102...
No configurational differences found between dbvlin101 and dbvlin102.
>>> Log file(s) for proddb will be transferred from dbvlin101 to dbvlin102...
> Transferring 'o1_mf_1_35_9gdb7647_.arc.gz' to server dbvlin102:7890
Progress: 0%...20%...40%...60%...80%...100% [7551 KB/s] - done.
1 archive log transfer to dbvlin102 for proddb completed.
Last sequence was 35.
No Mail sent as SEND_MAIL_FLAG = N
>>> Dbvisit Archive Management Module (AMM)
Config: number of archives to keep = 0
Config: number of days to keep archives = 7
Config: archive backup count = 0
Config: diskspace full threshold = 80%
Current disk percent full (/u01/app/oracle/fast_recovery_area) = 67%
Number of archive logs deleted = 0
=============================================================
dbvisit ended on dbvlin101: Mon Jan 27 22:48:32 2014
============================================================= |
Step 18:
The second to last step is to run Dbvisit Standby on the standby Standby server , example :
| No Format |
|---|
oracle@dbvlin102[/usr/dbvisit/standby]: ./dbvisit proddb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11735) (pid 31798)
dbvisit started on dbvlin102: Mon Jan 27 22:50:11 2014 ()
=============================================================
>>> Sending heartbeat message... - done.
>>> Log file(s) for proddb from dbvlin101 will be applied to dbvlin102
201401272250 - Log seq 35 thread 1 applied to standby database proddb.
No Mail sent as SEND_MAIL_FLAG_DR = N
>>> Dbvisit Archive Management Module (AMM)
Config: number of archives to keep = 0
Config: number of days to keep archives = 7
Config: diskspace full threshold = 80%
Processing /u01/app/oracle/archive/proddb...
Archive log dir: /u01/app/oracle/archive/proddb
Total number of archive files : 7
Number of archive logs deleted = 1
Current Disk percent full : 63%
=============================================================
dbvisit ended on dbvlin102: Mon Jan 27 22:50:18 2014
=============================================================
|
...