Re: Offset (2)

Hi Marcel, I have seen this problem before. In my experience I have found that Informix has over written the LVCB but never the other way around. When you take a look at the LVCB you see a very nice Informix Copyright Message. The consequences I have seen have never effected Informix but some of the AIX LVM Utilities. For example, if you had picked up some diagnosis regarding your disks and decided to do a copylv you would find that it would not work. In future apply an offset to all AIX LV's. Note also, with AIX I have not seen it rewrite the LVCB, if you do this in Solaris with the VTOC it will overwrite on reboot and you are knackered. Regards Sean P. Galvin Marcel Nihon wrote in message <36D282E8.D80DEDED@ulg.ac.be>... >Hi, >Under aix, we have several Informix databases which were created without >offset in their dbspaces. >The dbspaces are raw devices. >We observed that the first bytes of some of these dbspaces were >overwritten by aix for the lvcb >(logical volume control block). >Does someone know what can be the consequences of the overwritten? >To introduce an offset in the dbspaces, does it exist a method other >than backup and restore? > >-- > Marcel Nihon > > -------------------------------------------------------------------- > Service General d'Informatique (SEGI) Support logiciels > Universite de Liege > Sart Tilman B26 Tel. : +32(4)366.49.78 > 4000 Liege Fax : +32(4)366.29.20 > Belgium email: Marcel.Nihon@ulg.ac.be > > >