This article covers the process to follow when you want to upgrade from Dbvisit Standby version 7 to Dbvisit Standby version 8. In short, it will require upgrading the software and the existing DDC.
There are a few important things to take note of before starting the upgrade.
- You will not be required to recreate the standby database.
- To upgrade to Dbvisit Version 8, your Oracle database must be running Oracle 10.2.0.5 and above. See the Support Matrix
- You’ll have to contact our License and Renewals team to request a new Version 8 license key. The old V7 license will not work on V8.
- Note - for RAC configurations, the DDC will have to be recreated. Please refer to point 4 the Important Notes
1. Prepare the version 7 config
- Stop all schedules / cronjobs on both Primary and Standby
- Manually run dbvisit on Primary to send logs
3. Manually run dbvisit on Standby to apply logs
4. Manually run a log gap report on Primary to ensure no gap exists.
5. Stop all Dbvisit processes on Primary and Standby.
2. Upgrade the Dbvisit Standby Software
Upgrade the Dbvisit Standby as per detailed steps https://dbvisit.atlassian.net/wiki/spaces/DS8QSG/pages/104431669/Upgrade+Dbvisit+Standby#UpgradeDbvisitStandby-2.2.UpgradeDbvisitStandbySoftware
3. Start the Dbvisit Process on both Primary and Standby servers
1. Start the Dbvisit processes from the new Install Base on Primary
oracle@dbvlab01[/home/oracle/v8/dbvisit/installer]: cd /usr/dbvisit
oracle@dbvlab01[/usr/dbvisit]: ll
total 16
drwxr-x--- 6 oracle oinstall 4096 Mar 19 14:36 dbvagent
drwxr-x--- 6 oracle oinstall 4096 Mar 19 14:36 dbvnet
drwxr-x--- 6 oracle oinstall 4096 Mar 19 14:37 dbvserver
drwxr-x--- 10 oracle oinstall 4096 Mar 19 14:36 standby
oracle@dbvlab01[/usr/dbvisit/standby]:
racle@dbvlab01[/usr/dbvisit]: cd dbvnet
oracle@dbvlab01[/usr/dbvisit/dbvnet]: ./dbvnet -d start
Dbvnet daemon started.
oracle@dbvlab01[/usr/dbvisit/dbvnet]: cd ../dbvagent/
oracle@dbvlab01[/usr/dbvisit/dbvagent]: ./dbvagent -d start
Dbvagent daemon started.
oracle@dbvlab01[/usr/dbvisit/dbvagent]: cd ../
oracle@dbvlab01[/usr/dbvisit]: cd dbvserver/
oracle@dbvlab01[/usr/dbvisit/dbvserver]: ./dbvserver -d start
Dbvserver daemon started.
oracle@dbvlab01[/usr/dbvisit/dbvserver]: ps -ef|grep dbv
oracle 8362 1 0 14:50 ? 00:00:00 ./dbvnet -d start
oracle 8370 1 0 14:50 ? 00:00:00 ./dbvagent -d start
oracle 8380 1 0 14:50 ? 00:00:00 ./dbvserver -d start
2. Start the Dbvisit processes from the new Install Base on Standby
oracle@dbvlab03[/home/oracle/v8]: cd /usr/dbvisit
oracle@dbvlab03[/usr/dbvisit]: ll
total 16
drwxr-x--- 6 oracle oinstall 4096 Mar 19 14:40 dbvagent
drwxr-x--- 6 oracle oinstall 4096 Mar 19 14:40 dbvnet
drwxr-x--- 6 oracle oinstall 4096 Mar 19 14:41 dbvserver
drwxr-x--- 10 oracle oinstall 4096 Mar 19 14:40 standby
oracle@dbvlab03[/usr/dbvisit]: cd dbvagent/
oracle@dbvlab03[/usr/dbvisit/dbvagent]: ./dbvagent -d start
Dbvagent daemon started.
oracle@dbvlab03[/usr/dbvisit/dbvagent]: cd ../
oracle@dbvlab03[/usr/dbvisit]: cd dbvnet
oracle@dbvlab03[/usr/dbvisit/dbvnet]: ./dbvnet -d start
Dbvnet daemon started.
oracle@dbvlab03[/usr/dbvisit/dbvnet]: ps -ef|grep dbv
oracle 18425 1 0 14:51 ? 00:00:00 ./dbvagent -d start
oracle 18430 1 0 14:51 ? 00:00:00 ./dbvnet -d start
oracle 18434 4017 0 14:51 pts/0 00:00:00 grep dbv
4. Upgrade the DDC on Primary
1. Change directory to the Standby Core
oracle@dbvlab01[/usr/dbvisit/standby]: ll
total 8632
drwxr-x--- 2 oracle oinstall 4096 Mar 19 13:47 conf
-rwxr-xr-x 1 oracle oinstall 8789336 Mar 19 14:36 dbvctl
drwxr-x--- 2 oracle oinstall 4096 Mar 19 14:36 doc
drwxr-x--- 2 oracle oinstall 4096 Mar 19 14:36 gs
drwxr-x--- 2 oracle oinstall 4096 Mar 19 14:36 lib
drwxr-x--- 2 oracle oinstall 4096 Mar 19 14:06 log
drwxr-x--- 2 oracle oinstall 4096 Mar 19 14:05 pid
drwxr-x--- 2 oracle oinstall 20480 Mar 19 14:06 tmp
drwxr-x--- 2 oracle oinstall 4096 Mar 19 14:06 trace
2. Run the upgrade DDC command and follow the questions
- take note of DB_UNIQUE_NAME_DR
- take note if ASM will be used or not
oracle@dbvlab01[/usr/dbvisit/standby]: ./dbvctl -d devdb -o upgrade
=======================================
Dbvisit Standby Database Technology (8.0.26_0_ga39d778d) (pid 8422)
dbvctl started on dbvlab01: Tue Mar 19 14:53:18 2019
=======================================
>>> DDC file devdb version: 7
------------------------------------------------------------------------------
Enter DB_UNIQUE_NAME for the standby database
=>DB_UNIQUE_NAME_DR is [devdb]:
Your input: devdb
Is this correct? <Yes/No> [Yes]:
Choice is devdb
------------------------------------------------------------------------------
Enter ORACLE_SID for the ASM instance on the standby server. If the standby database does not use ASM storage, leave empty
=>ORACLE_SID_ASM_DR is []:
Is this correct? <Yes/No> [Yes]:
Choice is null
>>> DDC file devdb upgraded to version 8.0.26.
>>> Dbvisit Database repository (DDR) devdb created.
========================================================
dbvctl ended on dbvlab01: Tue Mar 19 14:53:57 2019
========================================================
3. Apply the version 8 license key
oracle@dbvlab01[/usr/dbvisit/standby]: ./dbvctl -d devdb -l 4jo6z-8aaai-u09b6-ijjxm-7o75q-06wug-6rm63
=============================================================
Dbvisit Standby Database Technology (8.0.26_0_ga39d778d) (pid 8504)
dbvctl started on dbvlab01: Tue Mar 19 14:55:52 2019
==============================================================>Update with license key: 4jo6z-8aaai-u09b6-ijjxm-7o75q-06wug-6rm63? <Yes/No> [Yes]:
>>> Dbvisit Standby License
License Key : 4jo6z-8aaai-u09b6-ijjxm-7o75q-06wug-6rm63
customer_number : 1
dbname :
expiry_date : 2019-04-15
product_id : 8
sequence : 1
status : VALID
updated : YES
=============================================================
dbvctl ended on dbvlab01: Tue Mar 19 14:56:04 2019
=============================================================
5. Manually Send and Apply Logs
1. Run dbvisit on Primary to send logs
oracle@dbvlab01[/usr/dbvisit/standby]: ./dbvctl -d devdb
=============================================================
Dbvisit Standby Database Technology (8.0.26_0_ga39d778d) (pid 8559)
dbvctl started on dbvlab01: Tue Mar 19 14:56:14 2019
=============================================================
>>> Obtaining information from standby database (RUN_INSPECT=Y)... done
Thread: 1 Archive log gap: 0. Transfer log gap: 632
>>> First time Dbvisit Standby runs, Dbvisit Standby configuration will be copied to
dbvlab03...
>>> Performing a log switch... done
>>> Transferring Log file(s) from devdb on dbvlab01 to dbvlab03 for thread 1:
thread 1 sequence 633 (thread_1_seq_633.1103.1003330593.gz)
=============================================================
dbvctl ended on dbvlab01: Tue Mar 19 14:56:38 2019
=============================================================2. Run dbvisit on Standby to apply logs
oracle@dbvlab03[/usr/dbvisit/standby]: ./dbvctl -d devdb
=============================================================
Dbvisit Standby Database Technology (8.0.26_0_ga39d778d) (pid 18643)
dbvctl started on dbvlab03: Tue Mar 19 14:57:07 2019
=============================================================
>>> Applying Log file(s) from dbvlab01 to devdb on dbvlab03:
thread 1 sequence 633 (1_633_999620717.arc)
Last applied log(s):
thread 1 sequence 633
Next SCN required for recovery 3307384 generated at 2019-03-19:14:56:32 +13:00.
Next required log thread 1 sequence 634
>>> Dbvisit Archive Management Module (AMM)
Config: number of archives to keep = 0
Config: number of days to keep archives = 7
Config: diskspace full threshold = 80%
==========
Processing /u01/app/oracle/dbvisit_archdest/devdb...
Archive log dir: /u01/app/oracle/dbvisit_archdest/devdb
Total number of archive files : 3
Number of archive logs deleted = 0
Current Disk percent full : 83%
Disk space is sparse (83% full) and it is not allowed to remove oldest archives from
-> /u01/app/oracle/dbvisit_archdest/devdb
This is due to DELETE_ARCHDEST_THRESHOLD = N being set in DDC file.
==========
=============================================================
dbvctl ended on dbvlab03: Tue Mar 19 14:57:11 2019
=============================================================3. Run Log Gap report on Primary
oracle@dbvlab01[/usr/dbvisit/standby]: ./dbvctl -d devdb -i
=============================================================
Dbvisit Standby Database Technology (8.0.26_0_ga39d778d) (pid 8657)
dbvctl started on dbvlab01: Tue Mar 19 14:57:47 2019
=============================================================
Dbvisit Standby log gap report for devdb thread 1 at 201903191457:
-------------------------------------------------------------
Destination database on dbvlab03 is at sequence: 633.
Source database on dbvlab01 is at log sequence: 634.
Source database on dbvlab01 is at archived log sequence: 633.
Dbvisit Standby last transfer log sequence: 633.
Dbvisit Standby last transfer at: 2019-03-19 14:56:38.
Archive log gap for thread 1: 0.
Transfer log gap for thread 1: 0.
Standby database time lag (DAYS-HH:MI:SS): +00:01:04.
=============================================================
dbvctl ended on dbvlab01: Wed Mar 19 14:57:54 2019
=============================================================
6. Post-installation steps.
- Start the daemon processes to allow Dbvisit Standby to run in the background (or enable normal schedules)
- Enable email notification
https://dbvisit.atlassian.net/wiki/spaces/DS8QSG/pages/106135901/E-Mail+Notification+Configuration
- Configure AMM (Archive Log Management Module) as required
Comments