Did anybody see this message before in your db2diag.log?

My answer to your question is 'YES'

But you have not provided enough information to give a useful answer .. Please read 'Must Read Before Posting' thread ...

Sorry for not being able to help

Sathyaram

I got this message in my db2diag.log file. I need to find out the cause of this problem.
We are running DB2 version 7.2 on Sun Solaris.

thanks

That's useful to know ...

1) Check the ulimit for the instance owner

ulimit -a

If the max allowable filesize is not unlimited, I'd suggest to set it to unlimited ... Instance restart is needed for db2 to pick this up

2) Check if your file system is large file enabled

3) If you are using multi-container SMS tablespace, a filesystem full in one of the container paths will cause the above said condition

Having said these, more important is to see if your query can be tuned to create 'less temp data'

HTH
Sathyaram

THis can be caused by the directory that you have the tempspace going to isn't large enough, or you don't have Large File enabled on your systems. Not sure about solaris, but AIX has ulimits for each id, and you must also set those.





You don't say how large your tempspace is, We always try to make it 1.5-2.5 times are largest tablespace.