The DataDirect ODBC Driver Warning
Posted: Tue Sep 16, 2003 7:22 am
I have a job using DataStage Veriosn 6 on a Unix system connecting to Oracle.
The job connects to an oracle database through OCI stages and also connects to another database through ODBC via a Datastage Basic function.
The initialisation files all appear set up correctly but when I run the job I get a warning message for the job stating '[DataDirect][ODBC Oracle driver]The DataDirect ODBC driver you are attempting to access has been provided to you by AscentialSoftware for exclusive use with DataStage. You are not licensed to use this driver with any application other than DataStage.' I am not using the driver that it is complains about.
We know about the line within the configuration file that Datastage inserts if the above driver is used and we remove it.
Similar ODBC code to that in the funtion, if used as job control, works without getting the warning errors.
Unfortuantely, I need to use it within the funtion because of the additional funtionality needed.
Is there a way that the ODBC warning can be avoided/suppressed without suppressing 'valid' warnings that would come from the Datastage Basic function?
Thanks, in anticpation,
Paul
The job connects to an oracle database through OCI stages and also connects to another database through ODBC via a Datastage Basic function.
The initialisation files all appear set up correctly but when I run the job I get a warning message for the job stating '[DataDirect][ODBC Oracle driver]The DataDirect ODBC driver you are attempting to access has been provided to you by AscentialSoftware for exclusive use with DataStage. You are not licensed to use this driver with any application other than DataStage.' I am not using the driver that it is complains about.
We know about the line within the configuration file that Datastage inserts if the above driver is used and we remove it.
Similar ODBC code to that in the funtion, if used as job control, works without getting the warning errors.
Unfortuantely, I need to use it within the funtion because of the additional funtionality needed.
Is there a way that the ODBC warning can be avoided/suppressed without suppressing 'valid' warnings that would come from the Datastage Basic function?
Thanks, in anticpation,
Paul