DSXchange

You can set that to 500 as well but thats not the bottleneck. Its your target database that has a backlock effect on the source. If you put @FALSE in the constraint of your output link you will see that the input link rows/sec will soar. An array size of 10 is hardly going to make any difference. Wh...

ray.wurlod wrote: The DataStage Run Machine is written in a combination of C and DataStage BASIC.

I didnt know that C was used too. Good to know.

Try Array size 600. Try higher numbers. 10 wont bring you much. Also try transaction size with 0 then 10k or 20k. If you absolutely have to rollback if error occurs then specify transaction size as 0 else try with other numbers.

HUH. That doesnt look right. You sure its even working. Try something like

If the value from the above is greater than 0 then reject else pass.

I am loading Oracle 10g with ~1.5KB record size with a throughput of 2.5Krows/sec. I am talking about 2 cpu server engine.All inserts. It also depends upon your record size, table indices etc. Out of curiosity. What transaction size/array size combo you tried ?

Ditch the RMM stage. Time for the Super RMM stage.

Get the log in a file using the dsjob -logsum and redirecting the output to the file. Attach that file in your sequence job. Or if all you want is a summary then check the option "Include job status in email" in the notification activity under the notification tab.

You did not close the double quotes in your query. Copy paste the bottom code as it is. SELECT DS_JOBS.NAME AS JOB_NAME,DS_JOBS.CATEGORY,DS_JOBOBJECTS.NAME AS OBJECT_NAME,DS_JOBOBJECTS.OLETYPE, EVAL DS_JOBOBJECTS."IF INDEX(UPCASE(@RECORD), 'PROJDEF' , 1)>0 THEN 'FOUND' ELSE ''&q...

My point was to wait for him to come back. I bet its more then just info. sharing. It seems to me like he forgot to add the lines "How to get rid of this error?"

One reason is rejects. Try to get rid of your rejects. Correction: Try to get rid of rejects that create warnings in your log. Are you getting warnings? Also if your doing upserts, they are the worst. Try splitting your streams and doing inserts and updates seperately.

True. From time to time we should remind the "got it" posters to share the solution as well.

You dont have to post it in multiple forums. Please delete them before anyone replies to them.

Coverd before. Search on "Output file full". Do an exact search.

What happens when you use generated sql?
Also try this: Define two columns key, count and execute Rays query in the odbc stage. What do you see?

There are varialbes in your JobControl that were never intialized which is createing the errors Program "JOB.1261378057.DT.1399753353": Line 1078, Variable previously undefined. Zero length string used. Program "JOB.1261378057.DT.1399753353": Line 1144, Variable previously undefined. Zero length str...