DSXchange

What warning message are you getting from the server job? Does your sequence doing something else also like calling a routine? The error says its unable to start the next job (Do a select * from DS_JOBS where JOBNO='192' ), OR may be the other job is not having a compiled status :? (Check and confirm)

What about an update after the load, like

If we mention KEY1 and KEY2 alone as key columns in the Hashed file , then the values can be overwritten Instead of Hashed File use Universe Stage with Key1 and Key2 as keys not the date column. Select multi row lookup as checked. Once rows are looked up (more than one may be), check for the date c...

You need to create a pointer to the Hashed file so that it would have entry in the VOC file and after that you can access it using the pointer name, instead of the pathed file.

It would be possible only through a Routine. Which would handle the call to the Oracle for the sequence.

But why such a requirement

Next day we again executed the same job with userid "A". This time it executed successfully. We are not able to understand why it failed first time. Then why it successfully executed when executed with same userid secod time. One reason could be what Arndw has suggested and the other coul...

Do a Search on ETLStats. Bunch of goodies. 3) How many loaded/updated For this may be you would need to alter your job designs. You would need to have separate links for the inserts and updates(one for insert and the other for update). (Not from the same link) Or may be you would need to maintain th...

I have a solution.
I don't know whether its right way of doing or not, but it works.

I read the DS_JOBOBJECTS using a Hashed File Stage and use a transformer concate the columns there and search the string in the concated column.

Till now it has worked with 100% success.

Try it. Its fast also.

Sequence gives no error but also doens't do anything

How are you claiming it?
Have you seen the log?
Does it show anything suspicious?
Check the Server jobs called, did they run? (may be they aren't even called, because of the trigger condition?)

Can you really get the handle of the parent job, at a time if a job is running, you can't get its handle.

Even it can be without having any source, just need to put one stage variable and a constraint to the output link so that it runs atleast once.

Try it.

Put in the transformer's derivation (as a job parameter) for the column of the db where you want it finally. That's all about it.

I think dsx is a better choice, if you want to dig information related with jobs or want general modifications, but I guess it should also be possible through xml (but would be complicated, involved and slow (since the size)). Through the manager at the time of export (the export dialog box) check t...

Explicit call to DSLogFatal would abort the job. You can use it within the stage variable.

Set your transaction size to zero.