 |
» |
|
|
 |
Ask the Wizard Questions
database won't come up after shutdown
The Question is:
I am running ADABAS database in a Vax 4000-500 platforms with VMS 6.1.
the problem i am having is that once you shutdown the database it
won't come up again, unless you reboot the VAX. An insufficient
global pages message is displayed. I increased global pages to 90000,
and the problem continues.
Any guess?.
Regard,
The Answer is:
90000 pages is not a lot. More than likely, ADABAS is using a large
global section. Use INSTALL LIST/GLOBAL/FULL to see how large it is. For
whatever reason the section is being held in memory after ADABAS
shutdown or perhaps the free pages are being fragmented. Use
F$GETSYI("CONTIG_GBLPAGES") to determine the largest contiguous extent
of global pages and F$GETSYI("FREE_GBLPAGES") to see the total free
space. I suggest you track global page consumption before and after
ADABAS startup and shutdown to determine exactly what it's doing.
There may also be one or 2 stray processes holding the section in
memory. Stopping the processes should free the global pages.
Once you know how large the global section is, you can determine how
many GBLPAGES to allocate in order to guarantee restarting the
database. I'd suggest allowing at least 3 times the required size as
*extra* global pages over your system's normal requirements. The GBLPAGES
parameter is quite cheap - it's not unusual to see a system with it
set higher than 200000, especially when running database applications.
|