DSXchange

Does RT_BP6487 (without the .O suffix) exist? Do VOC entries for RT_BP6487 and RT_BP6487.O exist?

The job in prod is likely to have a different number. You can ascertain this number via a query against the DS_JOBS table.

Worst case, you could copy the job back from prod.

Same answer as for the other post where you posed this question.

karthikeyan M wrote:The issue is due to size of the file system might be full.

Are you sure? On what evidence? What other possibilties might exist?

Maybe someone else on the system has deleted one of the data set segment files?

It's probably just an artifact of the data browser. Are the "." characters still present if you write the timestamps into a text file?

r u able to resolve this issue. The present tense of the verb "to be" is spelled "are", not "r". The second person personal pronoun is spelled "you", not "u". Questions should be marked with terminating "?" character. DSXchange is not a mo...

g_rkrish wrote:I think the problem is with your Dataset...

Why do you think that? I see no evidence for it in the original post.

It's an environment variable. Therefore add it to the project's environment variables using the Administrator client. That having been done it will be available for loading into jobs as a parameter should you wish to do that as well.

In version 7.x only the ODBC stage has the ability to create one of these "grouped transactions".

What do you want to happen if JOB1 finishes with warnings?

1) No.
2) cat .*.adm in the project directory.

Clearing them would be dangerous - they're set for a reason. Make sure that no-one has the job open in Director log or monitor view during backup time.

@OUTROWNUM will do it if, as I already advised, the Transformer stage is executing in sequential mode.

A job is locked if it's open in Designer (obviously) but also if it's open in Log view or in Monitor view in Director. It may therefore be transiently locked by dsjob with any of the log interrogation options.

The only way to get a guaranteed unbroken sequence is to generate it using a stage executing a formula in sequential mode or to use a generator such as the Surrogate Key Generator stage.

The usual approach, when there are reserved characters in a pathname, is completely to surround the pathname in double quotes.