Re: Server crashed on startup with error in dsmcperf.dll

2001-08-24 Thread Bandu Vibhute (GWB)
Clemens, Normally if you extend recovery log by 10-20 %, ADSM starts, but you have to initiate Full db backup ASAP. If this doesn't work then you have to restore db from recent tape(s). You can't apply patches to ADSM code when DB needs recovery. Good luck, Bandu Vibhute, George Weston

Re: Server crashed on startup with error in dsmcperf.dll

2001-08-24 Thread Jeff Bach
3.1.2.90 is newer. -Original Message- From: Bandu Vibhute (GWB) [SMTP:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 9:45 AM To: [EMAIL PROTECTED] Subject: Re: Server crashed on startup with error in dsmcperf.dll Clemens, Normally if you extend recovery log by 10-20 %,

Server crashed on startup with error in dsmcperf.dll

2001-08-20 Thread Block, Clemens
Hi Folk! I have an urgent problem with my ADSM Server 3.1.2.50 on a Windows NT System. Yes I know, it's quiet old. The new 4.1 x Server is also running on an nerw machine but unfor- tunaltely not all nodes are actually migrated. Murphy is everywhere. As I explained earlier the day, the Server

Re: Server crashed on startup with error in dsmcperf.dll

2001-08-20 Thread Martin, Jon R.
Clemens, It is possible to extend the log without starting the server. Check out the dsmserv extend log and dsmfmt commands. There are several good solutions posted in the archives. www.adsm.org Jon -Original Message- From: Block, Clemens [mailto:[EMAIL PROTECTED]] Sent: Monday,