DSXchange

Go with #2. Don't use the trigger. Pull the sequence value in your job so you know what it is before you use it. Then you can write the new ID to your file as well.

You've posted in an improper forum. This one is for discussion of posible FAQ topics, not for solving job problems. Here we don't know anything about your installation or even if you are seeking a Server or PX solution. Maveric has assumed PX. Please let us know which job type you have so the Modera...

No, it has nothing to do with 'improper' OSH code. Search the forum for your error message, it has been discussed here a bajillion times.

When you say 'iterations', are you using the Loop stages? There is a patch available that corrects a 'stack overflow' problem with looping Sequence jobs after a number of iterations in certain situations.

Contact your Support provider. Reference ECASE 62595. See if that helps.

You only need two triggers (or one composite one) if you want the next job to run if the previous one 'Ran OK' or Finished with Warnings. Is that the case? Or should warnings cause things to stop? I pretty much always use the 'Reset if required' option. Can't even think right now when I wouldn't.

There's no way you can execute "a bunch" of different sql statements from a single link, you won't be able to bind everything properly to the columns in the stage. Which is exactly what your error says happened.

For something like that, I'd suggest a script via sqlplus. Or put them in a proc.

Suggest you try it with the -server part removed for grins. And verify your Project and Job are spelled corrected, down to the case.

I would think you are fine now. For the record, what did you consider the 'primary column' that you had marked as a Key and marking what other column made it work for you? From what I recall of the rules, the repitition element should be the 'lowest' level element. But then, Key selection is more of...

Ok. A 'table definition' is not an 'account'. The Account in a Hashed File stage is synonymous with the Project the job that uses it is running in. This would typically be left blank to indicate the 'current' project. Your table definition should be either used with the 'Load' option on the Columns ...

chulett wrote:What two NLS_CHARACTERSET settings are involved here?

Did you ever get the answer to this question? Seems like it might be a piece of information needed to get you a proper answer. From someone else.

Why not look for that information yourself? All kinds of places would have that information, here's one that took me 2 seconds to find:

http://en.wikipedia.org/wiki/Surrogate_key

Define 'unload'. If all that means is 'dump to a file' with no transformations, that is usually best done with tools your database provides.

FULL.NAME or FULL.TEXT? You mention one and then use the other.

Argh... we don't need a 'Pitfalls' forum, but one for Pratfalls it seems. That and assorted Groaners.

It may 'work' but Convert would be a 'better' as in a more efficient answer.