DSXchange

Good to know - thanks for posting that! :D

Here are the various fault types that I am aware of: signal Value Description 1 (SIGHUP) hangup 2 (SIGINT) interrupt 3* (SIGQUIT) quit 4* (SIGILL) illegal instruction 5* (SIGTRAP) trace trap 6* (SIGIOT) IOT instruction 7* (SIGEMT) EMT instruction 8* (SIGFPE) floating-point exception 9 (SIGKILL) kill...

1. Derive no.of years between two dates Again, way too vague. Derive how exactly? And unfortunately your example is a poor choice because the MM/DD portions are identical. How about these two dates - how many years are between them in your environment? 05/28/1964 & 03/27/1965 1? 2? Rounding up ...

Yes Sir. :D

Is that... ok? Or something totally goofy you've never seen before?

Doesn't really answer my question. Write out a specification, spell out in words how the 'number of years' difference between two full dates would need to be computed, regardless of the tool you would use. Post it here. Then we can help convert that into what you would need for a DataStage routine o...

What do you consider to be the 'number of years' between any two dates? Simply the subtraction of the two YYYY components? The number of days between them divided by 365? Something else?

One 'dev/test' Server installation with one 'RTI' installation. The only difference between dev and test are the Projects on the server.

I don't believe that would be a 'DS Oracle plug-in' thing, but a general Oracle question - does Oracle allow it. I don't think so but have never had any reason to encrypt anything other than string data.

Have you talked to your DBA?

As you noted, it will be in the Project directory that the job was run from.

ps. You still have the 'Disable BBCode' option enabled / checked, which is why the quote in your post came out wrong. Again. Uncheck it.

Look in the Sequence job's log for a 'Job Run requested (...)' entry and double-click on it. What is the Mode (row/warn limits) ?

Placement isn't critical as long as Project and Job come last. And all child jobs will inherit this limit from the Sequence automagically.

That error means there is more than just "2006-02-23" in your date, which usually means Field Marks or some other invisible mojo going on. So try either passing YSATCdate<1> to the DSSetParam function or remove things first using Convert or EReplace: Convert(@FM,"",YSATCdate) This ...

Thanks.

lsnovick wrote:LOG=ora.8105.41297d.0.log

That ".log" file is where these particular sqlldr errors would be. You'd need to find it, I assume it would be in the job's Project but don't know for certain.

Source database? Actual data type?

Is this some kind of INTERVAL data type?