IV35780: ISSUE WHEN USING TWO ORACLE INSTANCES FOR MAXIMO SPATIAL CONFIGURATION

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

  • Steps to replicate in Maximo 7.5.0.3 Spatial 7.5.0.1:
    
    1 - Configure Maximo Spatial using one Oracle instance for
    Maximo and another one for ArcGIS.
    
    2 - Open the map and update the shape of an existing feature
    using Maximo Spatial and Save it.
    
    3 - Open the map again and check the change was not saved.
    

Local fix

  • No workaround has been found.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *  IBM Maximo Spatial Asset Management 7.5 users, using Oracle *
    * database and separated database instances or schemas for     *
    * Maximo and ArcGIS.                                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Changes in GIS versioned objects, from Maximo, are not saved *
    * in GIS, sometimes silently, sometimes with an error message. *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please install the latest Spatial interim fixes.  Notice     *
    * that there are manual changes that must be followed, and all *
    * synonyms to versioned GIS tables must be replaced by views   *
    * in Maximo database or schema.                                *
    ****************************************************************
    

Problem conclusion

  • The error is caused by a know Oracle problem, which happens in
    the specific model adopted in Maximo Spatial design, which in
    this case uses synonyms, views and database links. Maximo
    Spatial was modified to also work with views, instead of
    synonyms only, so the Maximo views pointing directly to GIS
    versioned views solve the updating problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV35780

  • Reported component name

    MAXIMO SPATIAL

  • Reported component ID

    5724T3900

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-23

  • Closed date

    2013-02-19

  • Last modified date

    2013-02-19

  • 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 SPATIAL

  • Fixed component ID

    5724T3900

Applicable component levels

  • R750 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Maximo Spatial Asset Management

Software version:

750

Reference #:

IV35780

Modified date:

2013-02-19

Translate my page

Machine Translation

Content navigation