explicit TEMP table in rootdbs?

All, I'm having a problem with an explicit TEMP table being created in my rootdbs. I have 6 temp dbspaces created at 1 gig each. My entry for dbspace temp in my onconfig file is below. create TEMP table <tabname> ( column list .... ); Any help would be greatly appreciated. $ onstat -c|grep TEMP # DBSPACETEMP:# Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces DBSPACETEMP temp1:temp2:temp3:temp4:temp5:temp6 # Default temp dbspaces

If you issue "onstat -d", do the temp dbspaces show up as type TEMP, that is, do they have a code of "T". "Darren_Jaco...." <Darren_Jacobs@carmax.com> Sent by: forum.subscriber@iiug.org 03/15/2005 08:17 AM To: ids@iiug.org cc: Subject: explicit TEMP table in rootdbs? [4512] All, I'm having a problem with an explicit TEMP table being created in my rootdbs. I have 6 temp dbspaces created at 1 gig each. My entry for dbspace temp in my onconfig file is below. create TEMP table <tabname> ( column list .... ); Any help would be greatly appreciated. $ onstat -c|grep TEMP # DBSPACETEMP:# Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces DBSPACETEMP temp1:temp2:temp3:temp4:temp5:temp6 # Default temp dbspaces

Thanks to all who responded. I'm having a problem with my internal recall function (memory).....I believe my index to be corrupt!!! "June C. Hunt" <june_c_hunt@hotm ail.com> To Darren_Jacobs@carmax.com 03/15/2005 09:57 cc AM Subject RE: explicit TEMP table in rootdbs? [4512] "Darren_Jaco...." <Darren_Jacobs@carmax.com> wrote: > >I'm having a problem with an explicit TEMP table being created in my >rootdbs. I have 6 temp dbspaces created at 1 gig each. My entry for >dbspace temp in my onconfig file is below. > >create TEMP table <tabname> >( >column list .... >); > >Any help would be greatly appreciated. > >$ onstat -c|grep TEMP ># DBSPACETEMP:># Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces >DBSPACETEMP temp1:temp2:temp3:temp4:temp5:temp6 # Default temp dbspaces > Hi Darren, As Keith Simmons points out, the WITH NO LOG option is required. The following paragraph was taken from the SQL: Syntax manual for IDS v9.4, page 2-262. Hope this helps. Use the WITH NO LOG option to reduce the overhead of transaction logging. If you specify WITH NO LOG, operations on the temporary table are not included in the transaction-log operations. The WITH NO LOG option is required on all temporary tables that you create in temporary dbspaces. June