RE: Misunderstood DBSPACETEMP ?
Posted in 1996
Stefan
As I understand it, DBSPACETEMP is an onconfig configuration parameter. =
Setting it from the environment should have no effect. The application =
will create the temp table in the default dbspace or where the database =
was created.
In the onconfig file, you need to set DBSPACETEMP to tempdbs1 (the =
dbspace you've marked with T), like so:
DBSPACETEMP tempdbs1=20This will create the temp table in DBSPACETEMP. If you set it to dbs1, =
tempdbs1 then it will attempt to first create in dbs1 and if it fails =
then in tempdbs1.
Hope this helps
Sujit Pal
DBA, Computer Sciences Corp.
----------
From: Stefan Weideneder[SMTP:stefan@sweidi.weideneder.de]
Sent: Tuesday, October 08, 1996 11:46 AM
To: informix-list@rmy.emory.edu
Subject: Misunderstood DBSPACETEMP ?
Hi folks,
has anyone some experience with DBSPACETEMP ? Starting with version
7.0 ( an inofficial version ) until 7.12UC1 I've made a few tests
with temporary tables. Now I wonder, if I was wrong.
My problem:
I create two dbspaces, dbs1 ( a regular one ) and tempdbs1 ( a dbspace
that is marked as a temporary dbspace (T) ).
I set my DBSPACETEMP environment variable to "dbs1,tempdbs1" and start
dbaccess ( of course I've exported DBSPACETEMP ).
Now I create a temporary table with no log.
CREATE TEMP TABLE t1 ( f1 char(2016) ) WITH NO LOG;
I thought, that this table should be placed in "tempdbs1" now. But
no, it's obviously placed in dbs1. I don't know if the system has been
restarted again, after the dbspaces (dbs1 and tempdbs1)
had been created.=20
The system where I've made this strange experience was HP-UX 10.0
with 7.12UC1 OnLine DS.
( A last hint, my database was created in dbs1 ).
Is this a bug or do I have to restart the OnLine System after adding
a dbspace that I want to use as a temporary dbspace ?
Thanks for your reply,
Stefan
stefan@weideneder.de