IBM Support

IJ31962: NOT ABLE TO SEARCH IN COMMUNICATION LOGS

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

  • ERROR DESCRIPTION:
    Not able to search in communication
    logs
    
    PROBLEM:
    Get error when we try to filter communication
    logs of any escalation.
    
    PERFORMANCE ISSUE:
    No
    
    STEPS TO
    REPRODUCE:
    1- Go to Logging application;
    2- Search for: sql;
    3-
    Change the log level to INFO;
    4- Apply Setting and save it;
    5-
    Go to Escalations application;
    6- Search any escalation;
    7-
    Open the Communication Logs;
    8- Click in Filter and add any ID
    on To field.
    Note that this error will appears "BMXAA6713E -
    The MBO fetch operation failed in the mboset with the SQL error
    code 8116. The record could not be retrieved from the database.
    See the log file for more details about the error."
    
    [1/15/21
    10:26:52:403 EST] 00168b01 SystemOut O 15 Jan 2021 10:26:52:402
    [INFO] [MAXIMOc1] [CID-UIASYNC-49278] Correlation
    started.
    [1/15/21 10:26:52:407 EST] 00168b01 SystemOut O 15 Jan
    2021 10:26:52:406 [ERROR] [MAXIMOc1] [CID-UIASYNC-49278]
    BMXAA6714E - The data for the next record in the mboset could
    not be retrieved for the SQL query select * from esccommlog
    where ((upper(sendto) like '%lmedeiro%')) and (exists ( select
    1 from escalation where escalation = 'INVAPPR' and uniqueid =
    escalationid and ownertable= 'INVOICE' ) or exists ( select 1
    from escalation where escalation = 'INVAPPR' and uniqueid =
    escalationid and (ownertable in (select value from
    synonymdomain where domainid in ('TKCLASS', 'WOCLASS') and
    maxvalue= 'INVOICE' ))) or exists ( select 1 from escalation
    where escalation = 'INVAPPR' and uniqueid = escalationid and
    objectname = 'WOACTIVITY')) order by createdate OPTION (FAST
    1000) . See the log file for more details about the
    error.
    com.microsoft.sqlserver.jdbc.SQLServerException:
    Argument data type text is invalid for argument 1 of upper
    function.
    	at com.microsoft.sqlserver.jdbc.SQLServerException.ma
    keFromDatabaseError(SQLServerException.java:217)
    	at com.microso
    ft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStat
    ement.java:1655)
    	at com.microsoft.sqlserver.jdbc.SQLServerState
    ment.doExecuteCursored(SQLServerStatement.java:2114)
    	at com.mic
    rosoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLS
    erverStatement.java:859)
    	at com.microsoft.sqlserver.jdbc.SQLSer
    verStatement$StmtExecCmd.doExecute(SQLServerStatement.java:778)
    
    	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.jav
    a:7505)
    	at com.microsoft.sqlserver.jdbc.SQLServerConnection.exe
    cuteCommand(SQLServerConnection.java:2445)
    	at com.microsoft.sql
    server.jdbc.SQLServerStatement.executeCommand(SQLServerStatement
    .java:191)
    	at com.microsoft.sqlserver.jdbc.SQLServerStatement.e
    xecuteStatement(SQLServerStatement.java:166)
    	at com.microsoft.s
    qlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement
    .java:677)
    	at
    psdi.mbo.MboSet.getNextRecordData(MboSet.java:3333)
    	at
    psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2941)
    	at
    psdi.mbo.MboSet.fetchMbos(MboSet.java:2898)
    	at
    psdi.mbo.MboSet.getMbo(MboSet.java:2114)
    	at psdi.webclient.syst
    em.beans.DataBean.getMbo(DataBean.java:4382)
    	at psdi.webclient.
    system.beans.DataBean.filterrowsinner(DataBean.java:6450)
    	at ps
    di.webclient.system.beans.DataBean.filterrows(DataBean.java:6421
    )
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMe
    thodAccessorImpl.java:90)
    	at sun.reflect.DelegatingMethodAccess
    orImpl.invoke(DelegatingMethodAccessorImpl.java:55)
    	at
    java.lang.reflect.Method.invoke(Method.java:508)
    	at psdi.webcli
    ent.system.session.AsyncProcess.run(AsyncProcess.java:172)
    	at
    java.lang.Thread.run(Thread.java:811)
    [1/15/21 10:26:52:407
    EST] 00168b01 SystemOut O 15 Jan 2021 10:26:52:407 [ERROR]
    [MAXIMOc1] [CID-UIASYNC-49278] BMXAA6713E - The MBO fetch
    operation failed in the mboset with the SQL error code 8116.
    The record could not be retrieved from the database. See the
    log file for more details about the
    error.
    com.microsoft.sqlserver.jdbc.SQLServerException:
    Argument data type text is invalid for argument 1 of upper
    function.
    	at com.microsoft.sqlserver.jdbc.SQLServerException.ma
    keFromDatabaseError(SQLServerException.java:217)
    	at com.microso
    ft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStat
    ement.java:1655)
    	at com.microsoft.sqlserver.jdbc.SQLServerState
    ment.doExecuteCursored(SQLServerStatement.java:2114)
    	at com.mic
    rosoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLS
    erverStatement.java:859)
    	at com.microsoft.sqlserver.jdbc.SQLSer
    verStatement$StmtExecCmd.doExecute(SQLServerStatement.java:778)
    
    	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.jav
    a:7505)
    	at com.microsoft.sqlserver.jdbc.SQLServerConnection.exe
    cuteCommand(SQLServerConnection.java:2445)
    	at com.microsoft.sql
    server.jdbc.SQLServerStatement.executeCommand(SQLServerStatement
    .java:191)
    	at com.microsoft.sqlserver.jdbc.SQLServerStatement.e
    xecuteStatement(SQLServerStatement.java:166)
    	at com.microsoft.s
    qlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement
    .java:677)
    	at
    psdi.mbo.MboSet.getNextRecordData(MboSet.java:3333)
    	at
    psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2941)
    	at
    psdi.mbo.MboSet.fetchMbos(MboSet.java:2898)
    	at
    psdi.mbo.MboSet.getMbo(MboSet.java:2114)
    	at psdi.webclient.syst
    em.beans.DataBean.getMbo(DataBean.java:4382)
    	at psdi.webclient.
    system.beans.DataBean.filterrowsinner(DataBean.java:6450)
    	at ps
    di.webclient.system.beans.DataBean.filterrows(DataBean.java:6421
    )
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMe
    thodAccessorImpl.java:90)
    	at sun.reflect.DelegatingMethodAccess
    orImpl.invoke(DelegatingMethodAccessorImpl.java:55)
    	at
    java.lang.reflect.Method.invoke(Method.java:508)
    	at psdi.webcli
    ent.system.session.AsyncProcess.run(AsyncProcess.java:172)
    	at
    java.lang.Thread.run(Thread.java:811)
    [1/15/21 10:26:52:408
    EST] 00168b01 SystemOut O 15 Jan 2021 10:26:52:408 [INFO]
    [MAXIMOc1] [CID-UIASYNC-49278] Correlated data: BEGIN
    UISessionId:14 UIClientIP:9.211.99.105 UserId:maxadmin
    AppName:escalation ElapsedTime:6 ms END
    
    CURRENT ERRONEOUS
    RESULT:
    BMXAA6713E - The MBO fetch operation failed in the
    mboset with the SQL error code 8116. The record could not be
    retrieved from the database. See the log file for more details
    about the error."
    
    EXPECTED RESULT:
    Be able to filter the log
    from any escalation
    
    ENVIRONMENT (SYSTEM INFO):
    
    App Server IBM
    WebSphere Application Server 9.0.0.7
     Version
    Tivoli's
    process automation engine 7.6.1.1-IFIX20200324-1612 Build
    20190514-1348 DB Build V7611-365 HFDB Build HF7611-06
    IBM
    Maximo Asset Management Work Centers 7.6.0.4 Build $build$ DB
    Build V7604-119
    IBM Tpae Integration Framework 7.6.1.1 Build
    20190419-2330 DB Build V7611-01
    IBM Maximo Spatial Asset
    Management 7.6.0.5-20200330-1230 Build 20190522-1410 DB Build
    V7605-09 HFDB Build HF7605-07
    IBM Maximo Asset Management
    7.6.1.1 Build 20190514-1348 DB Build V7611-01
    IoT Connection
    Utility 7.6.0.2 Build 20190426-2206 DB Build V7602-07
    Server
    OS Windows Server 2016 10.0
    Server DB Microsoft SQL Server
    13.0 (13.00.4466)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * NOT ABLE TO SEARCH IN COMMUNICATION LOGS                     *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 7.6.1.3 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ31962

  • Reported component name

    MAXIMO SYSTEMS

  • Reported component ID

    5724R46AV

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-05

  • Closed date

    2021-07-22

  • Last modified date

    2021-07-22

  • 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

    MAXIMO SYSTEMS

  • Fixed component ID

    5724R46AV

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
23 July 2021