Re: NON-EMPTY TEMPORARY DBSPACE. Can we upgrade with this non-e

sujata_soman_at_omm-la2-infotech-001@internet.omm.com wrote: > > Hi all, > This actually refers to a previous chain of e-mail regarding the "Contents > of TEMPDBS", where we had a problem of a non-empty temporary dbspace ( with > non-empty chunks ) We finally found out the bug # 61442, had INFORMIX dial in > and reset the chunk. Now this was our development box. We have the same problem > on our production box, and we are due to upgrade from 7.13 to 7.23 this weekend. > What I need to know, is, if it is okay to go ahead and upgrade without resetting > the chunk, and if we do so, will the chunks show up as inconsistent ?? The > reason for that is , we are unable to coordinate a down time for INFORMIX to > dial in and fix our chunk. We have to get 300 + users off the system ( from all > over the country ). I guess we will do it if we have to, but ... > > So, any suggestions ?? Just drop the tempdbspace and re-add it. You can ignore the warning about not reusing chunks until taking an archive. These are so that a partial restore will not restore a deleted chunk to a reused disk. Since this is a tempspace it is never restored. During the brief time that the tempdbspace is down sorts and temp tables will go to the rootdbs. The only hard part is getting access to the tempdbspace when it is not being accessed by the users. Art S. Kagel