CA TDM Troubleshooting

This article includes information that can help you troubleshoot issues that you might face while working with CA TDM.
tdm35
This article includes information that can help you troubleshoot issues that you might face while working with CA TDM.
 
3
 
2
 
 
Datamaker
Mismatch Between Datamaker and Repository Versions
Symptom
 
After I upgrade Datamaker and open it, I receive the following error message:
 
Licence Package version (3.2D) differs from Test Data Repository version (3.2C) error message.
 
The steps that caused this error in my case are as follows:
  1. Download CA TDM to a virtual machine and other individual local computers.
  2. Execute the setup file (.exe) for upgrading the already installed CA TDM version on the virtual machine.
  3. On the local computers, launch Datamaker.
    The following error message is displayed:
    Licence Package version (3.2D) differs from Test Data Repository version (3.2C) error message.
     
In this scenario, CA TDM is installed on the virtual machine where the repository database is installed. Other users have CA TDM installed on their local computers, but they use the repository located on the virtual machine to connect to Datamaker.
 
Solution
 
This error message occurs when the repository database is not in sync with, or not upgraded to the same version as, the repository connection you are trying to use on your local machine. From the error message, you can see that the repository is on a different version than the installation of CA TDM. 
The error message mentions the License Package, and this refers to the file pk_gtrep_lic.tsq in your Datamaker directory folder (C:\Program Files (x86)\Grid-Tools\GTDatamaker). You can open this file by using an appropriate editor. When you search for "Repository version" in this file, you see a line with the repository version listed. You can then compare this version number to the one in the error message and see that the repository is out of sync with your new or current installation.
The repository database being out of sync with your connection after an upgrade can be caused by either an incomplete upgrade or not performing repository maintenance after upgrading.
You can resolve this issue by re-executing the CA TDM setup installer (in case of an incomplete upgrade) and performing repository maintenance to sync your repository with your newly installed version of CA TDM. 
Before you start, verify that you have already performed the following tasks:
  • Download the appropriate CA TDM release you are planning to upgrade to on the computer where you have your current CA TDM release installed.
  • Note the user name and password of a user in the ADMIN group to perform an upgrade.
  • Close all the CA TDM and CA Agile Requirements Designer applications and stop the TDoD and remote publish services before starting the upgrade.
To re-execute the CA TDM setup installer, follow these steps:
  1. Double-click the setup_GTServer_x.x.x.xx.exe file (for example, setup_GTServer_3.6.0.19.exe) to extract all the compressed .zip files. 
  2. Browse for a destination and extract the files.
  3. Double-click the setup_GTServer_x.x.x.xx.exe file.
    The 
    GTServer Setup
     dialog opens. 
  4. On the 
    Welcome to the Prerequisites Wizard
     page, click the 
    Next
     button.
    Note:
     If you already attempted to upgrade once, you may be prompted with an extra window to repair or remove the CA TDM installation. Click the repair option.
  5. Accept the license agreement and click 
    Next
    .
  6. On the 
    Prerequisites
     dialog, leave everything checked as is and click 
    Next
    .
  7. For each prerequisite and product component, follow the specified prompts and finish the installation.
To finish upgrading the repository, follow these steps:
  1. Double-click the Datamaker icon on your desktop to launch the Datamaker UI.
  2. Log into Datamaker with your administrator credentials and connect to the repository.
    The following error is displayed: 
    Test Data Repository version specified in database (3.1B) is invalid. This version of the software can work with Test Data Repository versions 3.2A and above only. In order to run the upgrade you will need to know the user name and password of a user in the ADMIN group. Would you like to attempt an upgrade?
     
    Note:
     Your database and repository versions might be different from the example error message.
  3. Click 
    Yes
    .
  4. Enter the administrator user name and password, and click the green check mark in the bottom-right corner.
    The 
    CA Test Data Manager - Datamaker Repository Schema - Update Required
     dialog opens. 
  5. Click 
    Yes
    .
    A list of all your connection profiles is displayed.
  6. Connect to a profile and click the green button in the bottom-left corner.
    You can now access Datamaker and its toolbar.
    Note: 
    If you receive any error messages regarding the rep.xml, see Upgrade Product Components.
  7. Perform the repository maintenance so that everything with your repository and current installation are in sync. For more information about how to perform repository maintenance, see Repository Administration.
After you complete the upgrade and perform the repository maintenance, the version mismatch error message is no longer displayed.
No Valid Project Assigned to the User
 
Symptom
 
When I try to log into Datamaker, I get the following error message:
 
FATAL ERROR: CA Test Data Manager-Datamaker User Logon 
 
 
No valid project (with at least one version) has been assigned to this user!
 
 
Solution
 
This error message occurs when one of the user groups to which you have been assigned was incorrectly created or configured. This is why you are unable to log in successfully.
To resolve this issue, you can have another user create a new project and give you administrator rights to the project. This enables you to log in successfully, create sub-projects, and assign users to projects.
Unable to Connect to DB2 Through Datamaker
 
Symptom
 
I have access to a DB2 environment. However, when I am trying to connect to the DB2 database (source or target) through Datamaker, I am getting an error. I also tried copying the db2jcc.jar and db2jcc_license_cisuz.jar jar files to the C:\Program Files (x86)\Grid-Tools\GTDatamaker\lib folder without any success. 
How can I connect Datamaker (which is installed on Windows computer) to DB2 (which is installed on a Unix computer)?
 
