OpenVMS Alpha 7.2-1 & Rdb 7.0

[Enemy]

Error when opening Rdb database on _Alpha_
$rmu/open sql$database
%RDMS-F-CANTOPENDB, database could not be opened as requested
-RDMS-F-CANTCREGBL, error creating and mapping database global section
-SYSTEM-F-INSFSPTS, insufficient SPTEs available
%RMU-W-CANTOCDB, Error encountered while opening or closing database file
DISK02:[GUS_DB.][VOF_DATABASE]VOF.RDB;1
---

INSFSPTS, insufficient SPTEs available
Facility: SYSTEM, System Services
Explanation: There are too few system page table entries to map a process
buffer to the system.
User Action: Reboot the system and increase the SYSGEN parameter SPTREQ.
---
SPTREQ

(VAX only) SPTREQ sets the number of system page table (SPT)
entries required for mapping the following components

[faris_3]

Hi,

If you open/close databases or use tools which dynamically allocate system space
you may fragment your system space.

You can use (to anticipate the problem)
SDA> CLUE MEM/LAYOUT
System Space Expansion Region FFFFFFFF.8C000000 FFFFFFFF.FFDF0000

or he following tool to get more details
about the free fragments :

http://h18000.www1.hp.com/support/asktima/communications/CHAMP_SRC030312000607.html


You may try to use a MAX_NPAGEVIR to limit
max non paged pool to a smaller value than
normally set by autogen.
On a stable system NPAGEVIR = 2 * NPAGEDYN
may be enough and will give more system space expansion room.
hth,
/hf

[John Gillings]

Best option - upgrade to V7.3-2 (page table space moves into the S2 region and is no longer constrained by 32 bit address space).

Otherwise you need to reduce demands on S0 and S1 space. See:

SDA> CLUE MEMORY/LAYOUT
SDA> SHOW PAGE/FREE/S0S1

If you can't upgrade to V7.3-2, then try reducing one or more of BALSETCNT, NPAGEVIR, WSMAX or VCC_MAXSIZE.