IBM Support

IZ57378: DATABASE ERROR NUMBER 1 HAS OCCURRED WHEN OPERATIN ON LOCHIERARCHY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Maximo Version and Patch level
    -> 6.2.2 + HF10
    Server Operating Systems
     -> Maximo Administration Workstation : Windows XP
     -> Application Server : Solaris 10 - 64bit - SPARC
     -> Actuate Server : Windows Server 2003|
    Database platform
     -> Oracle10g(10.2.0.2)
    Web Appplication Server (WebSphere/WebLogic and Service Pack
    level)
     -> WAS 6.0.2.23
    < Recreation steps >
    1. On Locations application, click "New Location" icon.
    2. Enter the following values.
         Location    : TEST04
         Description : TEST04
         Type        : Operating
    3. "Select Action" --> "Manage Systems"
    4. On "Manage Systems" window, click "New Row"
    5. Enter the following values.
         System           : TEST01
         Description      : TEST01
         Site             : (anything)
         Primary System ? : Check
    6. Click "OK"
    7. "Select Action" --> "Associate Systems with Location"
    8. On "Associate Systems with Location" window, click "New Row"
    9. Enter the following value.
          System : TEST01
    10. Click "OK"
    11. Click "Save Location" icon
    12. "Select Action" --> "Duplicate Location"
    13. Enter the following values.
         Location    : TEST05
         Description : TEST05
         Type        : Operating
        ==> Do not click "Save Location" icon here
    14. "Select Action" --> "Associate Systems with Location"
    15. On "Associate Systems with Location" window, click "New Row"
    16. Enter the following value.
          System : TEST01
          Parent : TEST04
    17. Click "OK"
        ==> Then the error displays.
        On the customer's environment, using Oracle,
         "Database error number 1 has occurred when operatin on
    LOCHIERARCHY
          Site=XXXXX Location=TEST05 System=TEST01 Parent=TEST04.
          ORA-00001: unique constraint (MAXIMO.LOCHIERARCHY_NDX1)
    violated"
        .
        On our test environment, using DB2,
         "Database error number -803 has occurred when operatin on
          LOCHIERARCHY Site=XXXXX Location=TEST05 System=TEST01
          Parent=TEST04.
          DB2 SQL error. SQLCODE: -803, SQLSTATE: 23505, SQLERRMC:
    2;
          MAXIMO.LOCHIERARCHY
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Maximo users                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: IZ57378/09-16860:  SQL Error (unique    *
    *                      index violation) occurs when one        *
    *                      creates (but does not save) a new       *
    *                      location and tries to associate with a  *
    *                      system (and provide a parent location)  *
    *                      before saving.  When user clicks 'OK'   *
    *                      to finish the transaction in the        *
    *                      'Associate System with Location'        *
    *                      dialog, error occurs.                   *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    SQL Error (unique index violation) occurs when one creates (but
    does not save) a new location and tries to associate with a
    system (and provide a parent location) before saving.
    

Problem conclusion

  • In the 'Associate System with Location' dialog, when user
    clicks 'OK' transaction completes successfully.
    
    
    
    
    
    The fix for this APAR is contained in the following maintenance
    package:
    
      | release\fix pack | REL 6.2.6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ57378

  • Reported component name

    ASSETS

  • Reported component ID

    5724R46AS

  • Reported release

    621

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-08-07

  • Closed date

    2009-09-23

  • Last modified date

    2009-09-23

  • 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

    ASSETS

  • Fixed component ID

    5724R46AS

Applicable component levels

  • R621 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
09 April 2023