DSXchange

I can't see you have to do anything special to keep key values from repeating regardless of how many jobs are leveraging the same SKG. Each would grab a block size (however many that is, hopefully more than one) and when done would go back for more. There would be no duplicates.

Any chance you are running the 8.5 release? If so, the transformer looping functionality would come in handy here. Otherwise, seems to me you'd need to split that last field into however many separate columns as it contains and then perform a horizontal (columns to rows) pivot.

So... your example is of a single input record? And the last field, the internal values are separated by a newline? Also, to be anal, only your first value shows (sparcv9) at the end while all output examples show it... is that just a "typo" in your example? I'm assuming all internal value...

Where are your files located? Off the top of my head, .odbc.ini should be in $DSHOME while uvodbc.config should be in each project that needs it.

Any particular reason you keep marking your posts with a Job Type of "TX"?

No, the Folder stage can't do that. You'll need to parse it yourself inside the job.

From what I recall, it will want to combine whatever you put in the filename (which is required) and the Filter command, redirecting one into the other. For times like this when we really want to put everything in the Filter, I would typically put "/dev/null" on a UNIX system and (since yo...

dsscholar wrote:why cant i load it directly

What makes you think you can't?

Again... official support provider.

Some of the drop-down lists allow you to type directly in them, might give that a shot.

Post the same log entry from the first Execute Command stage.

Convert replaces a single character with another single charater. As noted, you need the parallel version of the Server EReplace function.

That or take advantage of the Filter property on the Sequential File stage to read them "all at once" based on a wildcard pattern & cat/type.

If everything used to work and then suddenly stopped working, find out what changed. If people aren't sure what changed or might be going on, contact your official support provider.

That would be a conversation to have with your DBA. Clarify something - are we talking about a single server installation here? And are you saying that jobs with the OCI stage work fine in other projects on this server but for one particular project all jobs with an OCI stage fail? I don't really se...

Sure, leverage the same utilities that the Server job uses under the covers - mkdbfile for a pathed hashed file or CREATE.FILE for an account-based one.