IBM Support

PK54555: "ORA-00936 : MISSING EXPRESSION" APPEARS ONLY WHEN JAPANESE CHARACTERS INCLUDED IN A QUERY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On DBLOOKUP statement, if Japanese characters are used in the
    query, the client receives the ORA-00936 error message
    indicating missing expression.
    

Local fix

  • none
    
    WTXCQ  WTX00001199
    
    CH     87140,999,760
    

Problem summary

  • When Japanese characters are included in a DB adapter query, the
    Oracle error message, "ORA-00936 : missing expression", appears.
    
    This was corrected by a previous fix to the type tree saving
    process.  The save for a type tree failed to flag it as an
    International tree. This meant that the mmc would not be flagged
    as Japanese, which would mean that the Native code page was
    ASCII not SJIS.
    
    When a DBLOOKUP is executed, non-Native strings are converted to
    Native.  Therefore, the SJIS characters were misconverted to
    ASCII, which caused the DBLOOKUP to fail.
    
    As a fix, the code page of the O/S is checked before saving a
    type tree.  If the code page is 932, then the map is saved as an
    International map and therefore the Native code page becomes
    SJIS, which in turn resolves the issue.
    

Problem conclusion

  • When Japanese characters are included in a DB adapter query, the
    Oracle error message, "ORA-00936 : missing expression", appears.
    
    This was corrected by a previous fix to the type tree saving
    process.  The save for a type tree failed to flag it as an
    International tree. This meant that the mmc would not be flagged
    as Japanese, which would mean that the Native code page was
    ASCII not SJIS.
    
    When a DBLOOKUP is executed, non-Native strings are converted to
    Native.  Therefore, the SJIS characters were misconverted to
    ASCII, which caused the DBLOOKUP to fail.
    
    As a fix, the code page of the O/S is checked before saving a
    type tree.  If the code page is 932, then the map is saved as an
    International map and therefore the Native code page becomes
    SJIS, which in turn resolves the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK54555

  • Reported component name

    WSTX

  • Reported component ID

    5724M4000

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-10-11

  • Closed date

    2008-04-14

  • Last modified date

    2008-04-14

  • 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

    WSTX

  • Fixed component ID

    5724M4000

Applicable component levels

  • R810 PSY

       UP

  • R820 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
14 April 2008