Data Dbs suddenly went Full

Hi, We've faced an issue where the dbspace kept on reducing and suddenly it reaches dead level. Then we've added space, but after adding space into it, the old space is being shown as well, as it never being used. After monitoring log file, we've found "temporary DBspace tempdbs_testdb is full" message. There is'nt any other message there to be monitored. Is there any way that the data dbs is being used as a temporary storage ? What else could be the reason for it ? Regards Kasi

Data dbs go full only when add data into the database, other then the tempdbs go full by sort/temp tables and so on. From your message, the online.log "temporary DBspace tempdbs_testdb is full" ,this means there have some big transactions need big tempspace to sort/join/... you can get the transactions use "onstat -x" and with "onstat -g ses/sql" to find which SQL did it.

Logged temp tables are written to normal dbspaces. If you have non-temp dbspaces listed in DBSPACETEMP they will be used otherwise the current database's home dbspace is used. In the OP's case, I'd guess that was the 'datadbs'. Art Art S. Kagel AdvanceDataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) See you at the 2010 IIUG Informix Conference April 25-28, 2010 Overland Park (Kansas City), KS www.iiug.org/conf Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Jan 4, 2010 at 3:29 AM, NETSKY LIAO <liaosnet@126.com> wrote: > Data dbs go full only when add data into the database, other then the > tempdbs > go full by sort/temp tables and so on. > > >From your message, the online.log "temporary DBspace tempdbs_testdb is > full" > ,this means there have some big transactions need big tempspace to > sort/join/... > you can get the transactions use "onstat -x" and with "onstat -g ses/sql" > to > find which SQL did it. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --00151747362a4ba029047c5517f6