DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
itsvarunm
Participant



Joined: 31 Aug 2012
Posts: 7

Points: 74

Post Posted: Fri Aug 31, 2012 6:58 am Reply with quote    Back to top    

DataStage® Release: 8x
Job Type: Parallel
OS: Unix
Hi,

I have a DB2 table which is having around 30 columns. I am using SCD staging in DS 8.1 to do SCD on this job. But the job aborts with the below error
[IBM(DataDirect OEM)][ODBC DB2 Wire Protocol driver]Out Of Memory

Any help is highly appreciated

Thanks,
Varun
ArndW

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup

Joined: 16 Nov 2004
Posts: 15367
Location: Germany
Points: 86605

Post Posted: Fri Aug 31, 2012 7:14 am Reply with quote    Back to top    

Is this the read or the write stage? Are you doing any SQL? How many rows of data or megabytes of data in the file and how long before the failure occurs after starting the job? If this is the read stage, then make a copy of your job with just the Read and a peek stage and see if the problem persists.

_________________

Image
Rate this response:  
Not yet rated
itsvarunm
Participant



Joined: 31 Aug 2012
Posts: 7

Points: 74

Post Posted: Fri Aug 31, 2012 8:57 am Reply with quote    Back to top    

Hi ArndW,

This is a write stage with UPSERT.. No custom SQL is used. The data volume is only in the 100s .. No big columns also. So the data size is less. The job barely takes 10 secs to execute. I had tried removing the SCD and doing a direct insert into the table. This works fine. The SCD /upsert seems to be causing the problem.

Thanks,
Varun
Rate this response:  
Not yet rated
ArndW

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup

Joined: 16 Nov 2004
Posts: 15367
Location: Germany
Points: 86605

Post Posted: Fri Aug 31, 2012 10:56 am Reply with quote    Back to top    

See if setting APT_DISABLE_COMBINATION to "true" changes the error message, perhaps it was incorrectly reported.

Do you have unusual data types in the record?

_________________

Image
Rate this response:  
Not yet rated
itsvarunm
Participant



Joined: 31 Aug 2012
Posts: 7

Points: 74

Post Posted: Fri Aug 31, 2012 11:16 pm Reply with quote    Back to top    

Hi ArndW,

Tried that but didnt help. There are no special column types in the table.

Thanks,
Varun
Rate this response:  
Not yet rated
ArndW

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup

Joined: 16 Nov 2004
Posts: 15367
Location: Germany
Points: 86605

Post Posted: Sat Sep 01, 2012 9:39 am Reply with quote    Back to top    

It does sound like a bug/problem in the SCD stage (since the error disappears when you remove the stage). If you replace your ODBC output with a PEEK or sequential file stage does the error persist?

_________________

Image
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours