temp space question

We have an instance of IDS 9.40.HC3 on a HP-UX 11i (11v1) box, that has about an 100GB database and currently the temp space is 9GB made up of 6 chuncks. I want to reduce the temp space to 6GB made up of 3 2GB chucks. If for no other reason to make it look pretty. :-) Really I want to use the freed space to an another chuck for the database dbspace. We seldon go over 3.5GB use of temp space so 6GB should be enough for the unexpected. My question is what is what is the easies way to do this or am I just mad in thinking to try it? My idea was to bring down the engine then drop the first 5 nodes, rename 5th & 6th to 0 & 1 and then create a new LVM node. Change the onconf to reflect just temp0-temp2 and bring up the engine. It that a good plan? What am I missing? John DBSPACETEMP temp0:temp1:temp2:temp3:temp4:temp5:temp6 crw-rw---- 1 informix informix 64 0x01000f Apr 2 2005 temp0.1 {1GB} crw-rw---- 1 informix informix 64 0x010010 Apr 2 2005 temp1.1 {1GB} crw-rw---- 1 informix informix 64 0x010011 Apr 2 2005 temp2.1 {1GB} crw-rw---- 1 informix informix 64 0x010012 Apr 2 2005 temp3.1 {1GB} crw-rw---- 1 informix informix 64 0x010013 Apr 2 2005 temp4.1 {1GB} crw-rw---- 1 informix informix 64 0x010026 Mar 4 2006 temp5.1 {2GB} crw-rw---- 1 informix informix 64 0x010027 Mar 4 2006 temp6.1 {2GB}

How many CPUs do you have allocated to the instance? A good rule of thumb is to set your temp spaces to a multiple of the number of CPUs. More, smaller temp dbspaces typically provide better parallelism and performance so long as there is no bottleneck with storage. Christine jda wrote: > We have an instance of IDS 9.40.HC3 on a HP-UX 11i (11v1) box, that has > about an 100GB database and currently the temp space is 9GB made up of > 6 chuncks. I want to reduce the temp space to 6GB made up of 3 2GB > chucks. If for no other reason to make it look pretty. :-) Really I > want to use the freed space to an another chuck for the database > dbspace. We seldon go over 3.5GB use of temp space so 6GB should be > enough for the unexpected. > > My question is what is what is the easies way to do this or am I just > mad in thinking to try it? > > My idea was to bring down the engine then drop the first 5 nodes, > rename 5th & 6th to 0 & 1 and then create a new LVM node. Change the > onconf to reflect just temp0-temp2 and bring up the engine. It that a > good plan? What am I missing? > > John > > DBSPACETEMP temp0:temp1:temp2:temp3:temp4:temp5:temp6 > > crw-rw---- 1 informix informix 64 0x01000f Apr 2 2005 temp0.1 > {1GB} > crw-rw---- 1 informix informix 64 0x010010 Apr 2 2005 temp1.1 > {1GB} > crw-rw---- 1 informix informix 64 0x010011 Apr 2 2005 temp2.1 > {1GB} > crw-rw---- 1 informix informix 64 0x010012 Apr 2 2005 temp3.1 > {1GB} > crw-rw---- 1 informix informix 64 0x010013 Apr 2 2005 temp4.1 > {1GB} > crw-rw---- 1 informix informix 64 0x010026 Mar 4 2006 temp5.1 > {2GB} > crw-rw---- 1 informix informix 64 0x010027 Mar 4 2006 temp6.1 > {2GB}

"jda" <adamski@graceland.edu> wrote in message news:1168885465.843169.217250@11g2000cwr.googlegroups.com... > We have an instance of IDS 9.40.HC3 on a HP-UX 11i (11v1) box, that has > about an 100GB database and currently the temp space is 9GB made up of > 6 chuncks. It's not definitive, but that doesn't look like what you've got from the information given below. It looks like you have 7 separate temp dbspaces of various sizes. I want to reduce the temp space to 6GB made up of 3 2GB > chucks. If for no other reason to make it look pretty. :-) Really I > want to use the freed space to an another chuck for the database > dbspace. We seldon go over 3.5GB use of temp space so 6GB should be > enough for the unexpected. > > My question is what is what is the easies way to do this or am I just > mad in thinking to try it? > > My idea was to bring down the engine then drop the first 5 nodes, > rename 5th & 6th to 0 & 1 and then create a new LVM node. Change the > onconf to reflect just temp0-temp2 and bring up the engine. It that a > good plan? What am I missing? > > John > > DBSPACETEMP temp0:temp1:temp2:temp3:temp4:temp5:temp6 So assuming you actually have 6 temp dbspaces: 1. Single-user mode or something 2. Use onspaces to remove all six dbspaces 3. Use lvremove to remove all 6 LVs 4. use lvcreate to create the 3 new LVs 4a. (Probably some fannying around with symbolic links) 5. onspaces to create the 3 new 2GB chunks 6. Edit $ONCONFIG to remove the reference to temp3 through temp7 7. Bounce IDS