DSXchange

Is it possible to use $PROJDEF in parameter set value file, I mean in the value file if I provide $PROJDEF as default value for any environment variable its not working unless I provide the actual value for it. example -- For environment variable $DATABASE with default value SEQDEV if I specify it a...

What patch would that be ? If any one know about it.

We turned OFF the auto purge, it's running fine so far. But I want to see for some more runs.

I would appreciate if I can know the reason why my previous query didn't work.

betterthanever wrote:here is how you should use open/close command in oracle/odbc stages.

Code: Select all

BEGIN
sql statement;
commit;
END;

I added the missing commands in my query and it worked great.

Thanks Betterthanever and DSGuru2B for you time and help.

DSGuru2B, I don't find any warnings of those kind, all other fatals/warnings are node_node0: Player 1 terminated unexpectedly. main_program: APT_PMsectionLeader(1, node0), player 1 - Unexpected exit status 1. main_program: Step execution finished with status = FAILED. warning --- main_program: Recei...

I have a requirement to delete some data from source before loading into target therefore I am running a delete command with where condition in oracle stage OPEN command option. It runs fine till it find data to delete but when there is no data found to delete the job aborts with errors Oracle call ...

Since your jobs are attached with jobcontrol process, it might cause the problem. We have a similar jobcontrol process and it won't allow a single warning. So if any job in the sequence get a single warning, job finished but sequence aborted due to the job warning. That will happen when you trigger...

girija wrote:As you mentioned, your Job status as "Finished (see log)" , means you have some warning in your job. Sequence might be aborted because of that, since the previous job not finished "OK". Please check this too.

Those warning are just implicit conversion warnings.

bart128792,

I checked the job is defined as "Allow Multiple instance" and it does exist since it is running when we try restarting it couple of times.

Its not that the same job aborting every time, its different jobs or some time same job with different invocation id (instance).

Yes I am using Multiple instances of a job in the sequence. But what could be the issue with that ?

Ray, when the job was started next time it was in "Finished (see log)" state therefore I believe it doesn't need to compile. Although when we compiled the main sequence it ran fine but it happened again for next run. I was searching online and found that it might be because the Auto purgin...

Its really strange but anyhow I need to implement the suggestion made by Ray to re-compile and run again. I will do that on monday and will let you guys know the result.

Thanks for your time and suggestions.

Yes with same error but for different job.

Nothing has changed. We were just trying reset the sequences and run again whenever it aborts.

As you suggested Ray we should try recompiling everything again and run.