We're here to help!

Upgrade during Rebuild after Activation

Follow

Read our docs This article covers the process to follow when you want to upgrade after activation and rebuild the standby on a new version. 

  • Primary = dbvlab01
  • Standby = dbvlab03
  • DB and DDC name = devdb

There are a few important things to take note of before starting the upgrade.

  • You will have to recreate the standby database.
  • You’ll have to contact our License and Renewals team to request a new Version 9 license key. 

1. Do the failover / activation of existing v8 Standby database

  1. Stop Dbvisit Schedules / Daemons.
  2. Manually send and apply logs

mceclip0.png

3. Activate the Standby Database

mceclip1.pngmceclip2.png

4. Verify that the DDC on New Primary (old standby) shows SOURCE is now New Primary.

mceclip4.png

2. Install Version 9.0.06 on both Hosts

1. Stop all Dbvisit processes on New Primary (old standby) and Old Primary.

2. Install the software on both hosts

Old Primary:

mceclip5.png

New Primary 

mceclip6.png

New Primary (Dbvserver)

mceclip7.png

 

3. Cleanup the old Primary DB 

  • Shutdown the old Primary database.
  • Delete the datafiles, files in FRA and archived logs

4. Start the Dbvisit Process on both Primary and Standby servers

1. Start the Dbvisit processes on old Primary

mceclip8.png

2. Start the Dbvisit processes on new Primary 

mceclip9.png

5. Upgrade the DDC on New Primary

1. Run the upgrade DDC command 

mceclip10.png

2. Apply the v9 license using the CLI

Lic.png

6. Run the CSD to recreate the Standby Database on Old Primary 

 Note my DATA diskgroup on Primary & Standby are different, so I had to change the Oracle Parameter db_create_file_dest accordingly

 1. Run CSD command on new Primary

oracle@dbvlab03[/usr/dbvisit/standby]: ./dbvctl -d devdb --csd
***Dbvisit Standby license will expire in 3 days. Please contact Dbvisit Standby
(www.dbvisit.com) to obtain license.

>>> Running pre-checks please wait... done
What would you like to do:
1 - Create standby datanase (and optionally save settings in template)
2 - Help
3 - Terminate processing
Please enter your choice [1]: 1
------------------------------------------------

=>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.
[N]:
Your input: N

Is this correct? <Yes/No> [Yes]:
--------------------------------------------------

=>Do you want to perform backup, transfer and restore operations in parallel
when possible? [Y]:
Your input: Y

Is this correct? <Yes/No> [Yes]:
--------------------------------------------------
A temporary location must be specified on dbvlab03 where the database will be
backed up to first.
This location must be big enough to hold RMAN backup of the whole database
(1.88GB).

=>Specify the location on this server: [/usr/tmp]:
Your input: /usr/tmp

Is this correct? <Yes/No> [Yes]:

--------------------------------------------------
=>Do you want to use an existing standby spfile rather than create a new one
from scratch? [N]:
Your input: N

Is this correct? <Yes/No> [Yes]:

----------------------------------------------------------------

=>Do you want to register a newly created standby database with Oracle Restart?
[N]:
Your input: N

Is this correct? <Yes/No> [Yes]:

The following oracle database parameters will be set in the standby database pfile or spfile:
----------------------------------------------------------------
SID NAME VALUE

*             audit_file_dest       /u01/app/oracle/admin/devdb/adump
*             compatible            11.2.0.4.0
*             db_block_size         8192
*             db_create_file_dest    +DATADR
*             db_domain                      
*             db_name                   devdb
*             db_recovery_file_dest     +FRA
*             db_recovery_file_dest_size 21474836480
*             db_unique_name            devdb
*             diagnostic_dest           /u01/app/oracle
*             dispatchers               (PROTOCOL=TCP) (SERVICE=devdbXDB)
*             log_archive_format         %t_%s_%r.dbf
*             memory_target              307232768
*             open_cursors               300
*             processes                  150
*             remote_login_passwordfile  EXCLUSIVE
*             service_names              devdb
*             spfile                     OS default
*             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]: 2

