Disk group configuration guidelines <a class="indexterm" name="id406698"></a><a class="indexterm" name="id406705"></a>


Disk group configuration guidelines
Prev	About setting up a disk group	Next

Disk group configuration guidelines

Follow these guidelines when setting up disk groups:

Only disks that are online and do not already belong to a disk group can be used to create a new disk group.
Create one disk group for each database.

The disk group name must be unique. Name each disk group using the DB2 database name specified by the environment variable $DB2DATABASE and a dg suffix. The dg suffix helps identify the object as a disk group. Also, each disk name must be unique within the disk group.

Note:

Users should not share a disk group between different DB2 instances. Although it is not recommended, sharing a disk group among all databases in the same instance may make sense if the instance contains several small databases. In this case, name the disk group using the DB2 instance name specified by the environment variable $DB2INSTANCE and a dg suffix.

Never create container files using file systems or volumes that are not in the same disk group.

In earlier releases of Veritas Volume Manager, a system installed with VxVM was configured with a default disk group, rootdg, that had to contain at least one disk. VxVM can now function without any disk group having been configured. Only when the first disk is placed under VxVM control must a disk group be configured.

Note:

Most VxVM commands require superuser or equivalent privileges.

See About tuning VxVM .