IBM Support

IV95258: MAXIMO SEARCHED ON SQL SERVER ARE ADDING EXTRA BRACES WHICH CAUSES THE SEARCH TO FAIL

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • MAXIMO SEARCHED ON SQL SERVER ARE ADDING EXTRA BRACES WHICH
    CAUSES THE SEARCH TO FAIL
    We noticed a difference in how the UI interprets some searches
    for Maximo 7.6 with SQL Server.
    In Work Order Tracking app for example, you may need to search
    for a work order number that is 6-digits long, the first 5
    digits are '12345' and the last digit is something between 0-4.
    
    In the UI, you could type this in the WONUM search box:
    12345[0-4]
    and the SQL it generates (ignoring the application-default
    other filters) is essentially:
    where wonum like '%12345[[]0-4]%'
    That is wrong.  The correct SQL generated should be :
    where wonum like '%12345[0-4]%'
    Steps to replicate :
    1- Log into Maximo 7.6 as maxadmin
    2- Go to Work Order Tracking app
    3- On the list tab type 100[0-5]  on the Work Order field
    4- Press ENTER to search
    5- You get "There are no rows to display"
    6- Click on Advanced Search menu, then Where Clause
    7- At the end of the query you will see this :
    and ((wonum like '%100[[]0-5]%'))
    8- As you can see, the Maximo search is throwing in an extra
    set of braces. The extra braces causes the search to fail.
    Let's change it to look like this :
    and ((wonum like '%100[0-5]%'))
    9- Click on Find
    10- Maximo will now show you the workorders between 1000 and
    1005
    NOTE :  This kind of issue did not happen in previous versions
    like Maximo 6.2.6.  But it happens in 7.6 with SQL Server.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users on SQLServer.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * SQL statements generated by record filtering, performed on   *
    * SQLServer databases, where the operator LIKE is followed by  *
    * a string literal containing '[' may not return the           *
    * appropriate results.                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is included in the following package:
                          | Release 7.6.0.9 of Base Services.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV95258

  • Reported component name

    ADMINISTRATION

  • Reported component ID

    5724R46A1

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-19

  • Closed date

    2017-06-30

  • Last modified date

    2017-06-30

  • 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

    ADMINISTRATION

  • Fixed component ID

    5724R46A1

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
System Related

Software version: 760

Reference #: IV95258

Modified date: 30 June 2017