WARNING: Do NOT use single or double quotes to enclose parameter values!
Separate multiple values with a comma. If a comma is part of a value, escape it
with a backlash.

=>Enter full parameter name: []: db_create_file_dest
1 - Remove from the standby parameter file
(parameter will be set to default value)
2 - New value in the standby parameter file

=>Please enter your choice: []: 2

=>Enter new value (leave blank to set to null)[]: +DATA
Validating ... please wait

The following oracle database parameters will be set in the standby database pfile or spfile:
-------------------------------------------------------------------
SID NAME VALUE

* audit_file_dest /u01/app/oracle/admin/devdb/adump
*             compatible            11.2.0.4.0
*             db_block_size         8192
*             db_create_file_dest    +DATA
*             db_domain                      
*             db_name                   devdb
*             db_recovery_file_dest     +FRA
*             db_recovery_file_dest_size 21474836480
*             db_unique_name            devdb
*             diagnostic_dest           /u01/app/oracle
*             dispatchers               (PROTOCOL=TCP) (SERVICE=devdbXDB)
*             log_archive_format         %t_%s_%r.dbf
*             memory_target              307232768
*             open_cursors               300
*             processes                  150
*             remote_login_passwordfile  EXCLUSIVE
*             service_names              devdb
*             spfile                     OS default
*             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]: 1

Validating oracle database parameters... please wait
=>SUCCEEDED
---------------------------------------------------------

=>Create standby database template for devdb using provided answers? [Y]:
Your input: 1

Is this correct? <Yes/No> [Yes]:
---------------------------------------------------------

=>Continue with creating a standby database? (If No processing will terminate,
the saved template will be available for future use) [Y]:
Your input: 1

Is this correct? <Yes/No> [Yes]:

>>> dbvctl 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 dbvctl 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
>>> Creating standby control file...done
>>> Total database size for devdb is 1.88GB
>>> Backing up primary database...

Backing up datafile 1... done
Backing up datafile 2... done
Backing up datafile 3... done
Backing up datafile 4... done
Backing up datafile 5... done

>>> Transferring backup from dbvlab03 to dbvlab01 ...

Transferring /usr/tmp/DBV_DEVDB_CSD_DBF_1_lpuhb34u_1_1.RMAN...done
Transferring /usr/tmp/DBV_DEVDB_CSD_DBF_1_lquhb38i_1_1.RMAN...done
Transferring /usr/tmp/DBV_DEVDB_CSD_DBF_2_lruhb38n_1_1.RMAN...done
Transferring /usr/tmp/DBV_DEVDB_CSD_DBF_3_lsuhb3c3_1_1.RMAN...done
Transferring /usr/tmp/DBV_DEVDB_CSD_DBF_4_ltuhb3c9_1_1.RMAN...done
Transferring /usr/tmp/DBV_DEVDB_CSD_DBF_5_luuhb3cg_1_1.RMAN...done

>>> Starting standby database devdb on dbvlab01 mount ...done
>>> Restoring datafiles on dbvlab01 ...

Restoring datafile 1... done
Restoring datafile 2... done
Restoring datafile 3... done
Restoring datafile 4... done
Restoring datafile 5... done

>>> Renaming standby redo logs and tempfiles on dbvlab01...done
>>> Completing standby database creation...done
>>> Standby database created.
>>> Performing checkpoint and archiving logs... done
>>> Synchronising standby...done

PID:9351
TRACE:9351_dbvctl_csd_devdb_201911200847.trc
2. Verify the version on both sides 
 
mceclip12.png
 
mceclip13.png
7. Update the DDC 

1. Check the current status of the DDC 

mceclip14.png

2. To update the DDC on new Primary (old Standby)

    Run ./dbvctl -d <DDC> -R

mceclip15.png

 

8. Run the Graceful Switchover to switch the config back

gs1.png

mceclip17.png

mceclip18.png

Confirm the switch back in the Configuration

gs2.png

 

9. Send & Apply logs, run Log Gap report

mceclip19.png

 

10. Enable daemons on Primary & Standby to take care of automatic sending and apply of logs.

mceclip20.png

 

End of Procedure

 

Have more questions? Submit a request

Comments