IBM Support

IV29876: BMXAA6712E- DB CONNECTION FAILED AND RECORD NOT RETRIEVED ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • PROBLEM DESCRIPTION:
    
    BMXAA6712E - The database connection failed and the record was
    not retrieved .
    Try the operation again. If you experience repeated failures,
    check the log files in the home directory or contact your system
    administrator.
    
    ENVIRONMENT:
    
    App Server  IBM WebSphere Application Server 7.0
    Version  BM Maximo Asset Management 7.5.0.2 Build 20120219-2030
    DB
    Build V7502-00
    Tivoli's process automation engine 7.5.0.2-IFIX20120706-1221
    Build
    20120219-2030 DB Build V7502-25
    WMS Data Factory 2.0.1.0 Build WMS_250_BUILD_2012_06_13_B30 DB
    Build
    V200-15
    IBM Maximo Asset Management Scheduler 7.5.0.0 Build BUILD_NUM DB
    Build
    V7501-03
    IBM Maximo Calibration 7.5.0.0 Build BUILD_NUM DB Build V7501-01
    WMS 2.6.0.0 Build WMS_260_BUILD_2012_09_24_B05 DB Build V260-05
    IBM Maximo for Oil And Gas 7.5.0.0-20120907-1143 Build
    20110418-1031 DB
    Build V7500-22 HFDB Build HF7500-00
    Server OS  Windows Server 2003 5.2 build 3790 Service Pack 2
    Server DB  Oracle 11.2 (Oracle Database 11g Enterprise Edition
    Release
    11.2.0.3.0 - 64bit Production)
    
    STEPS TO REPRODUCE:
    
    1) go to system configuration
    2)go to system config/platform configuration/system properties
    3) filter property name=mxe.db.UseSiteListInQuery
    4) modify global value=1
    5) save
    6) select action live refresh.
    Note!; If live refresh is not allowed,then change the Global
    Value and restart MXserver to apply the change.
     7) logout and login as user Sinclair
    8) go to planning condition for work (oil)
    9) try to find a record and notice the error:
    BMXAA6712E - The database connection failed and the record was
    not retrieved.
    Try the operation again. If you experience repeated failures,
    check the log files in the home directory or contact your system
    administrator
    N.B!: It works fine with Maxadmin who has access to all sites..
    ANALYSIS:
    
    This is similar to APAR #: IZ70857 / Issue(s): 10-11198  that
    was fixed for maximo 7.1.1.5 etc.
    Description: In Security Groups, if a user does not have
    authorization to access all sites, but they are given
    permission to access a few pre-defined sites, user validation
    takes a  long time.
    To enable it in the system properties mxe.db.UseSiteListInQuery
    needs to be set
    
    In Maximo 7.5.0.2 if mxe.db.UseSiteListInQuery=1 if users are
    given
    permission to access a few pre-defined sites, they will no
    longer be able to
    access or select values from Applications defined at system
    level...
    
    Checking the Logs:
    
    09 Oct 2012 13:03:28:707 [ERROR] [MXServer] [CID-UIASYNC-1071]
    BMXAA6714E - The
    data for the next record in the mboset could not be retrieved
    for the SQL query etc etc..
    java.sql.SQLSyntaxErrorException: ORA-00928: missing SELECT
    keyword
            at
    oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
            at
    oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
            at
    oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
            at
    oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
            at
    oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
            at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)
            at
    oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
            at
    oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.
    java:851)
            at
    oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleSt
    atement.java:1153)
            at
    oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleSt
    ateme
    nt.java:1267)
            at
    oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.
    java:1477)
            at
    oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleSta
    temen
    tWrapper.java:392)
            at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3025)
            at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2658)
            at psdi.mbo.MboSet.fetchMbos(MboSet.java:2615)
            at psdi.mbo.MboSet.getMbo(MboSet.java:1897)
            at
    psdi.webclient.system.beans.DataBean.getMbo(DataBean.java:4231)
            at
    psdi.webclient.system.beans.DataBean.filterrowsinner(DataBean.ja
    va:6205)
            at
    psdi.webclient.system.beans.DataBean.filterrows(DataBean.java:61
    76)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
            at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:39)
            at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    Acces
    sorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at
    psdi.webclient.system.session.AsyncProcess.run(AsyncProcess.java
    :144)
            at java.lang.Thread.run(Thread.java:619)
    09 Oct 2012 13:03:28:707 [ERROR] [MXServer] [CID-UIASYNC-1071]
    BMXAA6712E - The
    database connection failed and the record was not retrieved. Try
    the operation a
    gain. If you experience repeated failures, check the log files
    in the home direc
    tory or contact your system administrator.
    09 Oct 2012 13:03:28:707 [ERROR] [MXServer] [CID-UIASYNC-1071]
    BMXAA6713E - The
    MBO fetch operation failed in the mboset with the SQL error code
    928.  etc ..
    java.sql.SQLSyntaxErrorException: ORA-00928: missing SELECT
    keyword etc etc..
    
    Needs to be fixed again for Maximo 7502
    

Local fix

  • n/a
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • This problem is not reproducible in 7.5.0.4
    

APAR Information

  • APAR number

    IV29876

  • Reported component name

    MAXIMO SYSTEMS

  • Reported component ID

    5724R46AV

  • Reported release

    750

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-10-10

  • Closed date

    2012-11-06

  • Last modified date

    2012-11-06

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 November 2012