DSXchange

are you referencing the db2 profile in your dsenv file?

Isn't that more of an oracle question than a Datastage. In Datastage we have Surrogate Key generator to perform the similar functionality.

That might be the reason. Is the staging database available. Give you DBA a call and ask him what that particular thread (from your id) is doing at that staging table. If he doesnt have a definate answer, ask him to kill the thread, which sends back a message to datastage of "connection not availabl...

As i mentioned. You need to do this after that particular job has finished. You can use dsjob -logsum -type WARNING PROJECTNAME JOBNAME All of this is listed in Server Job Developer's Guide in dsbooks. If you want to code it in a routine, or even in the derivation in the transformer, look at the DSG...

What is the sub job doing, besides validations. It loading into some database ?

If there is no pre prcessing or post processing done in the job (via before/after subroutines) then i think thats a sign right there that the job is not moving forward. How many blue links are there, how stages have finsihed ? SO the last message in the log file was posted on 5:40 am. When did you s...

Use the update action "replace existing rows completly". Define all the keys properly as it supplies that key as the where predicate for the delete. Read into that update action, or as Anupam mentioned, look at the sql.

More than that, look at the log file of that job. That will tell you whats going on with the job. If all is green, then its the job itself, too many functions in one job, record size being really huge, all of that takes a toll on the performance.

For that you have to code accordingly. Like a batch script. Even then you wont be able to get warning message for each and every row. That information is present in the log files which is getting filled during the exection of the job, so there is no way you can get that info inside that same job. Af...

Check thispost out. It has a script in which these error codes are handled. This should be of some help.

Here are my views - Stop (manualy) all the jobs in run state Two contradictory statements, automatic and manually. Hmm, dont know what to say. And by the way, stopping jobs that are running without any specific reason is not a very good idea. These jobs could be accessing a database and by passing a...

how are you giving the path name.
Dont give the drive name thats mapped. Give the complete name of the server.
For eg:
If //myserver is mapped to drive J then dont give drive J , give //myserver.

Maybe you are not specifying one of the properties correctly. Did you specify 'Fixed Width Columns' to Yes. Try sending the data in Binary instead of Ascii. Also increase your buffer length a little bit. Play around with these options. Go through the FTP stage in dsbooks. And btw, my name is not chu...

Ok then try to ftp it manually from command prompt? See if that works

Sure, get a snapshot of the table before deleting and loading the new data. Then your comparison can be done.