JR39854: ODBC OPERATOR ABORTS WITH INVALID PRECISION VALUE CONNECTING TO MS SQL SERVER WITH NVARCHAR MORE THAN 2000 LENGTH.

IBM InfoSphere Information Server, Version 8.5 Fix Pack 2

APAR status

• Closed as program error.

Error description

• ODBC Operator write jobs connecting to MS SQL Server, with
  nvarchar in the schema which exceeds 2000 length, abort with
  invalid precision value error message
  
  DataStage job fails with the error
  
  main_program: Error loading "orchodbc": Could not load
  "orchodbc":  0509-130 Symbol resolution failed for
  /datastage/Ascential/DataStage/PXEngine/lib/liborchodbcaix3.so
  because:
   0509-136   Symbol __dl__FPv (number 284) is not exported from
       dependent module
  /datastage/Ascential/DataStage/branded_odbc/lib/libodbcinst.a(od
  bcinst.so).
   0509-022 Cannot load module .
   0509-026 System error: Cannot run a file that does not have a
  valid format.
   0509-192 Examine .loader section symbols with the
     'dump -Tv' command..
  Could not locate operator definition, wrapper, or Unix command
  for "odbcupsert"; please check that all needed libraries are
  preloaded, and check the PATH for the wrappers
  

Local fix

• No local fix. It currently works for nvarchar less then 2000
  

Problem summary

• ODBC Operator fails with invalid precision value when the schema
  contains nvarchar of more than 2000 length.
  

Problem conclusion

• With DD 5.3 drivers, the SQLBindParameter is strict in checking
  the passed arguments's validity.
  

Temporary fix

Comments

APAR Information

• 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

• R753 PSY

     UP

• R800 PSY

     UP

• R801 PSY

     UP

• R802 PSY

     UP

• R810 PSY

     UP

• R850 PSY

     UP