Upgrading Database on Source Location

This section provides step-by-step instructions for upgrading a source database in a channel with activated replication to ensure that no data is lost during the upgrade.

Upgrade Steps

1. Stop your application that is making changes to the database.

2. Ensure all changes made by the application are captured, and wait for the replication latency to reach zero. For more information on monitoring the replication latency, refer to the Statistics page.

3. Suspend the capture and integrate jobs running in a channel.

   {% tabs %}

   {% tab label="UI" %}

   1. Go to the Channel Details page.
   2. Under the Jobs pane, select the capture and integrate jobs.
   3. Click Suspend Jobs at the top right of the Jobs pane.

   

   {% /tab %}

   {% tab label="CLI" %}

   Run the dsssuspend command. For example:

   dsssuspend myhub mychannel
   

   {% /tab %}

   {% /tabs %}

4. Upgrade the source database.

5. Activate replication in the channel to capture changes from the beginning of the oldest current (not closed) transaction, and regenerate the jobs, state tables, and enroll information for the tables.

   {% tabs %}

   {% tab label="UI" %}

   1. Go to the Channel Details page and click Activate Replication.
   2. In the Activate Replication dialog, under Replication Components, select all options except Supplemental Logging.
   3. Click Activate Replication.

   

   {% /tab %}

   {% tab label="CLI" %}

   Run the command dssactivate with options -J, -E, -i, -ojesr. For example:

   dssactivate -J cap -J integ -E -i oldest_tx -ojesr myhub mychannel
   

   {% /tab %}

   {% /tabs %}

6. Start your application.