Create Standby Database using saved template
- KrupeshD (Deactivated)
Owned by KrupeshD (Deactivated)
You can create a standby database using a previously created and saved template. A template stores all standby database creation information that you have previously specified interactively.
To create a standby database using a template:
1. Start the Dbvisit Standby setup utility.
dbvisit_setup
2. 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
3. Choose the primary database to create a standby for. Only Dbvisit Standby configured databases will be shown :
=>Creating Standby Database.
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]:
4. The primary database must be up and running for the setup to proceed. Total size of the primary database is calculated and displayed. An option to create a standby database using a template will be listed if a saved template exists. Choose the template option:
Database dbvlx102 is up.
Total database size for dbvlx102 is 995Mb
=>Please ensure directory /usr/local/dbvlx102 exists on dbvisit32 and
has the correct privileges, otherwise the next transfer step may fail.
Checking Oracle installation on dbvisit32 in
/oracle/orabase/product/10.2.0/db_1/bin/oracle...
Total database size for dbvlx102 is 995MB
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]: 3
Starting creation of standby database.
5. You can view the contents of the existing template before using it to create a standby database:
What would you like to do:
1 - Create standby database using existing saved template
2 - View content of existing saved template
3 - Return to the previous menu
Please enter your choice [1]: 2
6. You can view the contents of the existing template before using it to create a standby database:
-------------------------------------------------------------------------------
CREATE STANDBY DATABASE TEMPLATE SUMMARY
-------------------------------------------------------------------------------
A - GENERAL SETTINGS
-------------------------------------------------------------------------------
TEMPLATE ID 1
DDC FILE dbvlx102
SOURCE HOST dbvisit31
DESTINATION HOST dbvisit32
STANDBY ASM Y
COPY DATAFILES DIRECTLY N
COMPRESS DATAFILES Y
USE TRANSPORTABLE MEDIA N
PRIMARY TEMP LOCATION /usr/tmp/tmp1
STANDBY TEMP LOCATION /usr/tmp/tmp2
STOP POINT SET N
CREATE DIRECTORIES AUTO Y
CREATED ON 28-11-2011 10-04-27
-------------------------------------------------------------------------------
B - INIT ORA PARAMETERS
-------------------------------------------------------------------------------
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 +ARCHIVELOGS
db_create_online_log_dest_2 +ARCHIVELOGS
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=+DATA
log_archive_dest_2 LOCATION=/oracle/oraarch/dbvlx102
log_archive_format %t_%s_%r.dbf
log_archive_start TRUE
log_file_name_convert +ARCHIVELOGS/dbvlx102/onlinelog,
+ARCHIVELOGS/DBVLX102/onlinelog,
+ONLINELOGS/dbvlx102/onlinelog,
+ARCHIVELOGS/DBVLX102/onlinelog
open_cursors 300
pga_aggregate_target 16777216
processes 150
remote_login_passwordfile EXCLUSIVE
sga_target 167772160
spfile default
standby_file_management MANUAL
undo_management AUTO
undo_tablespace UNDOTBS1
user_dump_dest /oracle/orabase/admin/dbvlx102/udump
-------------------------------------------------------------------------------
C - DATABASE FILE LOCATIONS
-------------------------------------------------------------------------------
TYPE ID STANDBY FILE NAME
DATA 1 +DATA
DATA 2 +DATA
DATA 3 +DATA
DATA 4 +DATA
DATA 5 +DATA
TEMP 1 +DATA
TEMP 2 +DATA
TEMP 3 +DATA
-------------------------------------------------------------------------------
What would you like to do:
1 - Create standby database using existing saved template
2 - View content of existing saved template
3 - Return to the previous menu
Please enter your choice [1]:
Validating template... Please wait...
STATUS=VALID
-------------------------------------------------------------------------------
What would you like to do:
1 - Create standby database using existing saved template
2 - View content of existing saved template
3 - Return to the previous menu
Please enter your choice [1]:
Validating template... Please wait...
STATUS=VALID
7. Dbvisit Standby will validate the template and proceed with creating a standby database without further interaction:
Starting creation of standby database.
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...