DSXchange

As suggested by Ray, I did a search on dsxchange as well as DeveloperWorks. I added the following in my dsenv file export TZ=ISTIMDT-5:30 (My timezone) Also added the above in the profile of the dsapi_slave Then restarted the engine Now, the server time on the director(below right corner of the wind...

We are facing an issue where all jobs in the director show wrong time in the logs. They indicate time which is one hour ahead of actual. I went to Tools - Options and checked the box to show server time. The time shown is one hour ahead I checked the time on the Unix box where the engine is installe...

arvind_ds wrote:Did you go through the link mentioned above? That was answer your question.

Sorry the link was not clear enough..Could you explain?

Is the Un-Register to be performed on Engine Machine or MetaData Machine?

Currently we have a two tier architecture with DS Engine on one machine A and metadata repository + WAS(Web Application Server) on another machine B. The user authentication is done thru machine B and jobs run on machine A The customer is planning to migrate machine B to another server with a differ...

Please post any other error messages which you see in the log. The above error messages are not complete

abhilashnair wrote:Just found that the view data works fine via ODBC Enterprise stage. Not sure why the connector is giving issues? As for checking the agent, what is the procedure ?

Any suggestions ?

Just found that the view data works fine via ODBC Enterprise stage. Not sure why the connector is giving issues? As for checking the agent, what is the procedure ?

After compiling when I tried to test connect it gave an error agent not available

while trying to view data, on ODBC connector stage, we are getting the following error.

"An exception occurred while trying to send the request to the handler.Request timed out"

The job runs fine but view data is not allowd. Any suggestions ?

We have a requirement where we need to send the number of rows updated/inserted on specific tables to users on a daily basis. There is a set of 8-10 jobs that run everyday. All of these are quite straightforward jobs having source ODBC stage, transformer and target ODBC. The target is set to be Upse...

We have a two tier topology where DataStage Metadata repository and application Server reside on System A and engine is on System B. There is only one project on System B. System B is being moved to a new box. The CPU, Ram and the IP will remain intact even on the new box. This movement is only beca...

This is happening because the lookup stage is beiong told to abort whenever it does not finds a match. As the lookup is able to find only one match and not the other it is failing

Inside Lookup stage, open properties and change the condition for lookup failure. You have to change it to continue

Re worked the job and used DB2 API stage instead of ODBC Enterprise. It worked fine...Guess something was amiss in ODBC, since the same query and same metadata was used in DB2 API as well

The only time I've seen anything remotely like this, it turned out to be a database client software bug. What does your official support provider have to say on the topic? Not gone to them yet..Trying to debug from my end. The source contains 817 rows. This error happens after 809 rows. But it has ...