Hi
I am querying from SQL server database using the ODBC stage.
The query is just selecting the columns from the source table.
The columns are ID(integer) and Address(varchar9255)).
I am able to run the query at backend.
But when I run the job I am getting the following error.
Test_Address..AX_STR_select: DSD.BCIConnect call to SQLConnect returned informational message.
Attempting to Cleanup after ABORT raised in stage
Test_Address..Transformer_128
DataStage Job 1255 Phantom 3672
Program "JOB.185184415.DT.1403032172.TRANS1": Line 65, Improper data type.
Attempting to Cleanup after ABORT raised in stage Test_Address..Transformer_128
DataStage Phantom Aborting with @ABORT.CODE = 3
Please help me in finding out the problem.
DSD.BCIConnect call to SQLConnect returned ERROR
Moderators: chulett, rschirm, roy
DSD.BCIConnect call to SQLConnect returned ERROR
Thanks,
Madhavi
Madhavi
The error message says that at line 65 there is an invalid datatype. My guess is the data in the address field is somehow settlingi nto the ID column which is causing that error. Go into the ODBC stage and look at line 65 and see if that is happening. What is your target stage in this job. Try to load the data into a sequential file and see if you are able to see the data correctly in the sequential file?
IHTH
Kris
IHTH
Kris
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I would guess, given the size of the VarChar column, that SQL Server or the ODBC driver has generated the informational message referred to, alerting you to the fact that you are using a large row size. The largest row size permitted by default in the ODBC stage is 8KB; you can increase this limit by setting the MAXFETCHROWBUFF parameter in the uvodbc.config file. This may be set globally or for an individual data source name.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.