Coincidentally, we just had the same thing happen to us, tho in our
case we have a good idea what caused it: a power problem which took
down some of our SAN paths and our server.

If you have mirrored log volumes, you can try bringing up the server
using MIRRORREAD LOG VERIFY.  This saved us from having to restore
our database.

..Paul

At 12:03 PM 1/4/2006, Richard Sims wrote:

On Jan 4, 2006, at 11:55 AM, LeBlanc, Patricia wrote:

 Does anyone have any experience with this error:

01/04/2006 05:33:29  ANR7838S Server operation terminated.
01/04/2006 05:33:29  ANR7837S Internal error LOGREAD566 detected.

Our TSM server crashed (running on aix) and we had to restore to
yesterday.  Trying to find a cause so we can prevent it from happening
again.

I see info in the knowledge base about extending the log, but the
server
crashed and we didn't have that opportunity.

Look in your AIX Error Log for any file system or disk problems which
may have contributed to the problem, and review the dsmserv.err file.
If nothing obvious, call TSM Support, as this is a rare one with no
ready solution.

   Richard Sims    http://people.bu.edu/rbs

--
Paul Zarnowski                            Ph: 607-255-4757
Manager, Storage Systems                  Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu