DSXchange

That usually means the job is already running.

Technically, you should never "need" hints. As noted, talk to your DBA and have them help you track down the issue. If they don't see anything on their side, you might want to consider involving your official support provider as I seem to recall that it may be an artifact of using those &...

First question that comes to mind - is your "ROW_ID" column indexed? Sounds like a full table scan to me, meaning it either doesn't have one or it isn't being used. For the later, involve your DBA and get an explain plan to determine why, typically it turns out to be a 'stats' issue from w...

To me, any kind of apparent "internal limit" error like the one you're seeing from the "storage area manager" and the number of BAPI stages / columns in your job, need to be pursued with your official support provider.

What operating system? This may help explain things, including why you can't kill them... you can't kill the undead.

Good.

Save the 'custom' SQL for those times when you have no other choice and as a Best Practice let the stages generate the SQL for you whenever possible. Those who come after you will be ever so grateful.

You need to help us help you. We have no idea what 'every possible way' you tried and I'm not willing to guess. Did you try the search suggested? What exactly did you try to solve this problem? :? Worst case, we need to know everything you can tell us about your OCI stage. For example - what is your...

Sounds more like DDL than DML.

Why do you feel the need to do anything custom here? Why not leverage the 'Delete existing rows only' update action? That should be all you need.

Rajmohan, I split this question from the completely unrelated post in the General forum that you added it to for some reason. Please take a moment and edit your post to add the relevant details for us - version, O/S, etc. They are only prompted for when you start a new conversation with the Post new...

Which DB2 stage? Shouldn't need anything 'custom' for this as there is (typically) a "Delete existing rows only" update action or equivalent available. Don't confuse "key" columns with indexes or primary keys, they are basically just columns to bind into the where clause.

What I've encountered working with the likes of Google and Yahoo is apparently known as "Signed Degrees format" as noted here.

What do you mean here by "geographical datatype"? Something specific to a software package? The geocodes (lat/long) I've dealt with in the past are simple decimal values with a scale of 5 or 6, from what I recall.

First advice for problems that mention the dreaded "CombinedOperatorController" is to add $APT_DISABLE_COMBINATION to your job, set it to True and rerun. The error will (should) still happen but you'll see which stage / operator is actually throwing the error.

I believe that is only true when there is a key field involved, which (oddly enough) is not required. I recall being able to retrieve a sequence from Oracle by doing a 'select x.nextval from dual' lookup without needing a fake where clause. It would just fire for every row with no input from the sou...