Thursday, December 29, 2011

Just tested to create Standby Database - Dbvisit Standby 6.0.16

I have 2 hosts (virtualbox) with Oracle Restart + SE database. I tested to create Standby Database by using "dbvisit_setup" command-line (Dbvisit Standby 6.0.14) and had some issue about ASM. I had to use rman (duplicate target database for standby from active database dorecover) to help. Dbvisit Standby 6.0.16 pre-release!
New features:
1) New Create Standby Database (CSD) functionality which improves the overall ability to create different standby databases configurations.

CSD now makes use of the following parameters:
- db_file_name_convert
- log_file_name_convert

Fixes:
1) Issue with adding own ORACLE_SID and ORACLE_HOME in web interface - fixed.
2) Dbvisit temp p2x-* directories not cleaned up for HP-UX and AIX - fixed.
3) Improve locking mechanism in rare cases when archive log file just arrives at the standby server and is 0 size and is picked up by Dbvisit Standby on the standby server.

So, I tested to create Standby Database by "dbvisit_setup" command-line and it was all work for me. Thank You #dbvisit for new version :)

Example:
[oracle@mylinux standby]$ ./dbvisit_setup
=========================================================

Dbvisit Standby Database Technology (6.0.16.7977)
http://www.dbvisit.com

=========================================================

=>dbvisit_setup only needs to be run on the primary server.

Is this the primary server? <Yes/No> [Yes]:
=========================================================
Dbvisit Standby Database Technology (6.0.16.7977)
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

------------------------------------------------------------------------------
=>Creating Standby Database.
Primary database will NOT be shutdown.

Choose database:

The following Oracle database(s) have a Dbvisit Database configuration (DDC)
file on this server:

DDC
===
1) orcl
2) Return to menu

Please enter choice : 1

Is this correct? <Yes/No> [Yes]:
Database orcl is up.

Checking Dbvisit Standby configurational differences between mylinux and linuxstb...
Dbvisit Standby configurational differences found between mylinux and linuxstb...
Transferring dbv_orcl.env to host linuxstb:dbv_orcl.env
Checking Oracle installation on linuxstb in
/u01/app/oracle/product/11.2.0/dbhome_1/bin/oracle...
Total database size for orcl is 1.94GB
What would you like to do:
1 - Create standby database (and optionally save settings in template)
2 - Create standby database using existing template (previously saved)
3 - Help
4 - Terminate processing
Please enter your choice [1]:

-------------------------------------------------------------------------------
Do you want to create an ASM standby database (with all or some database files
in ASM storage)? [Yes]:
Standby database will be ASM: Y
Is this correct? <Yes/No> [Yes]:

-------------------------------------------------------------------------------
Use compression to compress the database files before transfer? [Yes]: No
Database files will be compressed before transfer: N
Is this correct? <Yes/No> [Yes]:

-------------------------------------------------------------------------------
Dbvisit Standby provides functionality to create missing filesystem directories
on the standby server automatically.
Do you want Dbvisit Standby to create missing filesystem directories on the
standby server automatically? [Yes]:
Dbvisit Standby will create missing filesystem directories automatically: Y
Is this correct? <Yes/No> [Yes]:

-------------------------------------------------------------------------------
Primary database contains Oracle Managed Files (OMF). These files will be
created as OMF files on the standby server. Please make sure creating of OMF
files is enabled on the standby by setting up parameters db_create_file_dest,
db_create_online_log_dest_n and db_recovery_file_dest to point to valid ASM
locations. Refer to Oracle documentation for information how to enable creating
of OMF files.

The following oracle database parameters will be set in the standby database pfile or spfile:
-------------------------------------------------------------------------------
audit_file_dest /u01/app/oracle/admin/orcl/adump
compatible 11.2.0.0.0
db_block_size 8192
db_create_file_dest +DG_DATA
db_name orcl
db_recovery_file_dest +DG_DATA
db_recovery_file_dest_size 4794089472
diagnostic_dest /u01/app/oracle
dispatchers (PROTOCOL=TCP) (SERVICE=orclXDB)
memory_max_target 683671552
memory_target 683671552
open_cursors 300
processes 150
remote_login_passwordfile EXCLUSIVE
spfile +DG_DATA/orcl/spfileorcl.ora
standby_file_management MANUAL
undo_tablespace UNDOTBS1

-------------------------------------------------------------------------------
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

-------------------------------------------------------------------------------
Do you want to use TRANSPORTABLE MEDIA to transfer the database backup 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 backup.
[No]:
Transportable media will be used: N
Is this correct? <Yes/No> [Yes]:

-------------------------------------------------------------------------------
A temporary location must be specified on mylinux where the database will be
backed up to first.
This location must be big enough to hold RMAN backup of the whole database
(1.94GB).

Specify the location on this server: [/usr/tmp]:
Directory for temporary location will be: /usr/tmp
Is this correct? <Yes/No> [Yes]:

-------------------------------------------------------------------------------
A temporary location must be specified on linuxstb where the database backup
will be copied to before moving to specified locations.

Specify location on remote server: [/usr/tmp]:
Directory for temporary will be: /usr/tmp
Is this correct? <Yes/No> [Yes]:

-------------------------------------------------------------------------------
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]:

Dbvisit Standby 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
-------------------------------------------------------------------------------
+DG_DATA/orcl/datafile ===> +DG_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 server or create them manually.
Review and confirm ASM disk group names for non-OMF standby redo logs.

-------------------------------------------------------------------------------
Primary ===> Standby
-------------------------------------------------------------------------------
+DG_DATA/orcl/onlinelog ===> +DG_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.

-------------------------------------------------------------------------------
=>Create standby database template for orcl using provided answers? <Yes/No>
[Yes]:
An existing template found.
=>Do you want to view the existing template? <Yes/No> [Yes]:

