<No Subject Supplied>

>From naomi Fri Apr 16 10:25:26 MST 1993 remote from qip From: naomi@qip (Naomi Walker) Message-Id: <9304161725.AA29111@qip> Received: from qip by misty.anasazi.com; Fri, 16 Apr 93 10:25:25 MST Received: by qip (5.61/1.2) (from naomi (Naomi Walker) to informix-list@rmy.emory.edu) id AA29111; Fri, 16 Apr 93 10:25:27 -0700 Subject: Re: Upgrade Aborting! To: rridley@sin-pss.DHL.COM Date: Fri, 16 Apr 93 10:25:26 MST Cc: informix-list@rmy.emory.edu (Informix List) In-Reply-To: <9304161622.AA15975@everest.sin-pss.dhl.com>; from "Richard Ridley" at Apr 17, 93 12:22 am X-Mailer: ELM [version 2.3 PL11] Content-Type: text Content-Length: 1368 > > > We are trying to upgrade from Online 4.1 to 5.0 on an HP-UX 8.0 > > We get the error "Online MUST abort - primary chunk is down" when > trying to save the Shared Memory parameters : this is very strange as > the exact procedure on an HP-UX 8.02 (tho' with a much smaller > database) worked fine. Is there anything we can do besides > dbexporting re-initialising and dbimporting, as this will take a long > time with a 1Gig database which is needed NOW! > > When we restoe the 4.1 environment it comes up without a murmur - > any suggestions out there? > I'm not sure what went wrong, but i'd look at your tbconfig and make sure it matches what you think is correct. My primary reason for writing is to warn you to be extremely careful in this situation. When upgrading from 4.0 to 4.1, we found going forward was no problem. However, on one system, when we had to revert back to 4.0 for a short time due to some problems, we found the databases were not compatible, and had to restore from archives. I think this is still true with going from 4.1 to 5.0. Once a database is touch, it is converted to 5.0 format and is not compatible. -- Naomi Walker (aka N7FSA) naomi@anasazi.com Phoenix, Arizona To get the full value of joy, you must have someone to divide it with. ---Mark Twain