Troubleshooting
Problem
After creating a New index from the backend on the Audit table [A_WORKORDER] and ran the "Refresh Index Tables" from Maximo Database configuration application. MAXATTRIBUTE.PRIMARYKEYCOLSEQ in COMPANIES object for attribute: COMPANY,ORGID was 1 and 2 respectively. After the "Refresh Index Tables" the MAXATTRIBUTE.PRIMARYKEYCOLSEQ got changed to 1 for Attribute COMPANIESID and the MAXATTRIBUTE.PRIMARYKEYCOLSEQ was set to null for Attributes [COMPANY,ORGID ] in COMPANIES object.
Symptom
Companies are getting created multiple time instead of updating the Existing company data.
Resolving The Problem
The out of the box primary key seq should be ORGID =1 and COMPANY=2. You need to ensure you have this index before running the sql statements below.
You can update the primarykeycolseq from the backend running these sql statements
update MAXATTRIBUTE set primarykeycolseq=1 where OBJECTNAME =
'COMPANIES' AND ATTRIBUTENAME='ORGID'
update MAXATTRIBUTE set primarykeycolseq=2 where OBJECTNAME =
'COMPANIES' AND ATTRIBUTENAME='COMPANY'
update MAXATTRIBUTECFG set primarykeycolseq=1 where OBJECTNAME =
'COMPANIES' AND ATTRIBUTENAME='ORGID'
update MAXATTRIBUTECFG set primarykeycolseq=2 where OBJECTNAME =
'COMPANIES' AND ATTRIBUTENAME='COMPANY'
Go to Database Configuration, select Admin mode on, once in Admin Mode then turn Admin mode off. This should refresh the object cache.
If you have the maxattributecfg, maxattribute, maxsysindexes and maxsyskeys data before you refreshed the indexes and the same data after you refreshed the indexes we may be able to explain what happened. Otherwise, we guessing that maxsyskeys metadata did not reflect the physical indexes on the table. Therefore when you did a refresh the primarykeycolseq did not match the physical index and it defaulted to the primary key index, which is on the sequence id.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21999338