...
These are exactly the same steps detailed here - https://dbvisit.atlassian.net/wiki/display/UGDS7/Install+Dbvisit+Standby+-+Linux when installing via interactive mode.
Step 1
...
- Create DBVISIT_BASE directory
Create the “Dbvisit Base” directory. This is the directory into which Dbvisit Standby will be installed. The default location is /usr/dbvisit. This directory should be owned by the Oracle Database software owner.
...
| No Format |
|---|
root@dbvlab101[/usr]: cd /usr root@dbvlab101[/usr]: mkdir dbvisit root@dbvlab101[/usr]: chown -R oracle:oinstall dbvisit root@dbvlab101[/usr]: ls -ld dbvisit drwxr-xr-x 7 oracle oinstall 4096 Nov 10 14:09 dbvisit |
Step 2
...
- Download Latest Dbvisit Standby (version 7.0.x)
Download the latest software. The first step is to download the latest available version from the Dbvisit web site http://www.dbvisit.com. Once the software is downloaded, you can copy it to a temporary location on your server.
...
| No Format |
|---|
oracle@dbvlab101[/home/oracle/7.46]: ls -l total 98648 -rw-r--r-- 1 oracle oinstall 48656799 Oct 5 13:44 dbvisit-standby7.0.46-el6.zip |
Step 3
...
- Extract Installation Files
Extract the software downloaded in the previous step as well as updating the install-dbvisit file permission to allow the execution option. First use "unzip" to uncompress the downloaded software package, followed by using the "tar -xf" command to extract the archive.
...
| No Format |
|---|
oracle@dbvlab101[/home/oracle/7.46]: unzip dbvisit-standby7.0.46-el6.zip Archive: dbvisit-standby7.0.46-el6.zip inflating: dbvisit-standby7.0.46-el6.tar oracle@dbvlab101[/home/oracle/7.46]: oracle@dbvlab101[/home/oracle/7.46]: tar -xf dbvisit-standby7.0.46-el6.tar oracle@dbvlab101[/home/oracle/7.46]: oracle@dbvlab101[/home/oracle/7.46]: ls -lrt total 98648 -rw-r--r-- 1 oracle oinstall 110756 Oct 5 12:46 README.txt drwxr-xr-x 6 oracle oinstall 4096 Oct 5 12:46 dbvisit -rw-r--r-- 1 oracle oinstall 52234240 Oct 5 12:46 dbvisit-standby7.0.46-el6.tar -rw-r--r-- 1 oracle oinstall 48656799 Oct 5 13:44 dbvisit-standby7.0.46-el6.zip |
Step 4
...
- Run Installation in Batch Mode
Run the installer in batch mode. This eliminates the software from prompting the user for values during installation.
...
These tables will be used to maintain internal records used by Dbvisit Standby, including information regarding the transfer process of archive logs to the standby database. Please note that Create Standby Database (CSD) process will fail if DDR has not been created successfully.
DDR creation command
The command below shows an example, where the USERS tablespace is specified as the default tablespace and the TEMP tablespace as the default temporary tablespace for the user.
...
Please make sure to create and save the template by running the setup interactively and choose Option 7. Once the template is saved, exit from the setup.
Example creation of a CSD Template
...
In the example below, the Dbvisit Setup is executed and the Create Standby Database (option 7) is selected. This process will then be followed to create the CSD Template.
...
Note: As per example above the template was created and stored in the DDR. This must be done before you can execute the command below.
Command
The CSD Batch Command
...
| No Format |
|---|
./dbvisit_setup --csd --ddc <ddc> --template |
...
Example (Single Instance)
...
| No Format |
|---|
oracle@dbvlab101[/usr/dbvisit/standby]: ./dbvisit_setup --csd --ddc dev --template
=============================================================
dbvisit_setup started in BATCH mode at 20151116 22:18
csd = 1
ddc = dev
restart =
template = 1
output_dir =
web =
ddr =
INTERFACE_MODE = BATCH
=============================================================
./dbvisit_setup --csd --ddc dev --template
Creating standby database see trace file /usr/dbvisit/standby/trace/22804_dbvisit_setup_csd_dev_201511162218.trc
>>> Checking Dbvisit Standby for configurational differences between dbvlab101 and
dbvlab102...
No configurational differences found between dbvlab101 and dbvlab102.
>>> Checking Oracle installation on dbvlab102 in
/u01/app/oracle/product/11.2.0/db_1/bin/oracle...
>>> Checking primary datafiles on dbvlab101...
>>> Validating Dbvisit configuration file on dbvlab102...
>>> Checking if a database is up and running on dbvlab102...
Checks completed OK.
>>> Total database size for dev is 1.31GB
>>> Dbvisit will now run a pre-flight check for standby database creation. An attempt will
be made to create a standby (s)pfile using oracle standby database parameters, followed
by trying to start the standby instance. If this step fails, then please double-check
the following items before re-running Dbvisit again:
1) Review the standby database parameters you have supplied and provide valid values
unless a template is used.
2) Recreate the template to provide valid values for standby database parameters if a
template is used.
Running pre-flight check for standby creation, please wait... - done.
>>> Backing up primary database...
Backing up datafile 1... - done.
Backing up datafile 2... - done.
Backing up datafile 3... - done.
Backing up datafile 4... - done.
>>> Creating standby control file... - done.
Backup of primary database completed.
>>> Transferring backup from dbvlab101 to dbvlab102...
> Transferring 'dbv_dev_csd_dbf_1_12qmeir0_1_1.rman' to server dbvlab102:7890
Progress: 0%...20%...40%...60%...80%...100% [43507 KB/s] - done.
- done.
> Transferring 'dbv_dev_csd_dbf_1_13qmeit1_1_1.rman' to server dbvlab102:7890
Progress: 0%...20%...40%...60%...80%...100% [24272 KB/s] - done.
- done.
> Transferring 'dbv_dev_csd_dbf_2_14qmeit7_1_1.rman' to server dbvlab102:7890
Progress: 0%...20%...40%...60%...80%...100% [39616 KB/s] - done.
- done.
> Transferring 'dbv_dev_csd_dbf_3_15qmeiud_1_1.rman' to server dbvlab102:7890
Progress: 0%...20%...40%...60%...80%...100% [45445 KB/s] - done.
- done.
> Transferring 'dbv_dev_csd_dbf_4_16qmeiug_1_1.rman' to server dbvlab102:7890
Progress: 0%...20%...40%...60%...80%...100% [46481 KB/s] - done.
- done.
>>> Creating standby database parameter file... - done.
>>> Restoring standby control files... - done.
>>> Starting standby database dev on dbvlab102 mount... - done.
>>> Restoring datafiles on dbvlab102...
Restoring datafile 1 - done.
Restoring datafile 2 - done.
Restoring datafile 3 - done.
Restoring datafile 4 - done.
>>> Renaming standby redo logs and tempfiles on dbvlab102... - done.
>>> Performing checkpoint and archiving logs... - done.
>>> Finishing standby database creation... - done.
Standby database created.
To complete creating standby database please run Dbvisit on the primary server first,
then on the standby server, to ensure the standby database is in sync with the primary
database.
=============================================================
dbvisit_setup completed in BATCH mode at 20151116 22:24
============================================================= |
...
This option can also be used if there is a large gap between the primary and standby databases.
Sync Standby Database Batch Command
| No Format |
|---|
dbvisit_setup --sync --ddc <DDC> --tmp_dir <tmp_dir> --tmp_dir_dest <tmp_dir_dest> [--sync_lag] [--sync_nologging] [--web] [--output_dir] |
...
Example (Single Instance):
| No Format |
|---|
oracle@dbvlab101[/usr/dbvisit/standby]: ./dbvisit_setup --sync --ddc dev --tmp_dir /usr/tmp/ --tmp_dir_dest /usr/tmp/ --sync_lag --sync_nologging
=============================================================
dbvisit_setup started in BATCH mode at 20151117 00:13
csd =
ddc = dev
restart =
template =
output_dir =
web =
ddr =
INTERFACE_MODE = BATCH
=============================================================
./dbvisit_setup --sync --ddc dev --tmp_dir /usr/tmp/ --tmp_dir_dest /usr/tmp/ --sync_lag --sync_nologging
Synchronising standby database see trace file /usr/dbvisit/standby/trace/26412_dbvisit_setup_sync_dev_201511170013.trc
-------------------------------------------------------------------------------
Use RMAN incremental backups to synchronise a physical standby database
with the primary database. RMAN incremental backup of the primary
database will be created, starting at the current SCN of the standby,
which in turn will then be used to roll the standby database forward in
time.
RMAN incremental backups can be useful in case the physical standby
database:
Is lagging far behind the primary database.
Has widespread nologging changes.
Has nologging changes on a subset of datafiles.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
SUMMARY
-------------------------------------------------------------------------------
PRIMARY
Current SCN: 1796110 Time: 2015-11-17:00:11:05
Current sequence(s):
Thread 1 Sequence 204
Last archived sequence(s):
Thread 1 Sequence 203
STANDBY
Current SCN: 1795399 Time: 2015-11-17:00:07:08
Next SCN required for recovery: 1795104 Time: 2015-11-17:00:05:32
Sequence(s) required for recovery:
Thread 1 Sequence 203
No nonlogged transactions detected in standby datafiles.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Synchronising Standby Database
-------------------------------------------------------------------------------
Step 1 - Deleting previous incremental backup... - done.
Step 2 - Creating incremental backup of primary database... - done.
Step 3 - Creating standby control file... - done.
Step 4 - Transferring backup to standby server... - done.
Step 5 - Restoring standby control file... - done.
Step 6 - Cataloguing incremental backup in RMAN catalogue... - done.
Step 7 - Applying incremental backup to the standby database... - done.
Step 8 - Performing log switch on primary... - done.
Step 9 - Obtaining sync summary... - done.
Step 10 - Updating Dbvisit repository... - done.
-------------------------------------------------------------------------------
SUMMARY
-------------------------------------------------------------------------------
PRIMARY
Current SCN: 1796280 Time: 2015-11-17:00:14:59
Current sequence(s):
Thread 1 Sequence 205
Last archived sequence(s):
Thread 1 Sequence 204
STANDBY
Current SCN: 1796222 Time: 2015-11-17:00:14:03
Next SCN required for recovery: 1796180 Time: 2015-11-17:00:13:44
Sequence(s) required for recovery:
Thread 1 Sequence 204
No nonlogged transactions detected in standby datafiles.
-------------------------------------------------------------------------------
To complete standby database sync run dbvisit on the primary, then on the standby server.
=============================================================
dbvisit_setup completed in BATCH mode at 20151117 00:15
============================================================= |
...