This example shows how to create an ASM standby database with different structure as primary ASM database. Creating a standby database is performed on the primary server (primary node).
Windows only:
Start the Dbvisit Standby command console from the Start Menu ->Programs -> Dbvisit -> Standby. 
Linux/Unix only:
Go to the Dbvisit Standby install directory. Start the Dbvisit Standby setup utility.
dbvisit_setup
Linux/UNIX and Windows:
1. To create a standby database, choose option 7.
========================================================
Dbvisit Standby Database Technology
http://www.dbvisit.com
Dbvisit Database setup
Default values will be shown in []
Options:
1) New Dbvisit Database setup (combines options 2,3,4)
1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
2) New Dbvisit Database configuration (DDC) file setup
3) New Dbvisit Archive Management Module (AMM) setup
4) New Dbvisit Database repository (DDR) setup
5) Manage Dbvisit Database repository (DDR)
6) Update Dbvisit Database configuration (DDC) file
7) Create Standby Database (and template)
9) Uninstall Dbvisit Database repository (DDR)
E) Exit
=========================================================
Please enter choice : 7
2. Choose the primary database to create a standby for. Only Dbvisit Standby configured databases will be shown :
=>Creating Standby Database.
Primary database will NOT be shutdown.
For which primary database do you want to create a standby database?
The following Oracle database(s) have a Dbvisit Database configuration (DDC) file on this server:
SID
===
1) dbvisitp
2) dbvlx102
3) Return to menu
Please enter choice : 2
Is this correct? <Yes/No> [Yes]:
3. The primary database must be up and running for the setup to proceed. Total size of the primary database is calculated and displayed. The Dbvisit Standby installation files are also copied to the standby server initially. If uncompleted creation of the standby database is detected, a restart option will be available. Standby database can also be created using a saved template:
Database dbvlx102 is up.
Total database size for dbvlx102 is 30GB
=>Please ensure directory /usr/local/dbvlx102 exists on dbvisit32
and has the correct privileges, otherwise the next transfer step may fail.
Transferring dbv_functions to host dbvisit32:dbv_functions
Transferring dbvisit to host dbvisit32:dbvisit
Transferring dbvisit_setup to host dbvisit32:dbvisit_setup
Transferring dbv_oraStartStop to host dbvisit32:dbv_oraStartStop
Transferring dbv_dbvlx102.env to host dbvisit32:dbv_dbvlx102.env
Transferring dbv_ORACLE_SID.env to host dbvisit32:dbv_ORACLE_SID.env
Transferring README.txt to host dbvisit32:README.txt
Checking Oracle installation on dbvisit32 in
/oracle/orabase/product/10.2.0/db_1/bin/oracle...
Total database size for dbvlx102 is 30GB
What would you like to do:
1 - Create standby database (and optionally save settings in template)
2 - Restart the uncompleted creation of standby database
3 - Create standby database using existing template (previously saved)
4 - Help
5 - Terminate processing
Please enter your choice [2]: 1
Starting creation of standby database.
4. An ASM (for Oracle database versions 10.2 or higher) or normal file system standby database can be created:
------------------------------------------------------------------------------
Do you want to create an ASM standby database (with all or some database files
in ASM storage)? [Yes]: y
Standby database will be ASM: Y
Is this correct? <Yes/No> [Yes]:
5. It is possible to transfer datafiles directly to the standby server, but only if both primary and standby databases are filesystem, and the primary database does not contain Oracle Managed Files (OMF):
You can create a standby database by transferring the database files directly to the standby server,
or by copying them to a temporary local location first. By using a temporary location the time taken
to place the database in backup mode is reduced. If the database is very large then use a temporary
location (answer No).
If either a primary or a standby database is ASM, you have to use a temporary location (answer No).
Do you want to copy database files directly to the standby server? [Yes]:
Database files will be copied directly to the standby server: N
Is this correct? <Yes/No> [Yes]:
6. It is possible to compress datafiles before transferring:
------------------------------------------------------------------------------
Use compression to compress the database files before transferring? [Yes]:
Database files will be compressed before transferring: Yes
Is this correct? <Yes/No> [Yes]:
7. It is possible to create missing filesystem directories on the standby server automatically:
------------------------------------------------------------------------------
Dbvisit has functionality to create missing filesystem directories on the standby server automatically.
Do you want Dbvisit to create missing filesystem directories on the standby automatically? [Yes]:
Dbvisit will create missing filesystem directories automatically: Y
Is this correct? <Yes/No> [Yes]:
8. Oracle database parameters for the standby database can be customised:
------------------------------------------------------------------------------
The following oracle database parameters will be set in the standby database pfile or spfile:
-------------------------------------------------------------------------------
audit_file_dest /oracle/orabase/admin/dbvlx102/adump
background_dump_dest /oracle/orabase/admin/dbvlx102/bdump
compatible 10.2.0.1.0
control_files +ARCHIVELOGS/dbvlx102/control01.ctl,
+DATA/dbvlx102/control02.ctl,
+ONLINELOGS/dbvlx102/control03.ctl
core_dump_dest /oracle/orabase/admin/dbvlx102/cdump
db_block_size 8192
db_create_file_dest +DATA
db_create_online_log_dest_1 +DATA
db_create_online_log_dest_2 +ONLINELOGS
db_file_multiblock_read_count 16
db_name dbvlx102
db_recovery_file_dest +DATA
db_recovery_file_dest_size 2147483648
dispatchers (PROTOCOL=TCP) (SERVICE=dbvlx102XDB)
job_queue_processes 10
log_archive_dest_1 location=/oracle/oradata/dbvlx102
log_archive_format %t_%s_%r.dbf
log_archive_start TRUE
open_cursors 300
pga_aggregate_target 16777216
processes 150
remote_login_passwordfile EXCLUSIVE
sga_target 167772160
spfile +ARCHIVELOGS/dbvlx102/spfiledbvlx102.ora
undo_management AUTO
undo_tablespace UNDOTBS1
user_dump_dest /oracle/orabase/admin/dbvlx102/udump
-------------------------------------------------------------------------------
What would you like to do:
1 - Proceed with creating the standby database
2 - Edit oracle database parameters for the standby database pfile/spfile
3 - Terminate processing
Please enter your choice [1]:
Validating oracle database parameters... please wait
SUCCEEDED
9. It is possible to use TRANSPORTABLE MEDIA for very large databases or slow networks:
------------------------------------------------------------------------------
Do you want to use TRANSPORTABLE MEDIA to transfer the database files to the
standby server? Transportable media is an external device such as a USB drive
that is first plugged into the primary server and then manually transferred to
the standby site and plugged into the standby server to continue the process.
It can be used for large databases or slow networks.
Specifying No means the network will be used to transfer the database files.
[No]:
Transportable media will be used: N
Is this correct? <Yes/No> [Yes]:
10. To create an ASM standby database temporary locations on both primary and standby server must be specified, to hold a database backup:
------------------------------------------------------------------------------
A temporary location must be specified on dbvisit31 where the database will be
backed up to first. This location must be big enough to hold RMAN backup of the whole database (1.05GB).
Specify the location on this server: [/usr/tmp]: /usr/tmp/tmp1
Directory for temporary location will be: /usr/tmp/tmp1
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
A temporary location must be specified on dbvisit32 where the database will be
copied to before moving to specified locations.
This location must be big enough to hold the whole database (995MB).
Specify the location on the remote server: []: /usr/tmp/tmp2
Directory for temporary will be: /usr/tmp/tmp2
Is this correct? <Yes/No> [Yes]:
11. The process of creating a standby database can be broken into two steps:
------------------------------------------------------------------------------
The creation of the standby database consists of 2 parts:
1) Backup database to temporary location.
2) Transfer backup from temporary location to standby server.
The process can be stopped after step 1 and then continued with step 2 at a
later date.
Do you want to the process to stop between these 2 steps? [No]:
Process will stop between steps: N
Is this correct? <Yes/No> [Yes]:
12. It is possible to specify the locations of standby datafiles, redo logs and tempfiles different as primary:
Dbvisit will automatically create standby OMF ASM datafiles and tempfiles.
The files will be created under
<ASM Disk Group>/<db_unique_name>/datafile|tempfile.
Review and confirm ASM disk groups for standby datafiles and tempfiles.
-------------------------------------------------------------------------------
Primary ===> Standby
-------------------------------------------------------------------------------
+DATA/dbvlx102 ===> +DATA
+DATA/dbvlx102/datafile ===> +DATA
+DATA/dbvlx102/tempfile ===> +DATA
-------------------------------------------------------------------------------
What would you like to do:
1 - Confirm standby location(s) are correct and continue
2 - Provide different standby location(s)
Please enter your choice [1]:
Standby locations validated.
Primary database contains non OMF redo logs. Non OMF ASM redo logs will be created under:
<ASM Disk Group>/<db_unique_name>/onlinelog.
Make sure these locations exist on the standby or create them manually.
Review and confirm ASM disk group names for non OMF standby redo logs.
-------------------------------------------------------------------------------
Primary ===> Standby
-------------------------------------------------------------------------------
+ARCHIVELOGS/dbvlx102/onlinelog ===> +ARCHIVELOGS
+ONLINELOGS/dbvlx102/onlinelog ===> +ARCHIVELOGS
-------------------------------------------------------------------------------
What would you like to do:
1 - Confirm standby location(s) are correct and continue
2 - Provide different standby location(s)
Please enter your choice [1]:
Standby locations validated.
13. Provided answers can be stored as a template for future use (re-running creating of a standby database):
------------------------------------------------------------------------------
=>Create standby database template for dbvlx102 using provided answers?
<Yes/No> [Yes]: y
An existing template found.
=>Do you want to view the existing template? <Yes/No> [Yes]: n
What would you like to do:
1 - Keep existing template and continue with creating a standby database
using provided answers
2 - Save provided answers as a new template (Note: existing template
will be replaced by the new one)
Please enter your choice [1]: 2
What would you like to do:
1 - Continue with creating a standby database
2 - Terminate creating a standby database. The saved template will be
available for future use
Please enter your choice [1]:
14. The standby database will now be created. Once completed the next stepsto take will be shown:
Creating standby database...
Backing up datafile 1...
Backing up datafile 2...
Backing up datafile 3...
Backing up datafile 4...
Backing up datafile 5...
Creating standby controlfile controlfile...
Creating standby parameter file...
Backup of primary database completed.
Compressing /usr/tmp/tmp1/dbv_dbvlx102_dbf_1_70_1.piece...
Compressing /usr/tmp/tmp1/dbv_dbvlx102_dbf_1_71_1.piece...
Compressing /usr/tmp/tmp1/dbv_dbvlx102_dbf_2_72_1.piece...
Compressing /usr/tmp/tmp1/dbv_dbvlx102_dbf_3_73_1.piece...
Compressing /usr/tmp/tmp1/dbv_dbvlx102_dbf_4_74_1.piece...
Compressing /usr/tmp/tmp1/dbv_dbvlx102_dbf_5_75_1.piece...
Transferring /usr/tmp/tmp1/dbv_dbvlx102_dbf_1_70_1.piece.gz to
host dbvisit32:/usr/tmp/tmp2/dbv_dbvlx102_dbf_1_70_1.piece.gz ...
Transferring /usr/tmp/tmp1/dbv_dbvlx102_dbf_1_71_1.piece.gz to
host dbvisit32:/usr/tmp/tmp2/dbv_dbvlx102_dbf_1_71_1.piece.gz ...
Transferring /usr/tmp/tmp1/dbv_dbvlx102_dbf_2_72_1.piece.gz to
host dbvisit32:/usr/tmp/tmp2/dbv_dbvlx102_dbf_2_72_1.piece.gz ...
Transferring /usr/tmp/tmp1/dbv_dbvlx102_dbf_3_73_1.piece.gz to
host dbvisit32:/usr/tmp/tmp2/dbv_dbvlx102_dbf_3_73_1.piece.gz ...
Transferring /usr/tmp/tmp1/dbv_dbvlx102_dbf_4_74_1.piece.gz to
host dbvisit32:/usr/tmp/tmp2/dbv_dbvlx102_dbf_4_74_1.piece.gz ...
Transferring /usr/tmp/tmp1/dbv_dbvlx102_dbf_5_75_1.piece.gz to
host dbvisit32:/usr/tmp/tmp2/dbv_dbvlx102_dbf_5_75_1.piece.gz ...
Uncompressing /usr/tmp/tmp2/dbv_dbvlx102_dbf_1_70_1.piece.gz...
Uncompressing /usr/tmp/tmp2/dbv_dbvlx102_dbf_1_71_1.piece.gz...
Uncompressing /usr/tmp/tmp2/dbv_dbvlx102_dbf_2_72_1.piece.gz...
Uncompressing /usr/tmp/tmp2/dbv_dbvlx102_dbf_3_73_1.piece.gz...
Uncompressing /usr/tmp/tmp2/dbv_dbvlx102_dbf_4_74_1.piece.gz...
Uncompressing /usr/tmp/tmp2/dbv_dbvlx102_dbf_5_75_1.piece.gz...
Shutting down standby database on dbvisit32...
Standby database dbvlx102 on dbvisit32 shutdown.
Remote spfile /oracle/orabase/product/10.2.0/db_1/dbs/spfiledbvlx102.ora backed as
/oracle/orabase/product/10.2.0/db_1/dbs/spfiledbvlx102.ora.201111281014.
Remote spfile /oracle/orabase/product/10.2.0/db_1/dbs/spfiledbvlx102.ora deleted.
Spfile created on the remote server.
Restoring standby control files...
Starting Standby Database dbvlx102...
Standby Database dbvlx102 started nomount.
Standby database dbvlx102 on dbvisit32 startup nomount.
Shutting down standby database on dbvisit32...
Standby database dbvlx102 on dbvisit32 shutdown.
Standby control files restored. Starting Standby Database dbvlx102...
Standby Database dbvlx102 started .
Standby database dbvlx102 on dbvisit32 mounted.
Catalog backup piece /usr/tmp/tmp2/dbv_dbvlx102_dbf_1_70_1.piece...
Catalog backup piece /usr/tmp/tmp2/dbv_dbvlx102_dbf_1_71_1.piece...
Catalog backup piece /usr/tmp/tmp2/dbv_dbvlx102_dbf_2_72_1.piece...
Catalog backup piece /usr/tmp/tmp2/dbv_dbvlx102_dbf_3_73_1.piece...
Catalog backup piece /usr/tmp/tmp2/dbv_dbvlx102_dbf_4_74_1.piece...
Catalog backup piece /usr/tmp/tmp2/dbv_dbvlx102_dbf_5_75_1.piece...
Restoring datafile 1...
Restoring datafile 2...
Restoring datafile 3...
Restoring datafile 4...
Restoring datafile 5...
Tempfiles renamed.
Performing Oracle Checkpoint.
Waiting 3 seconds for log switch completion...
Standby database created.
To complete creating standby database, run dbvisit on the primary and
standby databases to ensure standby database is in synch with primary.
Please press <Enter> to continue...
=========================================================
Standby Database creation on dbvisit32 completed.
Next steps:
1) Exit out of dbvisit_setup.
2) Run Dbvisit on this server with command:
dbvisit database_name
3) Run Dbvisit on standby server with command:
(cd /usr/local/avisit_svn/trunk/dbvisit/standby)
dbvisit database_name
Once Dbvisit has been tested, schedule Dbvisit on primary and standby servers using cron or other scheduling tool.
=========================================================
Please press <Enter> to continue...
15. The standby database has been created. The Dbvisit Standby setup menu will be redisplayed:
=========================================================
Dbvisit Standby Database Technology
http://www.dbvisit.com
Dbvisit Database setup
Default values will be shown in []
Options:
1) New Dbvisit Database setup (combines options 2,3,4)
1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
2) New Dbvisit Database configuration (DDC) file setup
3) New Dbvisit Archive Management Module (AMM) setup
4) New Dbvisit Database repository (DDR) setup
5) Manage Dbvisit Database repository (DDR)
6) Update Dbvisit Database configuration (DDC) file
7) Create Standby Database (and template)
9) Uninstall Dbvisit Database repository (DDR)
E) Exit
16. Exit out of the main menu and run Dbvisit Standby as normal.