IBM Support

IJ29853: UNABLE TO ADD NEW OBJECT IN MT GA TENANT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • ERROR DESCRIPTION:Ø
    Adding new object in GA fails in DBConfig with error
    DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,
    SQLERRMC=3;MAXIMO.MAXSYSKEYS, DRIVER=4.11.69
    
    STEPS TO REPRODUCE:
    1. Log into MT env as maxadmin and GA tenant
    2. Go to Database Configuration and insert new object.
    3. Object= SUBWORKTYPE and Save
    4. On Attributes tab add
    ORGID (same as Organization, Orgid)
    SUBWORKTYPE(Upper 20)
    WORKTYPE (Same as WORKTYPE, WORKTYPE)
    Save
    5. Turn on Admin mode and then Apply Configuration changes.
    6 During configure you will get the error
    DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,
    SQLERRMC=3;MAXIMO.MAXSYSKEYS, DRIVER=4.11.69
    
    RESULT:
    error in dbconfig
    BMXAA6818I - RestoreFromBackup started for schema MAXIMO,
    connected to database
    jdbc:db2://mx-multitenant-7611.fyre.ibm.com:50005/mt7612
    BMXAA6818I - ConfigDB started for schema MAXIMO, connected to
    database
    jdbc:db2://mx-multitenant-7611.fyre.ibm.com:50005/mt7612
    BMXAA0364I - Getting metadata
    BMXAA0349I - Configuring tables
    BMXAA0347I - Creating table SUBWORKTYPE.
    DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,
    SQLERRMC=3;MAXIMO.MAXSYSKEYS, DRIVER=4.11.69
    BMXAA6819I - ConfigDB completed with errors.
    BMXAA6820I - RestoreFromBackup completed without errors.
    
    EXPECTED RESULT:
    Object added successfully
    
    Product Version:
    Tivoli's process automation engine 7.6.1.2 Build 20200715-0100
    DB Build V7612-284 MT DB Build V7612-16
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Any user who is creating new table as GA with key as unique  *
    * ID                                                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Checking for the existing of the index should check unique   *
    * id as first column in index                                  *
    ****************************************************************
    

Problem conclusion

  • Change code to check for position 1 of the unique ID column in
    the index
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ29853

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-10

  • Closed date

    2021-07-09

  • Last modified date

    2021-07-09

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
10 July 2021