Solution
 
The steps that you followed are for a Java application (for example, Fast Data Masker). To connect to IBM DB2 on LUW, z/OS, or iSeries using ODBC, .NET, or JDBC, you need DLLs and JARs that a client application named IBM DB2 Connect (also known as IBM Data Server Client) provides.
Additionally, review the following considerations:
  • IBM DB2 Connect used to come in two flavors: Personal Edition and Enterprise Edition. The Personal Edition is discontinued now. 
  • IBM DB2 Connect EE(Enterprise Edition) is a marketing name, but when it comes to downloading and installing the software, it is called IBM Data Server Client. 
  • IBM Data Server Client needs to be licensed if you are connecting to DB2 z/OS or iSeries (that is, AS400). For connecting to DB2 on LUW (including AIX), unlicensed version of IBM Data Server Client downloaded from the internet serves the purpose.
  • Licensing of IBM Data Server Client to connect to DB2 z/OS or iSeries means two things:
    • If you are using ODBC- or .NET-based application (for example, Datamaker or TDoD service), get the paid license file db2consv_ee.lic and apply the license using the 
      db2licm –a db2consv_ee.lic
       command.
    • If you are using a JDBC application, include the licensed file db2jcc_license_cisuz.jar in the CLASSPATH. For example, for GTSubset.exe, include db2jcc_license_cisuz.jar in the \lib folder. When you download the activation license from the IBM website, db2jcc_license_cisuz.jar is present in the same folder/zip file as db2consv_ee.lic.
  • When a 64-bit IBM Data Server Client is installed on Windows, it gets installed in the C:\Program Files\IBM\SQLLIB folder. If you are asked to copy the JDBC drivers from IBM DB2 Connect, you can copy the requested JAR files from C:\Program Files\IBM\SQLLIB\java.
  • Each IBM DB2 Connect EE SKU (for example, D58FILL) is a bundle of 25 authorized or floating licensed users. If you buy two D58FILL, it means you are buying license for 50 authorized users to connect to DB2 on LUW, z/OS, or iSeries.
  • Find the full list of various versions and fix packs of IBM Data Server Client that are available on a given day at http://www-01.ibm.com/support/docview.wss?uid=swg27016878.
Unable to Use the 32-Bit Version of Datamaker
 
Symptom
 
I am unable to use the 32-bit version of Datamaker. Is there a 64-bit version available?
 
Solution
 
The CA TDM Portal is a 64-bit component that is now available for use. The Portal currently provides some of the functionality that Datamaker does, and new functionality is being added with each release. For example, the Portal has its own publish engine and enables capabilities such as Tester Self-Service, which the older Test Data on Demand (TDoD) interface used to provide.
For more information about the CA TDM Portal, see CA TDM Portal.
Appending Additional Records to the Same Data Pool
 
Symptom
 
I have imported data from a Microsoft Excel file into a data pool. I have additional data in another Microsoft Excel file (with the same format) that I want to append to the same data pool. How can I do this?
 
Solution
 
To append the additional records available in a second Micorsoft Excel file to the same data pool, follow these steps:
  1. Rename the second Microsoft Excel file (with the additional data) so that the file name matches the first file name that you have successfully registered and imported.
  2. Access Datamaker.
  3. Register the second file with the same project. On the registration dialog, ensure the following:
    1. The name in the 
      Workbook Name
       field matches the first file name.
    2. The
       Import Any Data
       option is selected.
    3. The 
      Register
       option is unchecked.
  4. Click the 
    Register/Import
     button.
    Additional records in the second file are appended to the same data pool.
 
Note: 
For data in a CSV file, right-click on the data pool that has the initial data imported, click 
Import External File Data
, and point to the CSV file. In this case, however, it is important that your CSV file does not contain the "Header" row with the column names. Otherwise, that will also get imported as a record in your data pool.
Datamaker Stops Responding During Data Import
 
Symptom
 
After I register tables in Datamaker and try to import the data into the data pool, Datamaker stops responding. The data is not imported into the data pool. Some of the tables have more than 25,000 records. 
 
Solution
 
This is a performance issue with Datamaker. Datamaker 3.5 and prior releases cannot manage data import with tables that have over 25,000 records (approximately). The number of records Datamaker can manage depends on factors such as the size of the record, number of columns, use of data types, and so on. Therefore, you might be able to import more or less depending on these factors.
Although Datamaker cannot typically handle a scale of 25-30 thousand records because it is a 32-bit application, the CA TDM Portal can. The CA TDM Portal can handle a much larger data volume and is the recommended solution for such scenarios. To import the data that has tables with over 25,000 records, we recommend upgrading to Datamaker 3.8 (or later) or using the CA TDM Portal.
Licensing Violation Error
 
Symptom
 
When I try to launch Datamaker, I receive the following error message:
 
A licensing violation has occurred - the application will stop!
 
 
Solution
 
The licensing violation error is not because of any licensing issue. This error is about how you are accessing Datamaker. If the same user tries to use multiple instances of Datamaker at the same time, this error message is displayed.
To address this issue, ensure that you are using only one Datamaker instance at a time.