Loading table content without a defined id value
search cancel

Loading table content without a defined id value

book

Article ID: 27686

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager CA Service Desk Manager

Issue/Introduction

While loading data to a table that exists within the MDB using pdm_load, you may see messages of the following type:

"<table name>: No numeric or logical key"

"ERROR: Cannot create mapping for table (<table name>)"

"ERROR: skipping table"

Environment

Release: 12.6 or higher
Component:  CA Service Desk Manager

Cause

The problem described above is seen most often when loading new data, i.e. data not previously unloaded from the MDB via e.g. pdm_extract.

The above messages occur because the data being loaded does not contain a (unique) UUID.

Resolution

To resolve the problem, run pdm_load with the '-i' parameter, e.g.:

pdm_load -i -f <datafilename>

Note: For a complete description of the parameters available run the following:

pdm_load -h

Additional Information

You can also use the corresponding pdm_extract command to obtain a pdm_load template.  Example:  if you wanted to load new locations, run this command in an Admin command prompt on the SDM Server:

pdm_extract -f "Select location_name from ca_location where location_name = 'XXXX'" > loc-name.dat

(substitute XXXX for a known location defined in SDM.)

- Open the resultant loc-name.dat file in Notepad.  You will see this in the file, following the above example:

TABLE ca_location
        location_name
        { "XXXX" }

- Modify the loc-name.dat file to add additional location content:

TABLE ca_location
        location_name
        { "Location 1" }
        { "Location 2" }

(Make sure there is an empty newline at the bottom of the loc-name.dat file)

- Save the loc-name.dat file, then load the new file in using this command:

pdm_load -i -f loc-name.dat

IMPORTANT:  Please test this in a testing environment and also test with a small batch of entries before attempting a large scale data load in either testing or production.  Make sure you also have a backup of your database performed before making such a change.