Re: Chunks down after upgrade

Lars Fransson writes: < Stuff deleted> >The most peculiar thing about it is that now we can access the >Dbspaces although the chunks are marked as down! >We browsed through the earlier messages but couldn't find any >indication that Informix have had any problems with these Dbspaces. >The installation is running on HP 9000/730 HP-UX 8.05. >1) What happened? Sounds like 5.0 picked up a fault that 4.1 didn't notice - we had a similar problem upgrading from 4.1 to 5.0 but in our case it was the root chunk that was marked faulty and the 5.0 system refused to come online at all - what we eventually had to do was restore the 4.1 environment, dbexport the databases, install 5.0 , initialize from scratch and dbimport the databases. We now recommend that this is done for all our sites, as this way we can be sure that the 5.0 instance at least starts off clean. >2) Howcome we can read the Dbspaces when the chunks are down? This is a known 'feature' that occurs when you have the mirroring flag set to 1, even if you have no mirroring devices assigned - this is so that people can still use the database(s) until it is more convenient to export/tbunload/whatever to fix the problem, as this can take a while. >3) If we reinitialize the chunks : > Can we restore a 4.1-backup when running 5.0? Not sure on this one - never tried it. Hope this helps, Richard Ridley