We're here to help!

Downgrade Dbvisit Standby from 8.0.x to 7.0.x

Follow

Description

In the event that a Downgrade is required from version 8.0.x to 7.0.x where for example an upgrade was performed on an unsupported configuration (example 10g database), the following high level steps may be followed to re-enable a version 7 environment.

 


Solution

Option 1: A backup is available

This option assumes that prior to performing the upgrade from version 7 to version 8, a backup was taken of the Dbvisit Base directory.  This directory is the location where Dbvisit Standby is installed into:

Example Dbvisit Base Locations:  

  • Default Dbvisit Base on Windows Based Systems: C:\Program Files (x86)\Dbvisit 
  • Default Dbvisit Base on UNIX based systems: /usr/dbvisit

 

In option 1 we assume that Dbvisit Base used is /usr/dbvisit and that this location was in fact backed up prior to the upgrade.  If this is the case the rollback process is in fact really easy and the high level steps are listed below: 

 

  1. Shutdown current Dbvisit Processes (dbvagent, dbvnet, dbvserver)
  2. Stop any Schedules or version 8 Daemons 
  3. Remove the version 8 installation from the DBVISIT_BASE directory - /usr/dbvisit/* in this example
  4. Restore the backup of the /usr/dbvisit folder as it was prior to the upgrade
  5. Start Dbvnet:  "cd /usr/dbvisit/dbvnet; ./dbvnetd start"
  6. Start Dbvserver:  "cd /usr/dbvisit/dbvserver; ./dbvserverd start"
  7. Note - if using Oracle RAC and you had Dbvisit Standby version 7 configured from all nodes in the cluster, make sure you restore and perform the above steps (1-6) on all the nodes.
  8. Run Dbvisit on the Primary:
    • From both primary nodes run: ./dbvisit –R <DDC>
    • Note: Run this on both RAC nodes if you are using RAC - same as what you would have had before.
  9. Run Dbvisit Standby from standby server to apply all available logs: ./dbvisit <DDC>
  10. Everything should be back running as version 7 now.
  11. You can now re-enable your Schedules

 

Option 2:  No Backups in place

In the event where a version 7.0.x installation was upgraded to version 8 without a backup, you might be surprised to find that Dbvisit Standby version 8 actually did backup the version 7 DDC file during the upgrade process.  

The file will be in the DBVISIT_BASE/standby/conf directory with a timestamp appended to it.  It might be that you have more than one.  This can happen if you ran multiple upgrades.  

You will have to review these DDC file backups which is in the format : dbv_<DDC>.env.YYYYMMDDHHMM

Example: dbv_DEV.env.201701230314

Note that you will have to review these files and identify the one that was created at the time of the upgrade.

TIP: In version 8 DDC files we now have the DDC parameter:  DBVISIT_FULLVERSION 

If this parameter is present, it is not a version 7 DDC file.  Identify the last DDC file that does not have this parameter - if you know when you did the upgrade, this you can use the timestamp to help identify the correct file.

Once you have identified the file, follow these steps.  Make sure you identify all Primary Node DDC files if you were using Oracle RAC configuration.  This is required if you were running version 7 from all primary RAC nodes.

 

The steps you will then follow are discussed below:

  1. Copy the version 7 DDC file backup - identified as discussed above to a backup location
  2. Remove all files from the DBVISIT_BASE directory
  3. Install Latest Version 7 into this base - example 7.0.64
  4. Copy the DDC file from step 1 into DBVISIT_BASE/standby/conf directory without the timestamp.
  5. Repeat Step 1-4 on all nodes (primary and standby)
  6. Start Dbvnet: "cd /usr/dbvisit/dbvnet; ./dbvnetd start"
  7. Start Dbvserver: "cd /usr/dbvisit/dbvserver; ./dbvserverd start"
  8. Note - if using Oracle RAC and you had Dbvisit Standby version 7 configured from all nodes in the cluster, make sure you restore and perform the above steps (1-6) on all the nodes.
  9. Run Dbvisit on the Primary:
    1. From both primary nodes run: ./dbvisit –R <DDC>
      Note: Run this on both RAC nodes if you are using RAC - same as what you would have had before.
  10. Run Dbvisit Standby from standby server to apply all available logs: ./dbvisit <DDC>
  11. Everything should be back running as version 7 now.
  12. You can now re-enable your Schedules

 

Option 3:  No Backups in place and no backup DDC files in DBVISIT_BASE/standby/conf

If this is the case, there is no other option but to perform a clean new Dbvisit Standby version 7 installation.

The tasks to perform this is discussed in the Online Documentation.  Please review this for more detail.

 

 

NOTE:  After you have rolled back, make sure you perform backups.

 

Have more questions? Submit a request

Comments