IBM Support

Why the storage group status is 0x0000000A

Technical Blog Post


Abstract

Why the storage group status is 0x0000000A

Body

Normally the storage group status is 0. The following is an example that the storage group status is set to 0x0000000A instead:

$ db2pd -d mydb -storagegroup

Database Member 0 -- Database MYDB -- Active Standby -- Up 11 days 18:50:57 -- Date 2018-02-20-11.08.11.478864

Storage Group Configuration:

Address           SGID Default DataTag   Name

0x00003FFD04642820 0    Yes     0         IBMSTOGROUP

Storage Group Statistics:

Address           SGID State     Numpaths NumDropPen

0x00003FFD04642820 0    0x0000000A 2        0

Storage Group Paths:

Address           SGID PathID   PathState   PathName

0x00003FFD04666000 0    0        InUse       /path1

0x00003FFD04668000 0    1        InUse       /path2

 

The state 0x0000000A of storage group is a combination of the following two flags:

* 0x0000000000000002 - SQLB_STORAGEGROUP_SKIP_ALTERS
* 0x0000000000000008 - SQLB_STORAGEGROUP_REDEFINE_CONTAINERS

 

Other possible values are documented at the following link:

https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0011729.html#r0011729__pdstorinfo

These flags may be turned on when you restore the database to set up HADR and storage group has been redefined
using "ON..."option or other ways that redefine the storage group.

 

[{"Business Unit":{"code":"BU029","label":"Data and AI"}, "Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11140202