IBM Support

IZ37911: VALUE OF MAXSYSINDEXES.CLUSTERRULE IS INCORRECT, CAUSING INCORRECT VALUE FOR STORAGEPARTITION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem Definition: In Maximo 7.1.1.3 Base Service , client
    wants to
    separate index and data tablespace .
    So, he created a maxdemo database manually using maxinst .
    ( ex. maxinst -sMAXIDX -tMAXDATA -i"maxdemo.ora"  )
    But, According to Maximo system table (MAXSYSINDEXES) ,
    some indexes are created on data tablespace( MAXDATA) ,while
    other
    indexes are created on index tablespace (MAXIDX)
    
    Env : Maximo 7.1.1.0 Oracle DB : Replicated
          Maximo 7.1.1.3 DB2 DB : Replicated
    
    P.S : Karen Cushing already created issue(08-24741) and fixed
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: See summary                             *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    VALUE OF MAXSYSINDEXES.CLUSTERRULE IS INCORRECT, CAUSING
    INCORRECT VALUE FOR STORAGEPARTITION.
    

Problem conclusion

  • Already fixed via issue 08-24741
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ37911

  • Reported component name

    MAXIMO SYS CONF

  • Reported component ID

    5724R46S1

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2008-11-19

  • Closed date

    2008-11-25

  • Last modified date

    2008-11-25

  • 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

    MAXIMO SYS CONF

  • Fixed component ID

    5724R46S1

Applicable component levels

  • R710 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":"710","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
25 November 2008