IBM Support

IV73662: ATTRIBUTES STARTING WITH ASC GENERATING SQL ERROR CODE 207 WHEN TRYING ASCENDING SORT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • We have hundreds of user defined attributes that all begin with
    ASC. You cannot sort on these attributes when they are added to
    List Screens and to LookUp tables.  The ascending sort works
    but when you select the descending sort the SQL error code 207
    occurs and you must reload the records (All Records) to
    continue working in the application. The Maximo code is
    renaming the attribute in the order by clause.  So for example
    if you have an attribute named asctesta, the order by clause
    for a descending sort is order by desctesta desc.
    [5/22/15 15:49:24:271 EDT] 0000012b SystemOut     O 22 May 2015
    15:49:24:271 [ERROR] [MXServer] [] BMXAA6713E - The MBO fetch
    operation failed in the mboset with the SQL error code 207. The
    record could not be retrieved from the database. See the log
    file for more details about the error.
    com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column
    name 'desctesta'.
    STEPS TO REPLICATE:
    1. Go To Database Configuration
    2. Filter and Select the INVUSE object
    3. Select the Attributes Tab
    4. Create a new attribute
    5. Perform a Database Configuration
    6. Go To Application Designer
    7. Select the INVUSAGE application
    8. Add the ASCTESTA attribute to the List Screen
    9. Go To -> Inventory -> Inventory Usage
    10. Fill up the List Screen with records
    11. Select the Sort icon on the ASCTESTA attribute
    12. The ascending sort will work
    13. Select the Sort icon again to sort descending
    14. The Error will occur.
    BMXAA6713E - The MBO fetch
    operation failed in the mboset with the SQL error code 207. The
    record could not be retrieved from the database. See the log
    file for more details about the error.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Maximo Users                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Attributes starting with asc generating sql error code 207   *
    * when trying ascending sort.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to latest release                                    *
    ****************************************************************
    We have hundreds of user defined attributes that all begin with
    ASC. You cannot sort on these attributes when they are added to
    List Screens and to LookUp tables.  The ascending sort works but
    when you select the descending sort the SQL error code 207
    occurs and you must reload the records (All Records) to continue
    working in the application. The Maximo code is renaming the
    attribute in the order by clause.  So for example if you have an
    attribute named asctesta, the order by clause for a descending
    sort is order by desctesta desc.
    Ý5/22/15 15:49:24:271 EDT¨ 0000012b SystemOut     O 22 May 2015
    15:49:24:271 ÝERROR¨ ÝMXServer¨ ݨ BMXAA6713E - The MBO fetch
    operation failed in the mboset with the SQL error code 207. The
    record could not be retrieved from the database. See the log
    file for more details about the error.
    com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column
    name 'desctesta'.
    
    STEPS TO REPLICATE:
    1. Go To Database Configuration
    2. Filter and Select the INVUSE object
    3. Select the Attributes Tab
    4. Create a new attribute: ASCTESTA
    5. Perform a Database Configuration
    6. Go To Application Designer
    7. Select the INVUSAGE application
    8. Add the ASCTESTA attribute to the List Screen
    9. Go To -> Inventory -> Inventory Usage
    10. Fill up the List Screen with records
    11. Select the Sort icon on the ASCTESTA attribute
    12. The ascending sort will work
    13. Select the Sort icon again to sort descending
    14. The Error will occur.
    BMXAA6713E - The MBO fetch operation failed in the mboset with
    the SQL error code 207. The record could not be retrieved from
    the database. See the log file for more details about the error.
    

Problem conclusion

  • Able to sort attributes starting with ASC.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Fix Pack Release 7.5.0.9 TPAE
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV73662

  • Reported component name

    ADMIN & SECURIT

  • Reported component ID

    TIVOADMIN

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-28

  • Closed date

    2015-06-03

  • Last modified date

    2015-06-03

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

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

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    ADMIN & SECURIT

  • Fixed component ID

    TIVOADMIN

Applicable component levels

  • R750 PSY

       UP

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

Document Information

Modified date:
03 June 2015