Oninit cdi / Archive
Talk to an expert →

Help! I've dropped temp dbspace and can't recreate it

Posted in 2006

Topics: Storage & Space Management, Server Administration, Platform-Specific Issues, Versions, Editions & End-of-Life

Beau Nanaz — — source: Usenet: comp.databases.informix

IDS 10.0, Linux 2.4.21 64-bit Hi family. I recently realized that the dbspace I had created (tempdbs1) and listed in the DBSPACETEMP parameter was not actually created as a temp dbspace - I had omitted the -t when I created the space. It was the only entry in DBSPACETEMP and consisted of one chunk. No problem, says I, just drop it and recreate it with the -t: onspaces -c -d tempdbs1 -t -p <ugly path name here> -o 0 -s2097152 (Yes, lage chunks are enabled - no quibbling about the size, please.) Oh, yes, and I changed TAPEDEV to /dev/null and ran a level-0 backup after dropping it. I get this message: The dbspace you are trying to add is already in the DBSPACETEMP configuration parameter list and has a page size different than other dbspaces in the list. All the temporary dbspaces specified in the DBSPACETEMP configuration parameter list must have same page size. This is sheer nonsense! Of course the dbspace is already there! The space was listed in DBSPACETEMP before I created the instance so I got an error message and the server went on to a happy life anyway! And I have NOT changed the page size either. At this time I cannot bounce the engine to see if that clears up anything. Still, has anyone seen this before? Thanks. --J. PS Ignore the name in the From line. Enough of y'all know who this is. :-)

↪ replying to Beau Nanaz
ifxmaillist@quanta.co.nz — — source: Usenet: comp.databases.informix

When you last started the engine was this dbspace in DBSPACETEMP ? To get it out you need to stop and start your engine. MW -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Beau Nanaz Sent: Tuesday, 23 May 2006 9:54 a.m. To: informix-list@iiug.org Subject: Help! I've dropped temp dbspace and can't recreate it IDS 10.0, Linux 2.4.21 64-bit Hi family. I recently realized that the dbspace I had created (tempdbs1) and listed in the DBSPACETEMP parameter was not actually created as a temp dbspace - I had omitted the -t when I created the space. It was the only entry in DBSPACETEMP and consisted of one chunk. No problem, says I, just drop it and recreate it with the -t: onspaces -c -d tempdbs1 -t -p <ugly path name here> -o 0 -s2097152 (Yes, lage chunks are enabled - no quibbling about the size, please.) Oh, yes, and I changed TAPEDEV to /dev/null and ran a level-0 backup after dropping it. I get this message: The dbspace you are trying to add is already in the DBSPACETEMP configuration parameter list and has a page size different than other dbspaces in the list. All the temporary dbspaces specified in the DBSPACETEMP configuration parameter list must have same page size. This is sheer nonsense! Of course the dbspace is already there! The space was listed in DBSPACETEMP before I created the instance so I got an error message and the server went on to a happy life anyway! And I have NOT changed the page size either. At this time I cannot bounce the engine to see if that clears up anything. Still, has anyone seen this before? Thanks. --J. PS Ignore the name in the From line. Enough of y'all know who this is. :-) _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list

↪ replying to Beau Nanaz
Art S. Kagel — — source: Usenet: comp.databases.informix

Beau Nanaz wrote: > IDS 10.0, Linux 2.4.21 64-bit > > Hi family. You may HAVE to bring the server down, remove the old dbspace from dbspacetemp and restart it, but try just re-setting DBSPACETEMP to a list that does NOT contain the dropped dbspace, or call the new one something else, at least until you can schedule a long enough downtime to drop that one, bounce the server, and add the original one back. Art S. Kagel > I recently realized that the dbspace I had created (tempdbs1) and > listed in the DBSPACETEMP parameter was not actually created as a temp > dbspace - I had omitted the -t when I created the space. It was the > only entry in DBSPACETEMP and consisted of one chunk. > > No problem, says I, just drop it and recreate it with the -t: > onspaces -c -d tempdbs1 -t -p <ugly path name here> -o 0 -s> 2097152 > (Yes, lage chunks are enabled - no quibbling about the size, please.) > Oh, yes, and I changed TAPEDEV to /dev/null and ran a level-0 backup > after dropping it. > > I get this message: > > The dbspace you are trying to add is already in the DBSPACETEMP > configuration parameter list and has a page size different than other > dbspaces in the list. All the temporary dbspaces specified in the > DBSPACETEMP configuration parameter list must have same page size. > > This is sheer nonsense! Of course the dbspace is already there! The > space was listed in DBSPACETEMP before I created the instance so I got > an error message and the server went on to a happy life anyway! And I > have NOT changed the page size either. > > At this time I cannot bounce the engine to see if that clears up > anything. Still, has anyone seen this before? > > Thanks. > > --J. > PS Ignore the name in the From line. Enough of y'all know who this is. > :-) >

Glossary