CA Service Management - 14.1

17.3 17.2 17.1 14.1
English

Troubleshooting CA Service Management 14.1.04 Installation

This article contains the following:
casm1401
This article contains the following:
Issue: CA SDM Database Patch Fails
Sometimes, ApplyPTF fails to apply the
CA Service Management
 14.1.04 patch as some files are  used by another process. As a result, the 
Cum4
 folder is not created under the 
CASDM/Patches
 folder.
Resolution:
Exit and launch the installer again.
Issue: Language Independent Patch Installation Fails while Installing the Cumulative Patch
Example Scenario: When trying to install
CA Service Management
 14.1.04 on
CA Service Management
 14.1 (Advanced Availability), the language independent patch installation fails. The installation fails when attempting to load seed data for a table. 
Run the setup.exe from
RO96941
 and follow the installation wizard. The first part of CA SDM language independent patch (
T6EE243
)- installation happens, but the second step for CA SDM MDB Patch fails with error "
MDBTools install error=1
".
The following relevant messages are present in the
install_mdb.log
:
09-13,12:41:34 ERROR - java.lang.RuntimeException: Unable to migrate: ca_resource_family: please check table schema 
...
9-13,12:42:12 ERROR - MDBTools_0309E - DBDriver failed to install! 
09-13,12:42:12 WARN - MDBTools_0310W - DBDriver installed with one seed data error. 
09-13,12:42:12 INFO - MDBTools_0104I - Total time: 0H:0M:56S. 
09-13,12:42:12 MDBTools install error=1 
09-13,12:42:12 Setupmdb exit /B return code=1
The table specified in the "
Unable to migrate
" error message in the
install_mdb.log
 has one or more custom fields.  In the example scenario above, the table is "
ca_resource_family
".
Resolution:
Perform the following steps to resolve the problem. Confirm that the
ca_resource_family
 table depicted in this example scenario contains the custom fields.
If there are no custom fields for the
ca_resource_family
table
,
 the cause of the problem will not match the scenario documented for this issue and the below resolution will also be not applicable.
  1. Archive the data for the custom field(s) of the
    ca_resource_family
    table
    .
     
    You may use
    pdm_extract
     to achieve this.
  2. Archive the table definition; in particular, save the definition(s) of the custom field(s).
  3. Revert the table to the original (uncustomized) version by removing the custom field(s).
  4. Upgrade to
    CA Service Management
    14.1.04.
  5. If necessary, re-create the custom field(s) and re-load the archived data into the corresponding field(s).