The problem you ran into is a dead-lock problem, that can be hit
during certain states of the database and log, usually lots of
activity or recovery causing large numbers of log pages to be
processed. This has been fixed and will be available in few weeks when
the testing is complete.
If this problem returns and persists please contact me I can make a
fix-test version of the PTF available.
Jim Riehl
Tucson ADSM Sun Server Developer
Bradley King writes:
> If anyone wonders, I solved my own problem. I'm not sure it was the
> best way, but it worked. I did:
>
> dsmserv dumpdb
> dsmserv install
> dsmserv loaddb
> dsmserv auditdb
> dsmserv
>
> which now works again. Everything went fine, but it sure would have been
> nice if the server had given me some vague message somwhere about what was
> wrong. I certainly hope this is not a magic 32 day ritual!
>
> >At 07:24 AM 7/17/96 -0500, you wrote:
> >>I have a very confusing problem. (at least for me) I have been running
> >>a Solaris 1.2.0 adsm server for about a month now. I wanted to add a
> >>device,
> >>which I think I did successfully. At some point on the same day the server
> >>stopped communicating with anyone. I killed and restarted it to no avail
> >>I rebooted the server to no avail. Since I have a respawn in the inittab
> >>for the server and several schedule clients I rebooted the Sun after
> >>changing
> >>the inittab. I then launched the dsmserv by hand it says:
> >>
> >>ADSTAR Distributed Storage Manager for Sun Solaris
> >>[1] 403
> >># Version 1, Release 2, Level 0.0/1.0
> >>
> >>Licensed Materials - Property of IBM
> >>
> >>5765-303 (C) Copyright IBM Corporation 1990, 1994. All rights reserved.
> >>U.S. Government Users Restricted Rights - Use, duplication or disclosure
> >>restricted by GSA ADP Schedule Contract with IBM Corporation.
> >>
> >>ANR7800I DSMSERV generated at 16:24:47 on Mar 14 1995.
> >>ANR7801I Subsystem process ID is 403.
> >>ANR0900I Processing options file dsmserv.opt.
> >>ANR0990I ADSM server restart-recovery in progress.
> >>ANR0200I Recovery log assigned capacity is 28 megabytes.
> >>ANR0201I Database assigned capacity is 224 megabytes.
> >>ANR0306I Recovery log volume mount in progress.
> >>ANR0353I Recovery log analysis pass in progress.
> >>ANR0354I Recovery log redo pass in progress.
> >>ANR0355I Recovery log undo pass in progress.
> >>ANR0362W Database usage exceeds 92 % of its assigned capacity.
> >>
> >>
> >>then it just sits there w/o using cpu or allowing any connections. There
> >>are no errors in the log file, none on the screen. Is there anything that
> >>can be done? Since the server gives no indication of errors and there
> >>is no way to communicate with it I don't know what to do next.
> >>
> >>They typical resonse to an attempt to connect is as follows:
> >>>dsmdsmc
> >>ADSTAR Distributed Storage Manager
> >>Command Line Administrative Interface - Version 2, Release 1, Level 0.3
> >>(C) Copyright IBM Corporation, 1990, 1996, All Rights Reserved.
> >>
> >>Enter your user id: admin
> >>ANS5658E TCP/IP failure.
> >>ANS5519E Unable to establish session with server.
> >>
> >>ANS5103I Highest return code was -50.
> >>>
> >>
|
