DSXchange

There were two instances (not an exhaustive list. Check similar topics in this forum) in which the jobs compile, however they show as Not Compiled in Director 1. We are using User defined admin env variables so that they can be changed when the jobs are moved across environments. We are also includi...

I came across this error and found where the problem is. I used a parmeter set variable directly in the job without including the paramter set itself in the job parameters (job properties). While this may be only one of many reasons why this could occur, I am posting it here so that it is beneficial...

You are right. I did not use RAISE_APPLICATION_ERROR. I am a Oracle novice. Forgive my ignorance. Looking back at your posts, I feel I should have paid more attention to the string in upper case. Thanks for your patience.

In the stored procedure, when the exception handling is removed, DataStage aborts with error ORACLE_STAGE: The following SQL statement failed: call sp_trunc_table('test1623'). ORACLE_STAGE: The OCI function executeDirect returned status -1. Error code: 942, Error message: ORA-00942: table or view do...

We are using DataStage 8.7.0.1. Thank you for your inputs.

Thanks Craig. I just went by the description in Oracle connector stage "Fail on error for Before SQL Statement - Select Yes to stop the job if the Before SQL statement fails". I modified the SP to raise an exception and tested in SQL Developer. Following is the (custom) exception thrown no...

Yes, the above command/error is from sql developer client with the user id (both DataSage and Oracle SQL Developer)

Command:
exec sp_trunc_table('Ora 00942');

Result:
"ORA-00942: table or view does not exist"

Job design Sequential file - Transformer - Oracle Connector stage Oracle table needs to be truncated but the load userid do not have permissions to truncate and load the table. So the DBAs suggested an alternative approach to use a stored procedure that they will grant acess to and use it to truncat...

This issue is resolved. Everything was successful from DataStage. Because of previous failures (we were still setting up the RFC Connection when these failures occurred), SAP was still waiting on previous requests to be completed. They reset SAP load and it was all successful. Thank you for viewing ...

Hi, Here is the job design (Say Job A) Seq File -> Lookup with a database -> Transformer -> SAP BW Load Type of SAP BW Load is "Pull". So it was started from SAP and then DataStage job completed successfully, the status is Finshed. However in SAP, the job does not complete but keeps runnin...