Troubleshooting
Problem
After a EXTEND DBSPACE process completes, a DB2 rebalance process needs to be started. Sometimes it could hang/stop unexpectedly.
Symptom
The "db2 list utilities show detail" or "db2pd -utilities" does not show any rebalance is running.
Cause
There is an internal DB2 registry called REBALANCER wrongly set to OFF.
Diagnosing The Problem
When a rebalance DB2 process is started (manually redistributing/reclaiming data or automatically, following an "EXTEND DBS" process with "reclaim=yes"(*) option set), the DB2 commands:
(*)Note: the "reclaim=yes" options is available only since Server version V7
"db2 list utilities show detail"
or
"db2pd -utilities"
can be used to monitor the DB2 rebalance status.
If no data is returned, it could mean the rebalance is not properly working.
For example, running :
$db2 list utilities show detail
it will show:
SQL1611W No data was returned by Database System Monitor.
SQLSTATE=00000
while it should show :
Also, despite the following DB2 commands which run successfully :
ALTER TABLESPACE tablespace_name REBALANCE SUSPEND;
ALTER TABLESPACE tablespace_name REBALANCE RESUME;
still the rebalance is not started.
There is absolutely no error message logged in the db2diag.log file.
Resolving The Problem
There is an internal DB2 registry which was improperly set to OFF. It's call "REBALANCER".
In order to display its value, use the DB2 command:
"db2set -all"
and in the output look for the "REBALANCER" variable value, for example:
....
[i] DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:500
[i] DB2_ALTERNATE_GROUP_LOOKUP=GETGROUPLIST
[i] DB2_SKIPINSERTED=ON
[i] DB2_OPTPROFILE=YES
[i] DB2_BCKP_PAGE_VERIFICATION=TRUE
[i] DB2_KEEPTABLELOCK=OFF
[i] DB2_EVALUNCOMMITTED=ON
[i] DB2_SKIPDELETED=ON
[i] DB2MAXFSCRSEARCH=5
[i] DB2NOEXITLIST=ON
[i] DB2LIBPATH=/opt/tivoli/tsm/server/bin/dbbkapi
[i] DB2ENVLIST=LIBPATH
[i] REBALANCER=OFF
[i] DB2COMM=TCPIP
[i] DB2CODEPAGE=819
[g] DB2FCMCOMM=TCPIP4
[g] DB2SYSTEM=tsmserver.rome.it
[g] DB2INSTDEF=tsminst1
The internal DB2 registries are there to be used ONLY by DB2 Support Analysts, in order to help in some critical situations and should not be used/changed casually.
This being an internal registry, it does not even log diagnostics in the db2diag.log as this is supposed to be used consciously by IBM DB2 Support Analysts.
In order to fix the problem, run the following steps:
- from a DB2 command prompt, using the DB2 instance owner, run:
db2 connect to TSMDB1
db2 set schema TSMDB1
db2set REBALANCER=
- Restart DB2 by issuing :
db2stop / db2start
That will restart the rebalance process and should complete the DB2 tablespace rebalance.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21986604