Upgrade History Database Schema

In most cases, when you upgrade CA XCOM Data Transport from Release 11.6 to Service Packs (using either silent mode or GUI mode), the history database schema is updated automatically. In rare cases, however, this schema is not updated (for example, if network failure occurs), and the upgrade completes with warning messages.
xdtw1161
In most cases, when you upgrade CA XCOM Data Transport from Release 11.6 to Service Packs (using either silent mode or GUI mode), the history database schema is updated automatically. In rare cases, however, this schema is not updated (for example, if network failure occurs), and the upgrade completes with warning messages.
In such cases:
  • Check the log files for the upgrade. For details, see 
    Review the Log File
     in Install or Upgrade in Silent Mode.
  • Analyze Return Codes.
If the schema was not upgraded successfully, run the UPGRADEDB.EXE utility to upgrade it.
To run the utility, follow these steps:
  1. Stop all transfers.
  2. Stop the Scheduler Service.
  3. Back up the history database.
  4. Verify that you have ALTER table privileges: The utility reads the history database configuration specified in the xcom.glb file and performs the upgrade operation. If the user specified in the xcom.glb file does not have ALTER table privileges, obtain a user ID that does have these privileges, and specify its credentials in the DBUSER and DBPASSWORD parameters in the next step.
    The utility fails if you do not provide the credentials of a user with the required ALTER table privileges.
  5. Run UPGRADEDB.EXE from the command line, using the syntax that follows.
Syntax:
 
UPGRADEDB.EXE [-v] [GLBFILE=xcom.glb file path] [LOGFILE=Log file path] [DBUSER=DatabaseUser] [DBPASSWORD=Database Password]
 
-v
  (optional) Prints logs on standard output terminal. It is ignored if you specify LOGFILE.
 
GLBFILE 
 (optional) Specifies the complete path name of xcom.glb file. The default is %XCOM_HOME%\config\xcom.glb.
 
LOGFILE
  (optional) Specifies the complete path name of the log file.
 
DBUSER 
 (optional) Specifies the database user having ALTER privileges. The default is the value of XCOMHIST_USER in xcom.glb.
 
DBPASSWORD 
 (optional) Specifies the database password for the user. The default is the value of XCOMHIST_PASSWORD in xcom.glb.
An example follows:
UPGRADEDB.EXE LOGFILE=c:\temp\update.txt
This utility performs the following actions in sequence:
  1. Reads the xcom.glb file to obtain the required history configuration parameters.
  2. Verifies that sufficient information is available in xcom.glb file.
  3. Performs basic validations to verify database connectivity.
  4. Verifies whether the history database schema requires updates.
  5. If schema updates are required, runs ALTER queries based on the type of DBMS in use. The utility is certified with supported DB2 LUW, DB2 z/OS, and MySQL DBMS versions.
  6. Verifies that the schema is up to date.
 
Return Codes:
 
 
0
  Successful
 
40  
Xcom.glb file not found or failed to open
 
41
  Failed to get required values (XCOMHIST, XCOMHIST_USER, XCOMHIST_TBL, XCOMHIST_PASSWORD) from xcom.glb
 
42  
Failed to allocate SQL Handle
 
43  
Failed to connect to Database
 
44  
Failed to get DBMS Name
 
45  
Failed to get Database Name or Database name is Blank
 
650 
 XCOM_HOME environment variable not set and GLBFILE not provided
 
-1
  Unhandled SQL exceptions