Flashes (Alerts)
Abstract
If MAXINST was run without the -s and -t flags the STORAGEPARTITION metadata will be invalid. This causes errors during subsequent: Database Configuration, creating Interface Tables, installing add-on products, and installing a patch or test fix.
Content
If you receive any of the errors below you can be encountering this problem. You can follow the database-specific instructions below to correct the data and then rerun ConfigDB. You need to start the App Server to correct the domain value, then stop it again to rerun ConfigDB.
You see something similar to one of the following errors on Oracle:
ORA-00959: Table space 'MAXIMO' does not exist
Or
ORA-02216: Table space name expected
You see something similar to one of the following errors on SQL Server:
com.inet.tds.SQLException: Msg 1921, level 16, state 3, Line 1, SQL state 01000
[your-database-name]Invalid filegroup 'MAXIMO' specified
Or
[your-database-name]Invalid filegroup '' specified
ORACLE - Correcting the table data
Set storage partitions to the table space name by running the following statements:
UPDATE MAXTABLE SET STORAGEPARTITION = (SELECT TABLESPACE_NAME
FROM USER_TABLES WHERE TABLE_NAME = TABLENAME);
UPDATE MAXTABLECFG SET STORAGEPARTITION = (SELECT TABLESPACE_NAME
FROM USER_TABLES WHERE TABLE_NAME = TABLENAME);
COMMIT;
SQL Server - Correcting the table data
Set storage partitions to the correct filegroup name by running the following statements:
update maxtable set storagepartition = (select sysfilegroups. Groupname from dbo.sysindexes, sysobjects, sysfilegroups where dbo.sysindexes.id = sysobjects.id and sysobjects.name in (select lower(tablename) from maxtable) and sysobjects.type = 'U' and dbo.sysindexes.groupid = sysfilegroups.groupid and dbo.sysindexes.indid <= 1 )
update maxtablecfg set storagepartition = (select sysfilegroups. Groupname from dbo.sysindexes, sysobjects, sysfilegroupswhere dbo.sysindexes.id = sysobjects.id and sysobjects.name in (select lower(tablename) from maxtablecfg) and sysobjects.type = 'U' and dbo.sysindexes.groupid = sysfilegroups.groupid and dbo.sysindexes.indid <= 1)
DB2 - Correcting the table data
Set storage partitions to the table space name by running the following statements:
update maxtable set storagepartition = (select tbspace from syscat.tables
Where maxtable.tablename = tabname);
update maxtablecfg set storagepartition = (select tbspace from syscat.tables
Where maxtablecfg.tablename = tabname)";
All Databases - Updating Index metadata
The following section applies whether you are running an Oracle, SQL Server, or DB2 database.
From the Configure Database application, select Action>Rebuild Index metadata
Select Go to>Configuration>Database Configuration
Click Actions from the drop-down menu.
Click Refresh Index Tables
All Databases - Updating Storage Partitions
The following section applies whether you are running an Oracle, SQL Server, or DB2 database.
The DBSTORAGEPARTITION domain must be modified so that it lists the correct DB2 or Oracle table spaces or SQL Server filegroups.
Select Go to>Configuration>Domains
Query for the DBSTORAGEPARTITION domain.
Add a new row for each table space or filegroup that is not already listed.
Delete the rows for any listed table space or filegroup, which does not exist
Historical Number
M04739
Product Synonym
MAXIMO
Was this topic helpful?
Document Information
More support for:
IBM Maximo Asset Management
Software version:
6.0, 6.1, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 7.1, 7.1.1, 7.5, 7.6
Document number:
348107
Modified date:
25 September 2022
UID
swg21262981