DSXchange

Yah, it's called a Filter.

So, you call this for every row through the job - over and over? And are checking the logs over and over? This kind of information is typically gathered in a separate step after the job is completed, hence the question. You should consider calling this 'after job' if you want to keep it 'inside' th...

Don't use a database stage for a lookup. Period. I don't care what database we're talking about, it's the least performant way to do that. Use a hashed file. They are the heart and soul of Server jobs, so leverage them. And before you ask - no, there's absolutely no reason to put all 20M source rec...

2.But while trying to use ORAOCIBL i was suggested that this stage will not work if DS and oracle reside in different server as in my case. We know the documentation says this, but it is not true. Any stage that leverages the Oracle 'bulk loader' - aka sqlldr - only does inserts. I've already passe...

Just to make it a little more obvious to searchers, the Kumar noted solution was to set the Array Size to 1. It's a performance killer, but an unfortunate need if you want to properly capture every rejected record from an OCI stage. Without it, the proper reject number will be shown in the Monitor a...

Or sort the data then use stage variables... there's a number of different ways. However, the answer to the question as asked is 'no'.

Where are you calling this? This is gathering more than just a link row count. Also, please verify what your arguments are.

When using ODBC stages I did create user-defined query where sequences where used and it did work fine, in that case i didn't mention the column in the ODBC stage. For the record, the ODBC stage isn't quite as 'picky' as the OCI stages when it comes to using all the columns you've defined. It will ...

Make sure that the user that ran the job has permissions to all sections of the pathname - drive, folders, etc. And the filename itself, of course.

ps. The 'Help' for this concept is in the online help accessable from the Director.

Also try searching the forums for that phrase, there are many discussions here on the topic - and some even with solutions. I know, because I've had the same problem in the past.

The 'Monitor tab' is in the Director.

Can you post the routine you wrote? Please wrap it in 'code' tags so that your formatting is preserved. Also inlcude an example of how and especially where you are calling it in your job. Thanks.

Give us some specific values that are passing out #8 that you feel should not be...

You'll find most people here will heartily disagree with #1. Changes outside of the development environment should be strictly forbidden and you enforce this either by using Protected projects or a tool like Version Control which can ensure that jobs in those environments are Read Only.

I know. It's just that, while we could possibly come up with a way to answer the second question, the first can only be answered by The Builders.