DataStage ODBC connector not working properly

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
shukla_krishna
Premium Member
Premium Member
Posts: 28
Joined: Mon Apr 20, 2009 11:27 pm
Location: san antonio

DataStage ODBC connector not working properly

Post by shukla_krishna »

My job was working fine till 2 days back.
There was upgrade in the AS400 box and we started getting errors.

Our errors are mostly related to while reading data and if column has # in the name.

We get error if we read data

Select
M5HOSP,
"M5PAT#" as M5PATNO
From <>

But if we replace sql like

Select
M5HOSP,
Integer("M5PAT#") as M5PATNO
From <>

then its works with warning.

Warnings are like

APT_CombinedOperatorController,1: Invalid character(s) ([xFC]) found converting string (code point(s): [xFC][x04]C[xAB] ) from codepage UTF-8 to Unicode, substituting.
APT_CombinedOperatorController,2: Invalid character(s) ([xE2]) found converting string (code point(s): ^[xE2][x01][x02] ) from codepage UTF-8 to Unicode, substituting.
AS400_db2_ICD9PROC,0: *** glibc detected *** /opt/IBM/InformationServer/Server/PXEngine/bin/osh: munmap_chunk(): invalid pointer: 0x00000000050905f0 ***
AS400_db2_ICD9PROC,0: ======= Backtrace: =========
AS400_db2_ICD9PROC,0: /lib64/libc.so.6(cfree+0x166)[0x3d31272886]
AS400_db2_ICD9PROC,0: /opt/IBM/InformationServer/Server/DSComponents/bin/libccodbc.so(_ZN18CC_OdbcDBStatement8dbsFetchEv+0x121)[0x2aaaaaad407d]


Can some one can help.

Same table is getting read from server jobs and it works fine without change.
Krishna Shukla
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What kind of an "upgrade" was done?
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply