IBM Support

JR50886: GENERATED DB SCRIPTS FOR ORACLE THROW SP2-0027: INPUT IS TOO LONG (>2499 CHARACTERS) - LINE IGNORED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you run the following command to generate the Oracle
    database scripts for IBM Process Server and IBM Process Center,
    the resulting script contains two SQL commands that do not
    execute without intervention:
    
    >> BPMConfig.sh -create -sqlfiles <properties file> -outputDir
    <output directory>
    
    The views that fail to be created are:  TASK and TASK_TEMPL. And
    you observe the following error:
    
    Error from SQL to create <SCHEMA_NAME>.TASK SP2-0027: Input is
    too long (> 2499 characters) - line ignored
    FROM <SCHEMA_NAME>.TASK_INSTANCE_T*
    ERROR at line 2:
    ORA-00928: missing SELECT keyword
    Error from SQL to create <SCHEMA_NAME>.TASK_TEMPL
    SP2-0027: Input is too long (> 2499 characters) - line ignored
    FROM <SCHEMA_NAME>.TASK_TEMPLATE_T LEFT JOIN
    <SCHEMA_NAME>.PC_VERSION_TEMPLATE_T ON (<SCHEMA_NAME>.
    PC_VERSION_TEMPLATE_T.CONTAINMENT_CONTEXT_ID =
    <SCHEMA_NAME>.TASK_TEMPLATE_T.TKTID)
    *
     ERROR at line 2:
    ORA-00928: missing SELECT keyword
    Statement from the dbscript which is too long
    

Local fix

  • Manually modify the generated database script by adding line
    breaks at appropriate positions in the SQL commands that fail to
    execute.
    

Problem summary

  • The issue happens when using long database schema names. The
    database schema name is replaced  in the generated script. As a
    result,  some SQL commands are too long to be entirely read by
    the Oracle file processor.
    

Problem conclusion

  • A fix is available for IBM BPM 8.5.0.1 that generates additional
    line breaks inside the SQL statement so that the Oracle file
    processor can read the entire statement.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR50886:
    
    1.Select IBM Business Process Manager with your edition from the
      product selector, the installed version to the fix pack level,
      and your platform, and then click Continue.
    
    2.Select APAR or SPR, enter JR50886 , and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR50886

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-25

  • Closed date

    2014-09-17

  • Last modified date

    2014-09-17

  • 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 ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 September 2014