DSXchange

eostic wrote:Maybe someone can split this into its own thread.

Maybe?

Done.

Looks like one solution would be to drop your array size below 150.

I didn't look any further than doing a google search for "system resource exceeded" but it did bring up quite a number of topics on the subject. Probably some good information out there for you...

Interesting, certainly needed for other databases. And (a minor correction) those are parenthesis not brackets.

Good... then I don't see the need to play first row games and I see that you've posted to that effect. Thanks.

Some other line than what? It's clear they have a true "Large OBject" they are dealing with, hence the errors when it tries to shove it into a VARCHAR. And hence my suggestion to check to see of the stage even supports those objects.

Two things. One is I can't try squat as I haven't had DataStage access for 3 years now, having moved over to the Dark Side. Second, doesn't the dang product allow you to set the initial value of a stage variable yet on the Parallel side? Been there since Day One for Server and being able to do so wo...

Because theirs isn't.

Done.

Why are people seeing a need to use these functions?

Determine what is different about the two environments with regards to your connecting user and the permissions that it has. Obviously something is different there.

What makes you think you need to handle the first row differently?

In your shoes I'd be contacting your official support provider, see if the stage even supports CLOBs.

prasannakumarkk wrote:I have successfully implemented with varchar.

Only because your CLOB value was small, i.e. 4K or less.

So a Value Mark, eh? Interesting. Thanks for coming back and updating.

Why user-defined? Why not let the stage generate the SQL? If you did you'd find that it used a better mask for the TO_CHAR() function, one appropriate for a Timestamp data type: SELECT DW_DATE_ID,TO_CHAR(DATE_DT, 'YYYY-MM-DD HH24:MI:SS') FROM STG2D_DATE If you are consistent with your Oracle DATE ha...