IJ22881: ERROR: (IMPORTSTEP:CATALOGMERGER) NULL COM.IBM.DB2.JCC.AM.SQLINTEGRITYCONSTRAINTVIOLATIONEXCEPTION:

APAR status

• Closed as program error.

Error description

• Import failing with one of the following errors:
  
  
  
  ERROR:
  (ImportStep:CatalogMerger) null
  com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:
  One or more values in the INSERT statement, UPDATE statement,
  or foreign key update caused by a DELETE statement are not
  valid because the primary key, unique constraint or unique
  index identified by "3" constrains table
  "SAM.DISCOVERABLES_PERSISTENT" from having duplicate values for
  the index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=3.72.24
  at com.ibm.db2.jcc.am.hd.a(hd.java:809)
  
  
  ERROR:
  (ImportStep:CatalogMerger) SQLException -> Message :
  mainException
   -> SQL Message : One or more values in the INSERT statement,
  UPDATE statement, or foreign key update caused by a DELETE
  statement are not valid because the primary key, unique
  constraint or unique index identified by "3" constrains table
  "SAM.SOFTWARE_RELATIONSHIPS_PERSISTENT" from having duplicate
  values for the index key.. SQLCODE=-803, SQLSTATE=23505,
  DRIVER=3.72.24
  
  
  The issue is related with the software discovery done using the
  ISO tag in 9.2.16.0 version of the ILMT while only 9.2.17.0
  brings the component bundling options. Then, import in 9.2.18.0
  fails.
  
  TS003329843
  

Local fix

• Run one of the following SQL MERGE statements against ILMT
  database (depending on which step the import failed):
  
  merge into sam.discoverables_persistent trg_per using (
   select
    trg_per.id,
    src.id as ibm_id
   from ibm.discoverables src
   join sam.discoverables_persistent trg_per on src.guid =
  trg_per.guid and trg_per.ibm_id <> src.id
   where src.valid_to = '9999-12-31 23:59:59.997'
  ) as tmp
  on trg_per.id = tmp.id
  when matched then update set trg_per.ibm_id = tmp.ibm_id
  
  
  
  
  merge into sam.software_relationships_persistent trg_per using (
   select
    trg_per.id,
    src.id as ibm_id
   from ibm.software_relationships src
   join sam.software_relationships_persistent trg_per on src.guid
  = trg_per.guid and trg_per.ibm_id <> src.id
   where src.valid_to = '9999-12-31 23:59:59.997'
  ) as tmp
  on trg_per.id = tmp.id
  when matched then update set trg_per.ibm_id = tmp.ibm_id
  
  The catalog will not be attempted to be imported again unless it
   is uploaded one more time. To upload the same version of the
  catalog, you need to go to the Manamgement > Catalog Upload
  panel, select the catalog ZIP file (it is already present on the
   ILMT server machine in the
  <LMT_install_dir>/wlp/usr/servers/server1/data/sam/catalog/LMT/
  directory). After upload, trigger data import.
  

Problem summary

• ****************************************************************
  *****************
  ERROR DESCRIPTION:
  
  Import failing with error
  
  2020-02-07 07:02:09 (+0:00:00.001)
  
  ERROR: (ImportStep:CatalogMerger) null
  
  com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:
  
  One or more values in the INSERT statement, UPDATE statement,
  
  or foreign key update caused by a DELETE statement are not
  
  valid because the primary key, unique constraint or unique
  
  index identified by "3" constrains table
  
  "SAM.DISCOVERABLES_PERSISTENT" from having duplicate values for
  
  the index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=3.72.24
  
  at com.ibm.db2.jcc.am.hd.a(hd.java:809)
  
  
  
  The issue is related with the software discovery done using the
  
  ISO tag in 9.2.16.0 version of the ILMT while only 9.2.17.0
  
  brings the component bundling options (and the component definit
  ion itself). Then, import in 9.2.18.0
  fails.
  
  
  
  TS003329843
  
  ****************************************************************
  *****************
  * EXPECTED RESULTS:
  * The issue does not occur.
  ****************************************************************
  * RECOMMENDATION: Apply appropriate update when available.
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  packages:
   | Update | ILMT 9.2.19
  ****************************************************************
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LIC METRIC TOOL

• Fixed component ID

  5724LMTEM

Applicable component levels