DSXchange

Moderator comment: Split from this topic. You may be seeing the same message but it's your issue so off you go to your own post in the proper forum. And since this is your first post, I had to guess your version and O/S, if either are incorrect please edit your post and fix them.

I've used Chuck Smith's tools for this in the past, modifying some to store their output in a database table so it can be checked with simply queries.

Well... that message is pretty clear. Is this job using a new configuration file? Did you "Look for error messages in the preceding output"?

Let's go back to Ray's first question: Where exactly is this "insert parameter" control you are attempting to use?

True... but that would be more of an alternative rather than an equivalent.

Those are the kind of conversations you should be having with your DBA.

Did you do any searches for your "ORA-24381: error(s) in array DML" error that I assume you got based on the linked post? It's not about how many records are in the array but the total size - so that times the record length. For longer records, less will fit at a time. Of course there are ...

Bigger is not always better.

Nagaraj wrote:so why it is failing if i leave it as default 2000 rows and source being 7000 rows?

Because this -> default 2000 rows
Has nothing to do with this -> source being 7000 rows

Lower your array size, does the error go away?

Me, I don't care how "identical" your specs are - this is your issue so off you go to your own post. I did however link back to the original post.

That would be the Index() function, something you can search for as its use for this purpose has been documented here quite a bit.

Are you sure you didn't mean version 7.5.3 ?

OK peoples... I'm two steps away from locking this thread. We do not need to keep piling in here with every possible reason for the rather generic "abnormal ternination of stage" error one gets with Server jobs.

No, you don't need a "primary key" - what you need is a unique constraint in order for this to work. That constraint could be from a primary key or a unique index and causes the insert to fail which is what triggers the update.

Mark the first two columns as "key" columns.