What Database Tables Need to Updated When Refreshing Data Between a Donor and Target OTM Instance Where Scalability Has Been Enabled (Doc ID 1427433.1)

Last updated on JUNE 22, 2016

Applies to:

Oracle Transportation Management - Version 6.0 to 6.4.1 [Release 6 to 6.4]
Information in this document applies to any platform.

Goal

The goal of this document is to provide information regarding the tables that need to updated when refreshing data between two OTM databases where Scalability ( SCA ) has been enabled on the Target or Donor OTM instance.

Note: If you are moving from a SCA to SCA setup or a non-SCA to SCA instance you must follow steps 1 - 5 in the "Retaining the SCA setup on the Target Instance" section of these instructions in order to retain the existing SCA configuration of the Target database. Failure to do so will wipe out the current SCA configuration on the Target database. These instructions are written using the assumption that you will have a DEFAULT APP_MACHINE and DEFAULT APP_SERVER in both the Donor and Target DB's. If this is not the case the instructions would need to be further modified for your specific machine and server gid's for many of the SQL commands listed below.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms