DBS configuration

The database administrators must configure a set of associated resources for the DBS environment. SQL/MX will not make any assumptions about user resources.

To configure the DBS environment, the user must provide the configuration specifications for:
  • General items like users, user groups, CPUs, and MXCS services

  • Data volumes

The InstallDBS script processes the configuration specifications and configures the available resources. The DBS configuration is in the form of a set of shell export commands that set variables with predefined names to reflect the desired configuration. The DBS configuration specifications are optional. If not specified, the InstallDBS script will consider the default configuration settings.

Configuration metadata

Information regarding the configured resources for DBS are stored in a dedicated SQL/MX metadata tables. Allocated resources and user information are stored in the SQL/MX metadata tables. For example, users associated with individual databases. The SYSTEM_DBS_SCHEMA in the system catalog contains the following metadata tables storing the DBS configuration information:

    Global information for the DBS environment like global DBS administrator information.

    MXOAS processes dedicated to the DBS environment.

    CPUs configured for the DBS environment.

    Guardian users reserved for the DBS environment.

    Safeguard file-sharing groups reserved for the DBS environment.

    Data volumes reserved for the DBS environment.

    All the databases in the DBS environment.

    N:N relation between ALL_DATABASES and DBS_CPUS.

    The MXCS datasources used by the databases.

    Volumes used by individual databases.

    Privilege groups associated with individual databases.
For information on metadata tables, see SQL/MX 3.5 Release Technical Update.

Safeguard configuration

The following items are configured and reserved in Safeguard for the DBS environment.
  • Global DBS administrators

    A dedicated Guardian user group with overall management rights for all user databases. The DBS services are executed with the global DBS administrator authority. The global DBS administrators are configured with administrative capabilities.
    • In SQL/MX, global DBS administrators are configured as security administrators with CREATE CATALOG authority, and are authorized to perform DDL and Utility operations on databases.

    • In MXCS, global DBS administrators are added with operator permission.

    • In Safeguard, global DBS administrators own configured resources such as, volumes, groups, users and file-sharing group, and are authorized to manage these resources.

    • In NSK, global DBS administrators can create and manage persistent processes.
    The global DBS administrators are not authorized to access user data in the databases.
  • Initial DBS administrator user

    A user in the global DBS administrators group, to be added during configuration, who will own all of the following items:
    • Volumes

      Each configured volume is added to Safeguard.

    • File-sharing group

      Each configured file-sharing group is added to Safeguard with a predefined name.

    • User Group

      Each configured Guardian user group is added to Safeguard with a group name. 250 users are added to each group with predefined usernames.

MXCS configuration

Two MXCS services are added to the MXCS configuration during DBS installation for:
  • Application access to the database. The datasource associated with each database is hosted on this service.

  • Management activities for configured global DBS administrators. A datasource named DBS_MGMT_DS is created on this service using which global DBS administrators can connect to administer the databases in DBS environment.

Each MXCS service configured for DBS consists of an MXOAS process running as a persistent NSK process.

Volume configuration

A user specified volume configuration file contains a list of volumes for DBS use. If the file is not specified, by default, all TMF data volumes are configured for DBS use except:
  • $SYSTEM and $DSMSCM, if they exist as TMF data volumes.

  • Volumes where the largest free extent is less than 10 gigabytes.

For the sample volume configuration, see sample volume configuration.