Hi All
When i run a job it gets aborted by flashing the below warnings.
Can anyone explain what does it mean.
Any help would be greatly appreciated.
Regards
Shiva
SJETL2CLM5..Transformer_1.DSLink4: DSD.BCIPut call to SQLExecute failed.
SQLSTATE=IM974, DBMS.CODE=0
[DataStage][SQL Client]Parameter marker text size exceeds allocated space
Shivakumar
Parameter Marker
Moderators: chulett, rschirm, roy
Hi Shiva,
I don't know exactly what that error is but I think I have read somewhere in here (not long ago) that there is a maximum length for a paramater. What do your paramaters look like? Do you supply them by hand or from a file? If it's from a file, maybe the routine that supplies them to the job doesn't work as expected. Does it still fail if your try with different parameters? (I know these sound obvious but it's a start...)
Creo
I don't know exactly what that error is but I think I have read somewhere in here (not long ago) that there is a maximum length for a paramater. What do your paramaters look like? Do you supply them by hand or from a file? If it's from a file, maybe the routine that supplies them to the job doesn't work as expected. Does it still fail if your try with different parameters? (I know these sound obvious but it's a start...)
Creo
Hi
I would like to add some more infi with the above error
SQLSTATE=IM974, DBMS.CODE=0
[DataStage][SQL Client]Parameter marker text size exceeds allocated space
SQLSTATE=22005, DBMS.CODE=-99999
[DataStage][SQL Client][ODBC][IBM][CLI Driver] CLI0112E Error in assignment. SQLSTATE=22005
SQLSTATE=58005, DBMS.CODE=-902
[DataStage][SQL Client][ODBC][IBM][CLI Driver][DB2/6000] SQL0902C A system error (reason code = "13") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005
Can anyone help to sort out this error.Any help will be greatly appreciated
Regards
Shiva
Shivakumar
I would like to add some more infi with the above error
SQLSTATE=IM974, DBMS.CODE=0
[DataStage][SQL Client]Parameter marker text size exceeds allocated space
SQLSTATE=22005, DBMS.CODE=-99999
[DataStage][SQL Client][ODBC][IBM][CLI Driver] CLI0112E Error in assignment. SQLSTATE=22005
SQLSTATE=58005, DBMS.CODE=-902
[DataStage][SQL Client][ODBC][IBM][CLI Driver][DB2/6000] SQL0902C A system error (reason code = "13") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005
Can anyone help to sort out this error.Any help will be greatly appreciated
Regards
Shiva
Shivakumar
Hi,
It seems that you're using an ODBC stage (Do you access DB2 ?). You're guess is probably right - the generated sql has to many columns or the generated sql phrase is too large (It's happens with Informix CLI stage for instance). If it's a full table select use the user-defined sql and do a 'select * from table' this can proove the limitetion else try a native stage instead of ODBC
It seems that you're using an ODBC stage (Do you access DB2 ?). You're guess is probably right - the generated sql has to many columns or the generated sql phrase is too large (It's happens with Informix CLI stage for instance). If it's a full table select use the user-defined sql and do a 'select * from table' this can proove the limitetion else try a native stage instead of ODBC
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If you have 27 columns then the generated SQL will contain 27 parameter markers.
Somewhere, somehow, in this set of markers the text provided to substitute for a parameter marker exceeds the size specified in the metadata. It would be good if the diagnostics could tell you which one but, alas, they don't.
Stage tracing may help here, particularly if the error occurs early in job processing (so that the log file isn't too large). You can inspect the actual values that were processed into and out of the active stage that is driving the ODBC or DB2 stage.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
Somewhere, somehow, in this set of markers the text provided to substitute for a parameter marker exceeds the size specified in the metadata. It would be good if the diagnostics could tell you which one but, alas, they don't.
Stage tracing may help here, particularly if the error occurs early in job processing (so that the log file isn't too large). You can inspect the actual values that were processed into and out of the active stage that is driving the ODBC or DB2 stage.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518