IBM Support

IJ12929: UPGRADE FAILS IN SPATIAL PATCH V7600_07.CLASS

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

  • Client upgrade to Maximo 7.6.0.9 and Spatial 7.6.0.3 fails in
    Spatial patch V7600_07. V7600_07 inserts rows into table
    MAPMANAGER, but does not populate required columns
    GMAPAUTHMETHOD and ISMOBILE. Because the columns are defined as
    required, they cannot be left null, and so the upgrade fails.
    No default value is defined for either column. Following is the
    failure from client's UpdateDB log:
    
    ----------------------------------------------------------------
    ---
    Calling the script file : V7600_07 Wed Dec 05 09:59:01 CST 2018
    ----------------------------------------------------------------
    ---
    commit
    ;
    
    insert into mapmanager
    (mapmanagerid,mapname,mapprovider,description,active,plussgeomse
    rvurl,plussautocreatewofc,plussautocreatewolabel,plussautocreate
    srfc,plussautocreatesrlabel,plussautolocatewolabeltext1,plussaut
    olocatesrlabeltext1,plussautolocatesalabeltext1,plussautolocatew
    olabeltext2,plussautolocatesrlabeltext2,plussautolocatesalabelte
    xt2,plussautolocatewolabelpos,plussautolocatesrlabelpos,plussaut
    olocatesalabelpos,plussautolocatelabeltextsize,plussbing,plussbi
    ngmapskey,plussopenstreetmap,plussautolocateaslabeltext1,plussau
    tolocatelolabeltext1,plussautolocateaslabeltext2,plussautolocate
    lolabeltext2,plussautolocateaslabelpos,plussautolocatelolabelpos
    ,lengthunit,spatialgeocode,spatialroute,hasld,langcode,gmapsdist
    ancematrix,bmapsroute,bmapsdistancematrix,bmapsgeocode,spatialdi
    stancematrix,activelinearlayer) values
    (mapmanagerseq.nextval,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?
    ,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
    ;
    1001, SPATIAL, Web Adapter services TEST, 0,
    http://mkgiswebt/msdgis/rest/services/Utilities/Geometry/Geometr
    yServer, WO_POINTS, null, SR_POINTS, null, null, null, null,
    null, null, null, null, null, null, 10, 0, null, 0, null, null,
    null, null, null, null, Miles,
    http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServ
    er,
    http://route.arcgis.com/arcgis/rest/services/World/Route/NAServe
    r/Route_World, 0, EN,
    http://maps.googleapis.com/maps/api/distancematrix/json,
    http://dev.virtualearth.net/REST/v1/Routes,
    http://dev.virtualearth.net/REST/v1/Routes,
    http://dev.virtualearth.net/REST/v1/Locations,
    http://route.arcgis.com/arcgis/rest/services/World/Route/NAServe
    r/Route_World, true
    // Failed.
    
    ERROR: ORA-01400: cannot insert NULL into
    ("MAXIMO"."MAPMANAGER"."ISMOBILE")
    

Local fix

  • Alter database column definitions to include default values.
    This is only a workaround, since it is not possible to do so in
    a script.  UpdateDB does not support default values.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Maximo Spatial users                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * UPGRADE FAILS IN SPATIAL PATCH V7600_07.CLASS                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Added default values to ismobile attribute
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ12929

  • Reported component name

    MAXIMO SPATIAL

  • Reported component ID

    5724T3900

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-21

  • Closed date

    2019-04-29

  • Last modified date

    2019-04-29

  • 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

    MAXIMO SPATIAL

  • Fixed component ID

    5724T3900

Applicable component levels

  • R760 PSY

       UP

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

Document Information

Modified date:
29 April 2019