lookup failure

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
samsuf2002
Premium Member
Premium Member
Posts: 397
Joined: Wed Apr 12, 2006 2:28 pm
Location: Tennesse

lookup failure

Post by samsuf2002 »

Hi

i am getting this "Lookup_459,0: Fatal Error: fstat() failed: Object is too large for operation" error i am using sqlserver

can any one help
thanks
Sameer
hi sam here
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The message is fairly obvious; something in your query is generating a value that is too large. Assuming you are using ODBC, there is a maximum row size and a maximum number of columns that can be transferred. These maxima can be configured in uvodbc.config using the MAXFETCHBUFF and MAXFETCHCOLS parameters.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
samsuf2002
Premium Member
Premium Member
Posts: 397
Joined: Wed Apr 12, 2006 2:28 pm
Location: Tennesse

lookup failure

Post by samsuf2002 »

the solution what i found is we can split the job and run it and it worked fine but the issue is its taking more time this will be gud for one time initial load
hi sam here
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

What is the job design? And how did you split it ?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Post Reply