Library /sys$common/syshlp/SQL$HELP72.HLB  —  ALTER  DATABASE  Arguments  SHARED_MEMORY
    Syntax options:

       SHARED MEMORY IS SYSTEM
       SHARED MEMORY IS PROCESS
       SHARED MEMORY IS PROCESS RESIDENT

 Determines whether database root global sections (including global
 buffers when enabled) are created in system space or process space.
 The default is PROCESS.

    When you use global sections created in the process space, you
    and other users share physical memory and the OpenVMS operating
    system maps a row cache to a private address space for each user.
    As a result, all users are limited by the free virtual address
    range and each use a percentage of memory in overhead. If many
    users are accessing the database, the overhead can be high.

    When many users are accessing the database, consider using SHARED
    MEMORY IS SYSTEM. This gives users more physical memory because
    they share the system space of memory and there is none of the
    overhead associated with the process space of memory.

    The default is SHARED MEMORY IS PROCESS.

    When you use this clause as a cache attribute, it controls
    whether Oracle Rdb creates cache global sections in system space
    or process space. The default is PROCESS.

    The SHARED MEMORY clause determines whether database root global
    sections (including global buffers when enabled) or whether the
    cache global sections are created in system space or process
    space. The RESIDENT option extends the PROCESS option by making
    the global section memory resident.

    To enable or disable SHARED MEMORY IS PROCESS RESIDENT, the
    process executing the command must be granted the VMS$MEM_
    RESIDENT_USER rights identifier. When this feature is enabled,
    the process that opens the database must also be granted the
    VMS$MEM_RESIDENT_USER rights identifier. Oracle Corporation
    recommends using the RMU Open command when utilizing this
    feature.
Close Help