IBM Support

Object Structure Alternate Indexes not working as expected

Technote (troubleshooting)


When setting an Alternate Index on an Object Structure, transactions sent in using the Maximo Integration Framework that should match an existing record via this alternate index fail and the following error is seen in the log:

BMXAA5598E - Processing of an inbound transaction failed. The processing exception is identified in document 1.
BMXAA4211E - Database error number 2601 has occurred when operating on <Object Name> <Object Unique ID>=X.
[LAB-SVL203]Cannot insert duplicate key row in object 'dbo.<object name>' with unique index '<alternate index name>'.

Resolving the problem

Make sure that all attributes used on this index are not set to Search Type: TEXT. They need to be WILDCARD or EXACT for the index to function correctly.

This is set via Database Configuration. Open the Object in question, check the Index tab to find the Alternate Index that has been defined on the Object Structure, make a note of all the Attributes on the Index.

Then go to the Attribute tab and open each Attribute and check the Search Type.

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Control Desk
Systems and Asset Management Tivoli Asset Management for IT
Systems and Asset Management Tivoli Change and Configuration Management Database
Systems and Asset Management Tivoli Service Request Manager

Document information

More support for: Maximo Asset Management
MEA: Generic

Software version: 7.1, 7.1.1, 7.5, 7.6

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1625050

Modified date: 24 April 2013

Translate this page: