Volatile table usage in Teraradata Connector Stage-DS 11.3
Posted: Wed Apr 22, 2015 4:11 am
Hi ,
We are going through jobs migration from Datastage 8.1 to Datastage 11.3 . But we have observed one issue in Teradata Connecitor stage behavior between these 2 versions :
As of current design ,we are using Teradata Connector stage with setting as
Access method-Bulk, Transaction Mode-ANSI,Character Set -ASCII .
We are using before sql statement and creating few volatile tables (ex craete volatile table p1_table ............) which are then referred in after sql statement .
Job was running fine with above setting in datastage v8.1 but in Datastage 11.3 ,it is failing in after sql statement stating p1_table(created in before sql statement) doesn't exist .
I am suspecting ,its something to do with sessions ,but not sure how to fix .
Request your help in resolving this issue .
We are going through jobs migration from Datastage 8.1 to Datastage 11.3 . But we have observed one issue in Teradata Connecitor stage behavior between these 2 versions :
As of current design ,we are using Teradata Connector stage with setting as
Access method-Bulk, Transaction Mode-ANSI,Character Set -ASCII .
We are using before sql statement and creating few volatile tables (ex craete volatile table p1_table ............) which are then referred in after sql statement .
Job was running fine with above setting in datastage v8.1 but in Datastage 11.3 ,it is failing in after sql statement stating p1_table(created in before sql statement) doesn't exist .
I am suspecting ,its something to do with sessions ,but not sure how to fix .
Request your help in resolving this issue .