IBM Support

JR60274: A BAD SQL GRAMMAR EXCEPTION OCCURS WHEN AN ATTEMPT IS MADE TO CHANGE A SNAPSHOT

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.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • A SQL query might fail with a bad SQL grammar exception and the
    following exception might be logged in the SystemOut.log file:
    
    Caused by: org.springframework.jdbc.BadSqlGrammarException:
    PreparedStatementCallback; bad SQL grammar [select
    t0.USER_ID,t0.USER_NAME,t0.FULL_NAME,t0.PROVIDER from
    LSW_USR_XREF t0 where USER_NAME in (?,?,?,?,?,?,?,?,?,?,?,...)
    order by USER_ID]; nested exception is
    com.microsoft.sqlserver.jdbc.SQLServerException: The incoming
    request has too many parameters. The server supports a maximum
    of 2100 parameters. Reduce the number of parameters and resend
    the request.
     at
    org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.
    translate(SQLStateSQLExceptionTranslator.java:111)
     at
    org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTransla
    tor.translate(SQLErrorCodeSQLExceptionTranslator.java:322)
     at
    org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.
    java:607)
     at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:641)
     at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:670)
     at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:678)
     at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:710)
     at
    org.springframework.jdbc.core.simple.SimpleJdbcTemplate.query(Si
    mpleJdbcTemplate.java:187)
     at
    com.lombardisoftware.server.ejb.persistence.dao.UnversionedPODAO
    .executeQuery(UnversionedPODAO.java:259)
     at
    com.lombardisoftware.server.ejb.persistence.dao.UnversionedPODAO
    .findOrdered(UnversionedPODAO.java:248)
     at
    com.lombardisoftware.server.ejb.persistence.dao.UnversionedPODAO
    .findOrdered(UnversionedPODAO.java:233)
    
    Note: There is no specific scenario as long as sql query is
    being executed by UnversionedPODAO class.
    

Local fix

Problem summary

  • No additional information is available.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM)
    IBM Business Automation Workflow
    

Problem conclusion

  • A fix that allows more than the previous maximum of 2100
    parameters will be available in a future release of IBM Business
     Automation Workflow.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR60274

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-11-09

  • Closed date

    2018-11-29

  • Last modified date

    2018-11-29

  • 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

    BPM

  • Fixed component ID

    5737A5700

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFPJS","label":"IBM Business Process Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 September 2022