-------------------------------------------------------------------------------
CREATE STANDBY DATABASE TEMPLATE SUMMARY
-------------------------------------------------------------------------------
A - GENERAL SETTINGS
-------------------------------------------------------------------------------
TEMPLATE ID 1
DDC FILE orcl
SOURCE HOST mylinux
DESTINATION HOST linuxstb
STANDBY ASM Y
COPY DATAFILES DIRECTLY N
COMPRESS DATAFILES Y
USE TRANSPORTABLE MEDIA N
PRIMARY TEMP LOCATION /usr/tmp
STANDBY TEMP LOCATION /usr/tmp
STOP POINT SET N
CREATE DIRECTORIES AUTO
CREATED ON 20-12-2011 23-53-21
-------------------------------------------------------------------------------

B - INIT ORA PARAMETERS
-------------------------------------------------------------------------------
audit_file_dest /u01/app/oracle/admin/orcl/adump
compatible 11.2.0.0.0
control_files +DG_DATA/orcl/controlfile/current.258.770348255, +DG_DATA/orcl/controlfile/current.259.770348257
db_block_size 8192
db_create_file_dest +DG_DATA
db_name orcl
db_recovery_file_dest +DG_DATA
db_recovery_file_dest_size 4794089472
diagnostic_dest /u01/app/oracle
dispatchers (PROTOCOL=TCP) (SERVICE=orclXDB)
memory_target 838860800
open_cursors 300
processes 150
remote_login_passwordfile EXCLUSIVE
spfile /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfileorcl.ora
undo_tablespace UNDOTBS1

-------------------------------------------------------------------------------
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]:

Creating standby database...
Backing up datafile 1...
Backing up datafile 2...
Backing up datafile 3...
Backing up datafile 4...
Backing up datafile 5...
Backing up datafile 6...
Backing up datafile 7...
Backing up datafile 8...
Creating standby controlfile controlfile...
Creating standby parameter file...
Backup of primary database completed.
Transferring /usr/tmp/dbv_orcl_dbf_1_3_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_1_3_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_1_4_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_1_4_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_2_5_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_2_5_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_3_6_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_3_6_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_4_7_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_4_7_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_5_8_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_5_8_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_6_9_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_6_9_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_7_10_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_7_10_1.piece ...
Transferring /usr/tmp/dbv_orcl_dbf_8_11_1.piece to host linuxstb:/usr/tmp/dbv_orcl_dbf_8_11_1.piece ...
Shutting down standby database on linuxstb...
Standby database orcl on linuxstb shutdown.

Spfile +DG_DATA/orcl/spfileorcl.ora created on remote server.
Pfile /u01/app/oracle/product/11.2.0/dbhome_1/dbs/initorcl.ora created on
remote server.

Restoring standby control files...
Starting Standby Database orcl...
Standby Database orcl started nomount.
Standby database orcl on linuxstb startup nomount.

Shutting down standby database on linuxstb...
Standby database orcl on linuxstb shutdown.

Standby control files restored.
Starting Standby Database orcl...
Standby Database orcl started .
Standby database orcl on linuxstb mounted.

Restoring datafile 1...
Restoring datafile 2...
Restoring datafile 3...
Restoring datafile 4...
Restoring datafile 5...
Restoring datafile 6...
Restoring datafile 7...
Restoring datafile 8...
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 sync with primary.

Please press <Enter> to continue...
=========================================================
Standby Database creation on linuxstb 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/dbvisit/standby)
dbvisit database_name

[oracle@mylinux standby]$ /usr/local/dbvisit/standby/dbvisit orcl
=============================================================
Dbvisit Standby Database Technology (6.0.16.7995) (pid 16047)
dbvisit started on mylinux: Thu Dec 29 23:29:51 2011 (CLI)
=============================================================

Obtaining information from standby database (RUN_INSPECT=Y)...
Checking Dbvisit Standby configurational differences between mylinux and linuxstb...
No Dbvisit Standby configurational differences found between mylinux and linuxstb.

Log file(s) for orcl will be transferred from mylinux to linuxstb...
Transferring thread_1_seq_2.367.771204369.gz to host linuxstb:thread_1_seq_2.367.771204369.gz
201112292329 - 1 Log transfer to linuxstb for orcl completed.
Last sequence was 2.

Starting Dbvisit Archive Management Module (AMM)...
Dbvisit Archive Management Module (AMM)
(Number to keep: 0) (Days to keep: 7) (Archive backup count: 0) (Diskspace full threshold: 80%)
Processing +DG_DATA/orcl/archivelog/2011_12_29...
Dbvisit Archive Management Module (AMM) cannot be used with Oracle ASM...skipping

=============================================================
dbvisit ended on mylinux: Thu Dec 29 23:31:03 2011
=============================================================

[oracle@mylinux standby]$ ssh linuxstb /usr/local/dbvisit/standby/dbvisit orcl
=============================================================
Dbvisit Standby Database Technology (6.0.16.7995) (pid 14204)
dbvisit started on linuxstb: Thu Dec 29 16:31:30 2011 (CLI)
=============================================================

Log file(s) for orcl from mylinux will be applied to linuxstb...
201112291631 - Log seq 2 thread 1 applied to standby database orcl.

Starting Dbvisit Archive Management Module (AMM)...
Dbvisit Archive Management Module (AMM)
(Number to keep: 0) (Days to keep: 7) (Diskspace full threshold: 80%)
Processing /u01/app/arch...
Archive log dir: /u01/app/arch
Total number of archive files : 29
Number of files deleted : 0
Current Disk percent full : 78%

=============================================================
dbvisit ended on linuxstb: Thu Dec 29 16:31:52 2011

No comments: