Resolving Failed Upgrades - Data Stream Architecture - Data Stream Utility

Data Stream Utility Installation, Configuration, and Upgrade Guide for Customers

Product
Data Stream Architecture
Data Stream Utility
Release Number
16.00
Published
November 2016
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
lzp1474305417988.ditamap
dita:ditavalPath
3151_DSE_ICUCustomer_1600.ditaval.ditaval
dita:id
B035-3153
Product Category
Software
Teradata Tools and Utilities
In deciding how to resolve a failed DSC upgrade, it is important to first determine the cause of the problem and the point at which the failure occurred. DSC, ClientHandler, BARCmdline, and BARPortlets must be on the same version.
  1. If the upgrade of the DSC fails in the post install section of the rpm install, there are two options:
    Option Description
    Revert back to the previous version If the DSC failed before the DSC repository was modified:
    1. Uninstall both the new and the previous version.
    2. Install the previous version again using the configuration information you saved before the upgrade was attempted.
    If the DSC failed during the DSC repository upgrade:
    1. Drop the BAR and BARBACKUP databases from the DSC repository.
    2. Re-install the previous version.
    3. Run import_repository_backup_config, importing the file you exported when you executed the export_repository_backup_config command.
    4. Run recover_backup_metadata.
    5. Run config_system to configure the repository job using the xml file to which you exported the configuration information (step 2 of Backing Up the DSC Repository and Configuration When Upgrading).
      dsc config_system -n dscnode_Repository_name -f repository_config_system.xml
    6. Run enable_component to enable the repository system.
      dsc enable_component -t SYSTEM -n dscnode_Repository_name
    7. Run a repository restore job using the BAR Setup portlet or the command-line interface.
    8. Execute a tpareset to the repository database.
    Attempt to perform the upgrade again If the DSC failed before the DSC repository was modified:
    1. Uninstall both the new and the previous version.
    2. Install the new version again using the configuration information you saved before the upgrade was attempted.
    If the DSC failed during the DSC repository upgrade:
    1. The DSC repository is corrupt and the previously existing data must be recovered. Since the schema of the repository is likely to have changed between the previous and new versions, the new version cannot be installed until the previous repository has been rebuilt so that the data can be recovered. To rebuild the previous environment, follow steps a through h listed in the row above, for a DSC failure during the DSC repository upgrade.
    2. After you have properly reverted to the previous build, re-attempt the upgrade to the new build.
  2. If the upgrade fails for DSA components other than the DSC so that the environment is corrupt:
    1. Uninstall both the previous and the new version of the component.
    2. After determining the cause of the failure, do a fresh install of either the new or old version using the information you saved before the upgrade was attempted.