IBM Support

Integrity Checker reports errors about table ISEXTRACTCONFIG

Troubleshooting


Problem

Integrity Checker reports the following error:

BMXAA0443E -- Error - BMXAA0497E -- The following columns are defined to be 'same-as', but have different definitions:
  ISEXTRACTCONFIG.OWNERID same as ISEXTRACTCONFIG.ISEXTRACTCONFIGID

Symptom

Column ISEXTRACTCONFIG.OWNERID is defined to be the same-as - same data type and length - as column ISEXTRACTCONFIG.ISEXTRACTCONFIGID.  But the columns are not the same data type.  Column ISEXTRACTCONFIG.OWNERID is an integer; column ISEXTRACTCONFIG.ISEXTRACTCONFIGID is data type bigint.

Cause

Table ISEXTRACTCONFIG is added by third-party product Interloc Mobile Informer.  Columns OWNERID and ISEXTRACTCONFIGID are defined inconsistently.

Environment

Maximo with Interloc Mobile Informer

Diagnosing The Problem

The values for maxtype and length in the two rows returned by this SQL query should be the same, but they are not:
Select objectname, attributename, sameasobject, sameasattribute, maxtype, length, scale, required, persistent From maxattribute Where (objectname='ISEXTRACTCONFIG' And attributename='ISEXTRACTCONFIGID') Or (sameasobject='ISEXTRACTCONFIG' And sameasattribute='ISEXTRACTCONFIGID') ;
ISEXTRACTCONFIG.OWNERID is maxtype integer and length 12.  ISEXTRACTCONFIG.ISEXTRACTCONFIGID is maxtype bigint and length 19. 

Resolving The Problem

Two options:
  1. Use Database Configuration to change the data type of column ISEXTRACTCONFIG.OWNERID to bigint
  2. Apply the following 7 SQL statements:
Update maxattribute Set maxtype='BIGINT', length=19 Where objectname='ISEXTRACTCONFIG' And attributename='OWNERID'
go
Update maxattributecfg Set maxtype='BIGINT', length=19 Where objectname='ISEXTRACTCONFIG' And attributename='OWNERID'
gp
Drop Index isextractconfig_ndx3 On isextractconfig
go
Drop Index isextractconfig_ndx4 On isextractconfig
go
Alter Table isextractconfig Alter Column ownerid bigint
go
Create Index isextractconfig_ndx3 On isextractconfig(ownerid, extracttype, todelete)
go
Create Index isextractconfig_ndx4 On isextractconfig(ownerid, extracttype, toinclude)
go
Note the last SQL command is for SQL Server.  Syntax will be slightly different on other database platforms.  After column ISEXTACTCONFIG.OWNERID is altered, again run Integrity Checker in report mode to confirm the error is no longer reported.

Document Location

Worldwide

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"Integrity Checker","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWT9A","label":"IBM Control Desk"},"Component":"Integrity Checker","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

TS001756889

Document Information

Modified date:
29 January 2019

UID

ibm10869178