Author: Reinhard Mersch <mersch AT UNI-MUENSTER DOT DE>
Date: Mon, 12 Feb 2001 11:01:40 +0100
Mahesh, perhaps you are just too impatient? I have also seen startup times in the range of 15 minutes, and our DB is only half the size of yours, the recovery log is much smaller than yours. This was
... ... Their first initiative should have been to find out what the problem is. See what in-depth analysis you can do. Follow the suggestions in Reinhard Mersch's posting about start-up times vs. da
Author: James Thompson <mezron AT HOTMAIL DOT COM>
Date: Mon, 12 Feb 2001 11:40:31 -0700
What is your dbbufpoolsize and logpoolsize? When these values are large, it takes a while for the dsmserv process to claim all that RAM. If it does eventually come up, then you can try changing this
Author: Mahesh Babbar <mahesh.babbar AT ST DOT COM>
Date: Wed, 17 Jan 2001 01:12:31 +0530
Hello, My ADSM server is not starting. When I manually run 'dsmserv' command , it just stucks with the messages displayed as following: -- Cut Here -- %dsmserv ANR7800I DSMSERV generated at 23:08:28
Author: "Talafous, John G." <Talafous AT TIMKEN DOT COM>
Date: Wed, 17 Jan 2001 08:15:13 -0500
Make sure your recovery log has been correctly allocated on the volume. Also, you need and entry in the dsmserv.dks configuration file. This file will differ depending on your environment. Good Luck!