Why wouldn't a complete network shutdown and startup, without a system
reboot, be sufficient to clear the buffer pool memory structures?

Richard G.

[log in to unmask] wrote:
>
...
> Beyond the above case/example, their are rare rare rare cases of corruption
> in buffer pools and other data structures which typically consist of
> forward and backward pointers to data in real or virtual memory... If you
> have ever had a broken chain in Image... it is the same thing in network and
> O.S. data structures... it is possible for a pointer to be corrupted due
> to hardware failure or software bugs and then we find out how robust the
> software which reads the data is... In some cases the integrity of the
> system is in so seriously in question that an immediate system abort is
> the only appropriate action... In  other cases it is appropriate to mark
> the entry as bad and then relink the forward and backward pointers around
> the entry in question.  What does this have to do with reboot frequency ?
> With a system reboot, you are assured these forward and backward pointers
> are set back to zero (0) and any memory real or virtual which has been
> de-linked from a forward / backward pointer chain is now returned to the
> system.
>
> Well, the above 2 RUN-ON sentences are my .02$ on this topic from a
> Network perspective...  Enjoy!
>
> Regards,
>
> James Hofmeister
> Hewlett Packard
> Worldwide Technology Network Expert Center
> P.S. My Ideals are my own, not necessarily my employers.


--
Richard L Gambrell
Database Administrator and
Consultant to Computing Services at UTC

** UTC business:
  University of Tennessee at Chattanooga
  113 Hunter Hall, Dept. 4454
  615 McCallie Ave., Chattanooga, TN 37403-2598
  fax: 423-755-4025
  phone: 423-755-4551       email: [log in to unmask]

** other business or private:
  voice mail/phone: 423-874-0261  email: [log in to unmask]