DBSPACETEMP/tmp
Thanh noted the IDS 9.20 onconfig.std says temp files go to /tmp if DBSPACETEMP is unset or invalid, while the Admin Guide says rootdbs. Art S. Kagel replied that the location depends on factors such as implicit versus explicit temp tables, sort work files and logging, so either can occur. Thanh said the docs confuse beginners; Leonid Vorontsov added it depends on engine version. No definitive rule given.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
There is a comment in the onconfig.std as shipped with IDS 9.20, saying that: "... If specified it must be a colon separated list of dbspaces that exist when the DS system is brought online. If not specified, or if all dbspaces specfied are invalid, various ad hoc queries will create temporary files in /tmp instead." This contrasts to what is said in the Admin Guide, saying the DS would use the rootdbs for temporary space. Please explain, Thanh Sent via Deja.com http://www.deja.com/ Before you buy.
Actually you have to dig a bit deeper in the manuals. Temp location depends on several factors including whether the temp table is implicit or explicit or a sort-work file, whether it is to be logged or not, etc. They may be written to rootdbs or to /tmp. Art S. Kagel Thanh wrote: > > There is a comment in the onconfig.std as shipped > with IDS 9.20, saying that: > > "... If specified it must be a colon separated list of dbspaces that > exist when the DS system is brought online. If not specified, or > if all dbspaces specfied are invalid, various ad hoc queries will > create temporary files in /tmp instead." > > This contrasts to what is said in the Admin Guide, saying > the DS would use the rootdbs for temporary space. > > Please explain, > Thanh > > Sent via Deja.com http://www.deja.com/ > Before you buy.
In article <3993423A.532E2E76@bloomberg.net>, kagel@bloomberg.net wrote: > Actually you have to dig a bit deeper in the manuals. Temp location > depends on several factors including whether the temp table is implicit > or explicit or a sort-work file, whether it is to be logged or not, > etc. They may be written to rootdbs or to /tmp. I did scan the implicit/explicit things but then you know, after reading you thought that you know and then you read somewhere else that says something else and you screw... I meant me and all starters Sounds like a temporary space manager is needed :-) Thanks, Thanh > > Art S. Kagel > > Thanh wrote: > > > > There is a comment in the onconfig.std as shipped > > with IDS 9.20, saying that: > > > > "... If specified it must be a colon separated list of dbspaces that > > exist when the DS system is brought online. If not specified, or > > if all dbspaces specfied are invalid, various ad hoc queries will > > create temporary files in /tmp instead." > > > > This contrasts to what is said in the Admin Guide, saying > > the DS would use the rootdbs for temporary space. > > > > Please explain, > > Thanh > > > > Sent via Deja.com http://www.deja.com/ > > Before you buy. > Sent via Deja.com http://www.deja.com/ Before you buy.
"Art S. Kagel" wrote: > Temp location > depends on several factors including whether the temp table is implicit > or explicit or a sort-work file, whether it is to be logged or not, > etc. It depends on version of the engine too. Experiment can help. > They may be written to rootdbs or to /tmp. or to datadbs. > Art S. Kagel Leonid Vorontsov