DB2 - Problem description
| Problem IC99915 | Status: Closed |
HADRV10_MONITOR.KSH FAILING DUE TO .BASHRC ENTRIES | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
hadrV10_monitor.ksh calls "su -" here:
hdrRole=$(su - ${candidate_P_instance} -c "db2pd -hadr -db
${DB2HADRDBNAME?}" | egrep "^Primary |^Standby |not
activated|not active" | awk '{print $1}')
This will also trigger .bashrc/.kshrc/.profile.
In case, eg .bashrc contains a db2pd command too, like "db2pd
-db <dbname> -hadr", hdrRole will contain duplicate entries and
subsequent check
if [[ $hdrRole == "Primary" ]]; then
will fail.
The script needs to take into account that customer might have
outputs in their .bashrc that can conflict. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All using HADR * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 5. * **************************************************************** | |
| Local Fix: | |
| Solution | |
First fixed in DB2 Version 10.1 Fix Pack 5. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.03.2014 14.07.2015 14.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|