DSXchange

Job design: Reads data from a dataset, a transformer stage - the input of which is hash partitioned based on the target primary keys, add couple of more columns, with hard-coded values in transformer stage and finally truncate and insert into the target sql server table, using DRS connector stage. D...

Should i validate the Teradata client installation and configuration, how would i do it? What are items to be cross -verified? and what are the configurations required for setting up Teradata connector stage and ODBC. Lets take Teradata connector stage first: my dsenv config is as follows: TD64_CONN...

Yes Ray; The teradata client and utilities were installed by the Teradata DBA in the server

Can the experts please guide me in this issue. Thanks. I went through the post, and didnt get a clear picture as what should be configured exactly for Teradata connector stage and ODBC to Teradata to work.




Thanks
Nirmal

it seems that the job exe, we are executing in QA, got corrupted. we reimported the exe, and the job ran successfully. closing this issue. Thanks

Can the experts please assist me with this issue. Thanks

when i tried testing the ODBC connection through the example program, i got the following error: $ ./example ./example DataDirect Technologies, Inc. ODBC Example Application. Enter the data source name : **** Enter the user name : ***** Enter the password : **** SQLSTATE = 28000 NATIVE ERROR = 0 MSG...

we are able to successfully execute the stored procedure at the backend in the database

How do you know that the problem is in the Stored Procedure stage? Please post any error message that verifies this. i inferred from the following log entry that, only during stored procedure call, the STP stage is terminating abnormally. "Abnormal termination of stage JobOraCampExtract..PR_DE...

abnormal termination of STP stage in happening in our server job. Job design is a source sequential file, which has the values to be passed as parameter inputs to the stored procedure, being called in the STP stage. the sequential file is directly linked to the STP stage. Following is the extended l...

Thanks Andy for the useful information shared. Just one more advise required.

Will it be a clean restart of the Information Server, if we dont kill the Logging agents process and restarting the application. What will be the impact or consequence

Thanks Andy, it was the first problem, where DSParams file did not have proper file permission with the ID I was using.

Am getting the error, even when i open the datastage administrator using suite admin ID, and just click "OK", without making any changes at the project level.
This issue is suddenly creeping up.
Also, am getting the DSR.ADMIN Failed to write to DSParams file error.

I performed it immediately after logging into the Administrator.

Thanks for the reply.

We start the node agents as non-root user. Even then won't the logging agent stop properly??