DSXchange

Welcome. :D

Actually, first thing to try would be to help yourself. Do an exact search of the forums for your error: "Parameter specified but not used in flow: DSPXWorkingDir". I got almost 100 hits when I did.

Exactly, you've always needed 'allow' permissions to both cron and at for UNIX. And as Ray notes, cron does all of the repeating schedules while at does schedules that only run once. Granted, the vast majority of times you're doing the 'every X' type scheduling so for some people the issue may never...

I said experiment not solution. Wanted to see if the problem was in the DRS stage or the data itself regardless of the stage of choice.

First mention of there being a delimiter involved. Use an expression inside each field that can be null, check for null and only add the comma when it is not. Rather than: : NullToEmpty(hash_Biseps_Retailer.AD_CONTACTFIRSTNAME) : "," : Something like this instead: : (If IsNull&...

As an experiment, does it work more better if you replace the DRS stage with an OCI stage?

Just use it directly in the concatenation for the fields. Worst case: NullToEmpty(company):NullToEmpty(suburb):NullToEmpty(postcode):NullToEmpty(firstname):NullToEmpty(surname):NullToEmpty(telephone) Obviously not syntactically correct without the link...

Wrap each possibly null field in the NullToEmpty() transform.

Aborts are always reported by the transformer as it is the active stage. And sometimes you need to leave the array size at 1 for things to work. What database, by the way? What db stage?

Lots of people, apparently. An exact search of the forums for "received signal SIGSEGV" turned up 71 matches.

Try setting APT_ORACLE_PRESERVE_BLANKS to true.

With an NVarchar source they probably aren't. Can you dump them to a flat file and then check their value with a hex editor / viewer? That or do an 'od -h' dump.

You must be doing something wrong or those are not actual question marks. Post your exact syntax from the job.

And if it was added to the job's parameters but doesn't show up in the run dialogue, I would assume that its 'Prompt?' property was changed to 'No'.

You want him to severely cut off their... oh sorry, castigate. Never mind.

No problem, glad I could help stop you from building some large, elaborate 'version control for multiple partitions' system.

Please mark the topic as Resolved using the button at the top of the screen!