IJ24576: WHEN CREATING A NEW OBJECT, THE DEFAULT INDEX MAXIMO CREATES IS CREATED ON THE MAXIMO DATA TABLESPACE NOT THE INDEX TABLESPACE

APAR status

• Closed as program error.

Error description

• When creating a new Object, the default index maximo creates is
  created on the maximo data tablespace not the Index
  tablespace
  
  Note: This only seems to be an issue with
  Oracle
  
  STEPS TO REPRODUCE:
  
  On a 7611 with Oracle DB.
  Ensure
  MAXVAR MAXINSTINDEXPART is set to the name of the Index
  partition
  
  1. Go to Database Configuration and create a new
  Custom Object "TEST", Save.
  2. Check Indexes tab to update the
  default index on "TESTID" but there is no index available to
  update unless DB config is done.
  3. Do DB config, now default
  index is available and showing on the Indexes tab.
  
  RESULTS:
  Go
  To index "TEST_NDX1" and see that the storage Partition is not
  the index partition. Also note that this cannot be changed as
  it's readonly.
  
  EXPECTED RESULTS:
  Maximo should create the
  index on the defined Index partition
  
  PRODUCT VERSION:
  TPAE
  7.6.1.1
  

Local fix

• create the index yourself and pick the index partition or,
  after the fact, you have to move the index directly in the
  database
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * WHEN CREATING A NEW OBJECT, THE DEFAULT INDEX MAXIMO CREATES *
  * IS CREATED ON THE MAXIMO DATA TABLESPACE NOT THE INDEX       *
  * TABLESPACE                                                   *
  ****************************************************************
  STEPS TO REPRODUCE:
  Use Maximo on Oracle. This issue does not occur with db2.
  Ensure MAXVAR MAXINSTINDEXPART is set to the name of the Index
  partition.
  1 Go to Database Configuration and create a new table "TEST",
  Save.
  2 Do DB config so that table "TEST" and its default index on
  TESTID get created.
  3 Go to the Indexes tab and note that the default has been
  created.
  RESULTS:
  The index has been created on the default table storage
  partition, not
  the index partition specified by MAXVAR MAXINSTINDEXPART.
  EXPECTED RESULTS:
  Maximo should create the index on the storage partition
  specified by the MAXVAR MAXINSTINDEXPART.
  

Problem conclusion

• The fix for this APAR will be contained in a future release.
  

Temporary fix

Comments

APAR Information

• 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

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels