DSXchange

Can't be done in one transformer. You're going to need to arrange to make two passes thru the data and track the number of rejects - then reprocess it with those results in mind.

You need to get everyone out and reindex the project. Lots of posts on the subject, search for things like REINDEX or find the option under your DS.TOOLS menu.

I recall this conversation but nothing specific to your question... and I couldn't find anything either.

It means you can 'RTI enable' Server, TX or PX jobs but not Sequence jobs.

Error -12 is DSJE_BADNAME /* Job name badly formed */ - check to make sure it exists as you've specified it, down to the casing of the letters.

Well... processed X rows just means they were sent to the target database, it doesn't mean any were actually 'accepted' by it.

What does your job's log show? Warnings up the Wazoo?

What happens if you hang a reject link off the transformer?

Known issue. Designer 'crashes back to desktop' when working on Sequencer jobs - and there is a patch for it. :D Brief description of problem (ecase 72758) ========================================== It appears that the Datastage designer client crashes intermittently when editing job sequences. The ...

OCI does not (yet) natively support TIMESTAMP. Treat is as a varchar in your job.

Yup.

Add a stage variable. No need to use it but it will make the compiler happy.

Why use a seq file? Start the job from the transformer and constrain the output to one row.

Actually, the patch we have been discussing for Service Pack 2 is the one that corrects the inability to open certain stages in a Sequence job. The patch you are probably refering to is one that prevents Designer crashes when working with Sequence jobs.

Both are good to have.

chulett wrote:What does your job process, by the way... a series of job / stage / link names? Any chance one of the jobs it is trying to attach to is itself? That can hang the job.

Well?

dylsing wrote:I thought I checked the Key property for the output column in the Link Collector but it was the Group property that I checked.

This is actually a pretty common mistake, what with the way the columns are ordered.

What I dbout whether we can call a routine in the derivation of a Transformer stage. Of course you can. Just recognize the fact that it will be called for every row processed. What does yor job process, by the way... a series of job / stage / link names? Any chance one of the jobs it is trying to a...