DSXchange

Yes, that can work provided you know that the maximum length of the data in the CLOB is less than (or equal to) 4000.

You want the jobs to abort, not stop, for changes to rollback and for Sequence jobs to be restartable. Try a Routine Activity with UtilityFatalToLog rather than the Terminator stage, see if that helps.

Reset the aborted job and let us know the contents of any 'From previous run...' log message that (hopefully) shows up.

Any write caching going on?

You may be running into a problem with 'long' sql and part of the statement is getting lost. First try removing all whitespace, comments and returns, see if it works as one long line. Failing that, create a View using that sql and then source from the view.

String compares of numbers? No, not really going to work unless you pad them with zeroes to the same length. For example, try comparing "0003.6667" to "1456.7640" and see if you get the results you're expecting.

You're looking for orchdbutil it would seem. Lots of conversations here on its usage.

Sure looks that way.

"How can i find whether the OCI stg is using that index at run time."

It go faster?

As noted, use your tool of choice - Toad, SQl*Plus, etc - to check the explain plan of the DML if you're worried about it. Or have your DBA check for you.

You don't need to 'force' anything, it will use it automatically.

What's so weird about the problem? Updates, much like deletes, can be notoriously slow, especially when RI is involved. Do you at least have an index over the Key columns you are using? Without that, each update statement becomes a full table scan.

No such thing as 'force compile' in Server... and I do believe they've said they've already used the Multiple Job Compiler option in the Manager with no effect.

Funny, but again we just made the same suggestion.

ps. Add 1.

Since you substring 'from the left' you need to count from the left as well. What's your end game, what exactly do you want to do / extract once you have this position? I've been assuming return the substring from the string but perhaps it is something else. Using your example of "ABC 12345_10_...

Problem is, when you start a new post, the merry-go-round gets to start all over again. Best to stick to the original post and keep working at the problem there.