DB2 10.5 for Linux, UNIX, and Windows

Configuring PVIDs for a DB2 pureScale instance (AIX)

The shared disk to be used by the DB2® pureScale® instance must have the same physical volume identifier (PVID) configured on all hosts.

About this task

The shared disk on all the hosts must have the same PVID configured for the tiebreaker disk and the disks used for the DB2 managed shared file system and must be accessible on all the hosts for instance setup. You need to perform these steps on each host you want to participate in the DB2 pureScale instance for the tiebreaker disk and the disks used for the DB2 managed shared file system.

Procedure

Use the lspv command to list existing hdisk names (such as device names or physical volumes) and PVIDs. For example:

lspv
hdisk0          00c931e42dcf6ce4                    rootvg          active
hdisk1          00c931c447f3d4a9                    gpfs
hdisk2          00c931c447f3d4f2                    None
hdisk3          00c931c447f3d517                    None
hdisk4          00c931c447f3d53b                    None
hdisk5          00c931c447f3d561                    None
hdisk6          00c931c447f3d589                    None
hdisk7          00c931c447f3d5ac                    None
hdisk8          00c931c447f3d5d6                    None
hdisk9          none                                None

To assign a PVID to a disk in the storage array, run the following command:

   chdev -l <disk_name> -a pv=yes

For example, for hdisk9, you would run the following command:

   chdev -l hdisk9 -a pv=yes

which would return the following output for the lspv command:

lspv
hdisk0          00c931e42dcf6ce4                    rootvg          active
hdisk1          00c931c447f3d4a9                    gpfs
hdisk2          00c931c447f3d4f2                    None
hdisk3          00c931c447f3d517                    None
hdisk4          00c931c447f3d53b                    None
hdisk5          00c931c447f3d561                    None
hdisk6          00c931c447f3d589                    None
hdisk7          00c931c447f3d5ac                    None
hdisk8          00c931c447f3d5d6                    None
hdisk9          00c931e4b4505651                    None

On each of the other hosts, run the following command to remove the existing disk name:

   rmdev -dl <disk_name_for_the_same_shared_disk>

which would return the following output for the lspv command:

lspv
hdisk0          00c931e42dcf6ce4                    rootvg          active
hdisk1          00c931c447f3d4a9                    gpfs
hdisk2          00c931c447f3d4f2                    None
hdisk3          00c931c447f3d517                    None
hdisk4          00c931c447f3d53b                    None
hdisk5          00c931c447f3d561                    None
hdisk6          00c931c447f3d589                    None
hdisk7          00c931c447f3d5ac                    None
hdisk8          00c931c447f3d5d6                    None

Run the cfgmgr command. When the cfgmgr command is run, without a PVID assigned, the system will retrieve the PVID from the storage array (set in step 2). Running the lspv command will return the following output:

lspv
hdisk0          00c931e42dcf6ce4                    rootvg          active
hdisk1          00c931c447f3d4a9                    gpfs
hdisk2          00c931c447f3d4f2                    None
hdisk3          00c931c447f3d517                    None
hdisk4          00c931c447f3d53b                    None
hdisk5          00c931c447f3d561                    None
hdisk6          00c931c447f3d589                    None
hdisk7          00c931c447f3d5ac                    None
hdisk8          00c931c447f3d5d6                    None
hdisk9          00c931e4b4505651                    None