Maximo SQL performance problems on Oracle

Flash (Alert)


Abstract

Oracle bug 3566843 can cause the Cost Based Optimizer to pick an inefficient index when there are multiple indexes to choose from. Oracle versions 9.2.0.1 through 9.2.0.6 and 10.1.0.1 through 10.1.0.3 are affected.

Content


This problem only affects Maximo on Oracle databases. It can impact any version of Maximo using any Oracle 9i version less than 9.2.0.7, or any Oracle 10g version less than 10.1.0.4.

Due to Oracle bug 3566843, the Cost Based Optimizer may choose a less optimal index when there are multiple indexes on columns referenced in the where clause. This is more likely to affect SQL executed on tables with a large number of indexes, such as WORKORDER.

Solution

If you are running Maximo 4.1.1 patch 4 or higher, or any version of MAXIMO 5.x, you can patch/upgrade Oracle to version 9.2.0.8.

If you are running Maximo 6 or 7, you can patch/upgrade Oracle to version 9.2.0.8 or 10.1.0.4 or 10.2.0.x.




Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli Asset Management for IT All
Systems and Asset Management IBM Maximo Asset Management Essentials All

Historical Number

M04747

Product Alias/Synonym

MAXIMO

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Asset Management

Software version:

5.2, 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

Operating system(s):

Platform Independent

Reference #:

1263111

Modified date:

2007-06-10

Translate my page

Machine Translation

Content navigation