IBM Support

JR61217: ORACLE CONNECTOR SHOULD HONOR NLS_LANG WHEN RCP IS SET.

Fixes are available

IBM InfoSphere Information Server, Version 11.7.1.1 (Fix Pack 1)
IBM InfoSphere Information Server, Version 11.7.1.1 for AIX
IBM InfoSphere Information Server, Version 11.7.1.1 for Windows
IBM InfoSphere Information Server, Version 11.7.1.1 for Linux

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Oracle Connector should be modified to honor the NLS_LANG
setting when using Runtime Column Propagation (RCP) and when a
new environment variable CC_ORA_HONOR_NLS_LANG_WHEN_RCP is
set to TRUE to describe the metadata.

Local fix

  • 



Problem summary


    

  • A DataStage job wants to process rows in RCP mode between Oracle
 AL32UTF8 DB and Oracle WE8ISO8859P15. The issue is that for
CHAR semantics (i.e., VARCHAR (n CHAR)), whatever the NLS
parameters are, ustring are bound for those data types resulting
 in creation of NVARCHAR on target. For example, the situation
is undesirable for certain customers when NLS_LANG is set to
ISO8859-15 and Oracle database is WE8ISO8859P15.

    



Problem conclusion


    

  • A patch was built that allows the Oracle connector to honor
NLS_LANG when RCP (Runtime Column Propagation) is set. To obtain
 the desired behavior, the env var
CC_ORA_HONOR_NLS_LANG_FOR_RCP=TRUE must be set in the job or
project and NLS_LANG must have a valid value. This will allow
Oracle Connector to describe the columns created with CHAR
semantics as strings instead of ustrings when NLS_LANG is set to
 single byte database charset. Care must be taken since use of
this feathre can lead to data corruption when a multi-byte UTF8
character cannot be represented in the ISO charset.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    JR61217
    • 

  • Reported component name
    WIS DATASTAGE
    • 

  • Reported component ID
    5724Q36DS
    • 

  • Reported release
    B31
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2019-06-18
    • 

  • Closed date
    2019-08-27
    • 

  • Last modified date
    2020-01-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
    WIS DATASTAGE
    • 

  • Fixed component ID
    5724Q36DS
    • 



Applicable component levels


    

  • RB30  PSY
       UP
    • 

  • RB31  PSY
       UP
    • 

  • RB50  PSY
       UP
    • 

  • RB70  PSY
       UP
    • 

  • RB71  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.3","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            15 October 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback