Re: What patches are applicable to the HPE55

In article <NEWTNews.815855505.10393.Regalia@ppp08562.uu.net> mail08912@pop.net writes: >From: mail08912@pop.net >Subject: What patches are applicable to the HPE55 >Date: Wed, 08 Nov 95 10:24:28 PDT >Does anyone know what patches are applicable to the HPE55 Server. We are >running HP-UX 9.04. I've been told that the 700/800 series are >workstation models and the 'letter' series are servers. >We have a problem with Informix destroying the databases whenever the >system is shutdown and re-booted. We use Informix version 7 on cooked >files. Are there any patches that need to be installed. >Thank you >C.V. Regalia Firstly, HP 700s are workstations, HP800s are servers. An E55 is an 800. Secondly I suspect that your problem is more likely to relate to the shutdown/startup process not being clean. You should make sure that the database is stopped and offline before shutdown. You could do this with onmode in the shutdown file but there are a couple of problems there. Firstly it's not nice to pull the chair from under your users like that. Secondly it may be that the engine takes some time to close down after the onmode (transactions to be cleaned up) and if shutdown simply fires onmode and then takes the system out the closedown may not have been completed. It's better to use onmonitor and use graceful shutdown (accompanied by increasingly threatening wall messages) with perhaps a change to immediate shutdown at the end to take out the users who left their terminals on and wandered away. Then take the system offline. If the database is on raw disk there are other possible problems. Firstly you need to make sure that the partitions don't overlap with other partitions (assuming you use HP's standard disk partitioning) as there are several mutually exclusive sets of partitions in the HP approach to partitioning a disk. Secondly you could have an Informix chunk straying outside its allocated partition if you weren't carefull enough in setting up the chunks (just a thought - is it possible to do this with cooked files? If so fsck might be clobbering them). Thirdly, if you accidentally leave the partition or an overlapping partition in /etc/checklist fsck might get run on it or the superblock might get some bit twiddled as part of the interlock which prevents fsck being run needlessly on properly shutdown files. Ian