APAR status
Closed as program error.
Error description
ERROR DESCRIPTION: Unique key value duplication error when you try to duplicate an asset template record after autonumber setup. PROBLEM: Autonumber is causing issues if set it up and you have an asset template record having master pm reference, because while trying to duplicate the asset template record, you will get the similar below error : BMXAA4129E - The record for Attribute=CAPACITY, Organization=EAGLENA, Section=, Template=100005 already exists. This validation error is thrown when an attempt is made to insert a new record with a unique key value that already exists in the database. Ensure that the key value for the given record is unique. More information If you remove the auto numbering from the asset template you do not get any issues and you are able to duplicate the asset template having master pm reference. STEPS TO REPLICATE : 1- In order to configure autonumering for Asset Templates, open your SQL tool and run the following statements : Insert into autokey(PREFIX,SEED,ORGID,SITEID,AUTOKEYNAME,SETID,LANGCODE,AUTO KEYID) values ('',100001,'EAGLENA','','AWM_ASTEMPLATE',null,'EN',AUTOKEYSEQ.NE XTVAL); update maxattributecfg set canautonum=1, autokeyname = 'AWM_ASTEMPLATE' where attributename='TEMPLATEID' and objectname ='PLUSCTEMPLATE'; update maxattribute set canautonum=1, autokeyname = 'AWM_ASTEMPLATE' where attributename='TEMPLATEID' and objectname ='PLUSCTEMPLATE'; commit; 2- Open Maximo as maxadmin 3- Go to Database Configuration app and search for the PLUSCTEMPLATE object 4- Add &AUTOKEY& into the default value for the TEMPLATEID attribute in that object 5- Save changes and configure database 6- Restart Maximo server 7- Log into Maximo, once it is back online, as maxadmin 8- Go to Asset Templates app and create a new one 9- Ensure there is a classification associated with this record, in the Specifications tab (you can use any) 10- Save record 11- Change the record status to ACTIVE 12- Click on Duplicate Asset Template (In Actions menu) 13- Save the new record. 14- You will get an error message like this: BMXAA4129E - The record for Attribute=CAPACITY, Organization=EAGLENA, Section=, Template=100005 already exists. This validation error is thrown when an attempt is made to insert a new record with a unique key value that already exists in the database. Ensure that the key value for the given record is unique. More information NOTE: If you change the TEMPLATEID value to another value, it saves the record correctly. CURRENT ERRONEOUS RESULT: Users cannot duplicate asset template records and keep the seed value in the unique field. EXPECTED RESULT: To be able to duplicate Asset Template records with no issues. ENVIRONMENT (SYSTEM INFO): Tivoli's process automation engine 7.6.0.9-IFIX20180522-0831 Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-04
Local fix
NA
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users of Asset Templates. * **************************************************************** * PROBLEM DESCRIPTION: * * Unique key value duplication error when you try to duplicate * * an asset template record after autonumber setup. * **************************************************************** * RECOMMENDATION: * **************************************************************** Autonumber is causing issues if set it up and you have an asset template record having master pm reference, because while trying to duplicate the asset template record, you will get the similar below error: BMXAA4129E - The record for Attribute=CAPACITY, Organization=EAGLENA, Section=, Template=100005 already exists. This validation error is thrown when an attempt is made to insert a new record with a unique key value that already exists in the database. Ensure that the key value for the given record is unique. More information If you remove the auto numbering from the asset template you do not get any issues and you are able to duplicate the asset template having master pm reference. STEPS TO REPLICATE : ***Note: Step 1 is not a supported configuration change. Autokey functionality is not supported on all attributes and implementing it through the back end could create unforseen issues. 1- In order to configure autonumering for Asset Templates, open your SQL tool and run the following statements : Insert into autokey(PREFIX,SEED,ORGID,SITEID,AUTOKEYNAME,SETID,LANGCODE,AUTO KEYID) values('',100001,'EAGLENA','','AWM_ASTEMPLATE',null,'EN',AUTOKEY SEQ.NEXTVAL); update maxattributecfg set canautonum=1, autokeyname ='AWM_ASTEMPLATE' where attributename='TEMPLATEID' and objectname='PLUSCTEMPLATE'; update maxattribute set canautonum=1, autokeyname ='AWM_ASTEMPLATE' where attributename='TEMPLATEID' and objectname='PLUSCTEMPLATE'; commit; 2- Open Maximo as maxadmin 3- Go to Database Configuration app and search for the PLUSCTEMPLATE object 4- Add &AUTOKEY& into the default value for the TEMPLATEID attribute in that object 5- Save changes and configure database 6- Restart Maximo server 7- Log into Maximo, once it is back online, as maxadmin 8- Go to Asset Templates app and create a new one 9- Ensure there is a classification associated with this record, in the Specifications tab (you can use any) 10- Save record 11- Change the record status to ACTIVE 12- Click on Duplicate Asset Template (In Actions menu) 13- Save the new record. 14- You will get an error message like this: BMXAA4129E - The record for Attribute=CAPACITY, Organization=EAGLENA, Section=, Template=100005 already exists. This validation error is thrown when an attempt is made to insert a new record with a unique key value that already exists in the database. Ensure that the key value for the given record is unique. More information NOTE: If you change the TEMPLATEID value to another value, it saves the record correctly. CURRENT ERRONEOUS RESULT: Users cannot duplicate asset template records and keep the seed value in the unique field. EXPECTED RESULT: To be able to duplicate Asset Template records with no issues. ENVIRONMENT (SYSTEM INFO): Tivoli's process automation engine 7.6.0.9-IFIX20180522-0831 Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-04
Problem conclusion
This is fixed in code. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Interim Fix for Release 7.6.1.2
Temporary fix
Comments
APAR Information
APAR number
IJ15209
Reported component name
ADMINISTRATION
Reported component ID
5724R46A1
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-04-02
Closed date
2019-05-07
Last modified date
2019-05-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
MAXIMO
Fix information
Fixed component name
ADMINISTRATION
Fixed component ID
5724R46A1
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
07 May 2019