ADSM-L

Problems starting adsmserver

2004-07-07 09:43:46
Subject: Problems starting adsmserver
From: Jose Angel Navalón <Jose.A.Navalon AT UV DOT ES>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 7 Jul 2004 15:25:07 +0200
Dear gentlemen,
 
We have a problem when we trie to Start the ADSM Server, it begins
correctly but stops at a point in wich it say that the system date is
not correct.
 
We have verified the system date and it?s correct.
 
We have read that running the Accept date from command line console the
problem can be solved, but if we can run the adsmc, it says that can?t
connect to the adsm server.
 
Please, help us.
 
This is the output for the dsmserv command.
 
------------------
 
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 784 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.
ANR2100I Activity log process has started.
ANR1305I Disk volume /usr/lpp/adsmserv/bin/backup.dsm varied online.
ANR1305I Disk volume /usr/lpp/adsmserv/bin/spcmgmt.dsm varied online.
ANR1305I Disk volume /usr/lpp/adsmserv/bin/archive.dsm varied online.
ANR2102I Activity log pruning started: removing entries prior to
06/17/04 00:00:00.
ANR0110E An unnexpected system date has been detected; the server is
disabled. Use the ACCEPT
DATE command to establish the current date as valid.
ANR2103I Activity log pruning completed: 0 records removed.
ANR8439I SCSI library OPTLIB1 is ready for operations.
ANR0110E An unnexpected system date has been detected; the server is
disabled. Use the ACCEPT
DATE command to establish the current date as valid.
 
 
Best regards,
 
Thank you.
 
Jose Angel Navalón.
University of Valencia.

<Prev in Thread] Current Thread [Next in Thread>