IBM Support

IZ52077: THE TABLESPACE MAXIMO DOES NOT EXIST, IT IS MISSPELLED, THE SYSTEM HAS NOT BEEN GRANTED QUOTA ON THE TABLESPACE, OR IT IS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • Having problems running config while upgrading Maximo.
    
    It appears that the upgrade does not take additional
    storagepartitions
    into account on sql server.
    Client's only file group in the ITMS database on SQL server 2005
    is PRIMARY. He had mistakenly created a second one named MAXIMO
    and later removed it. Primary is set as his default.
    
    He is getting this error as part of his
    upgrade
    process from 6.2.3 to 7.1.1.4.  On page 72 he is being told to
    run
    UpdateDb followed by configDB
    
    I am getting the error below when running the CONFIGDB on my
    TAMIT
    7.1.1.4 database.
    E:\ibm\SMP\maximo\tools\maximo>configdb
    Tue May 19 10:51:33 CDT 2009 --- Starting ----
    BMXAA6806I - Reading properties file : maximo.properties
    19 May 2009 10:51:37:172 ÝWARN¨ BMXAA6422W - The value for
    MAXPROP
    Database.SQL.
    DataFilegroupName could not be cached. The name in the
    properties file
    is not de
    fined in the MaxProp table.
    -- BMXAA6818I - RestoreFromBackup started for schema dbo,
    connected to
    database
    jdbc:inetdae7a:itms.AIPC.com:1433?database=itms&language=us_engl
    ish&nowa
    rnings=t
    rue&mars=false Tue May 19 10:51:37 CDT 2009
    -- BMXAA6818I - ConfigDB started for schema dbo, connected to
    database
    jdbc:inet
    dae7a:itms.AIPC.com:1433?database=itms&language=us_english&nowar
    nings=tr
    ue&mars=
    false Tue May 19 10:51:37 CDT 2009
    The tablespace MAXIMO does not exist, it is misspelled, the
    system has
    not been
    granted quota on the tablespace, or it is not online. Tue May 19
    10:51:38 CDT 20
    09
    -- BMXAA6820I - ConfigDB completed without errors. Tue May 19
    10:51:38
    CDT 2009
    -- BMXAA6820I - RestoreFromBackup completed without errors. Tue
    May 19
    10:51:38
    

Local fix

  • First have a look at the document at the link below:
    http://www-01.ibm.com/support/docview.wss?rs=3214&context=SS
    LKT6&amp
    ;q1=filegroup&uid=swg21262981&loc=en_US&cs=utf-8&amp
    ;lang=en
    
    It appears that the upgrade does not take additional
    storagepartitions
    into account on sql server.
    
    This document  is a complex one covering all possibilities, you
    just
    need;
    update maxtable set storagepartition='PRIMARY'
    update maxtablecfg set storagepartition='PRIMARY'
    update maxsysindexes set storagepartition='PRIMARY'
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • This is user error.  Probably there are entries in
    maxtable/maxtablecfg with an invalid tablespace.  They should
    also make sure dbstoragepartition domain is correct.
    

APAR Information

  • APAR number

    IZ52077

  • Reported component name

    MAXIMO SYS CONF

  • Reported component ID

    5724R46S1

  • Reported release

    711

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-05-26

  • Closed date

    2009-05-31

  • Last modified date

    2009-05-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

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

Document Information

Modified date:
31 May 2009