Hi all
I am trying to update partitioned table in db2 v9.7 fp 3 using datastage
ADM6017E The table space "TSTEMP_32" (ID "4") is full. Detected on
container "/misnbtdb/temp/temp_32K" (ID "0"). The underlying file
system is full or the maximum allowed space usage for the file system
has been reached. It is also possible that there are user limits in
place with respect to maximum file size and these limits have been
reached.
Any body have any idea . Why it is getting filled up ..
it is consuming 105gb space and getting fail . On working envoirment it is consuming only 4 gb temp teblespace . Even No success after running RUNSTATS WITH DISTRIBUTION AND DETAILED INDEXES . Explain plans ,indexes , configurations are same in failed and working envoirment .
working envoirment where we are running query directly on db2 database . And failed evnoirment is where we are running the query using DATASTAGE .
Any sugestion ?
I am trying to update partitioned table in db2 v9.7 fp 3 using datastage
ADM6017E The table space "TSTEMP_32" (ID "4") is full. Detected on
container "/misnbtdb/temp/temp_32K" (ID "0"). The underlying file
system is full or the maximum allowed space usage for the file system
has been reached. It is also possible that there are user limits in
place with respect to maximum file size and these limits have been
reached.
Any body have any idea . Why it is getting filled up ..
it is consuming 105gb space and getting fail . On working envoirment it is consuming only 4 gb temp teblespace . Even No success after running RUNSTATS WITH DISTRIBUTION AND DETAILED INDEXES . Explain plans ,indexes , configurations are same in failed and working envoirment .
working envoirment where we are running query directly on db2 database . And failed evnoirment is where we are running the query using DATASTAGE .
Any sugestion ?