Yeong,

Your ADSM Database size is very small.  I would suggest to increase your DB
size as well.
To get rid of the log size problem you have to extend your recovery log size.
Have a look in your dsmserv.dsk for you current db and log names.
Use dsmfmt to format another log file. (dsmfmt -m -log filename size)
Size I would suggest about 20.
Then use dsmserv extend log filename size to increase your log size.

After this your server will start again.  As I said before, you need to
increase your DB.
That is possibly why your log run out of space.
Use dsmfmt -m -db filename size.
Then within ADSM admin session use define dbvol and extend db.
That is possibly why your log run out of space.

Regards
Gerrit


Yoon Sang Yeong wrote:

> I have encountered the following error message when i start up ADSM server,
> please help me how to recover this problem? Billion thanks to any reply.
>
> ADSTAR Distributed Storage Manager for AIX-RS/6000
> Version 3, Release 1, Level 2.40
> Licensed Materials - Property of IBM
>
> 5765-C43 (C) Copyright IBM Corporation 1990, 1998. All rights reserved.
> U.S. Government Users Restricted Rights - Use, duplication or disclosure
> restricted by GSA ADP Schedule Contract with IBM Corporation.
>
> ANR0900I Processing options file dsmserv.opt.
> ANR0990I ADSM server restart-recovery in progress.
> ANR0200I Recovery log assigned capacity is 102 megabytes.
> ANR0201I Database assigned capacity is 52 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.
> ANR0352I Transaction recovery complete.
> ANR9999D adminit.c(989): Insufficient log space to update table
> Administrative.Attributes.
>
> Best Regards,
> Yeong