suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT20528 Status: Closed

FSALERT FILE INCORRECTLY NAMED WHEN SETTING AN ALERT WHICH RESULTS IN THE
ERROR MESSAGE: "ERROR SCANNING ALERT DIRECTORY"

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Incorrect named fsalert file leads to the error message being
displayed in db2diag.log: "Error scanning alert directory for
host"

The following entries can appear in the db2diag.log.

-- MEMBER 0 --
2015-09-12-04.55.28.205451-240 I12541254E873         LEVEL:
Error
PID     : 22877                TID : 47278889474624  PROC :
db2rocme 0 [db2sdin]
INSTANCE: db2sdin              NODE : 000
HOSTNAME: srvdb2pd1.tjms.jus.br
FUNCTION: DB2 UDB, high avail services, sqlhaIsFsAlertSet,
probe:1843
MESSAGE : ZRC=0x80000043=-2147483581=SQLZ_RC_INVPARM
          "Gen. purpose validation error.  Invalid input."
DATA #1 : String, 39 bytes
Error scanning alert directory for host
DATA #2 : String, 21 bytes
srvdb2pd1.tjms.jus.br
DATA #3 : String, 56 bytes
/db2sd_20141122012550/db2sdin/sqllib_shared/ctrlha/alert
DATA #4 : String, 30 bytes
.srvdb2pd1.tjms.jus.br.fsalert
DATA #5 : String, 0 bytes
Object not dumped: Address: 0x00007FFF386786F0 Size: 0 Reason:
Zero-length data
DATA #6 : String, 0 bytes
Object not dumped: Address: 0x00007FFF386776F0 Size: 0 Reason:
Zero-length data

2015-09-12-04.55.29.968913-240 I12542128E851         LEVEL:
Error
PID     : 22594                TID : 139769442588448 PROC :
db2instance
INSTANCE: db2sdin              NODE : 000
HOSTNAME: srvdb2pd1.tjms.jus.br
FUNCTION: DB2 UDB, high avail services, sqlhaIsFsAlertSet,
probe:1843
MESSAGE : ZRC=0x80000043=-2147483581=SQLZ_RC_INVPARM
          "Gen. purpose validation error.  Invalid input."
DATA #1 : String, 39 bytes
Error scanning alert directory for host
DATA #2 : String, 9 bytes
srvdb2pd2
DATA #3 : String, 56 bytes
/db2sd_20141122012550/db2sdin/sqllib_shared/ctrlha/alert
DATA #4 : String, 30 bytes
.srvdb2pd1.tjms.jus.br.fsalert
DATA #5 : String, 0 bytes
Object not dumped: Address: 0x00007FFF82FD6930 Size: 0 Reason:
Zero-length data
DATA #6 : String, 0 bytes
Object not dumped: Address: 0x00007FFF82FD5930 Size: 0 Reason:
Zero-length data

-- MEMBER 1 --
2015-09-12-04.42.37.534461-240 I28749053E873         LEVEL:
Error
PID     : 4466                 TID : 47963939781184  PROC :
db2rocme 0 [db2sdin]
INSTANCE: db2sdin              NODE : 000
HOSTNAME: srvdb2pd2.tjms.jus.br
FUNCTION: DB2 UDB, high avail services, sqlhaIsFsAlertSet,
probe:1843
MESSAGE : ZRC=0x80000043=-2147483581=SQLZ_RC_INVPARM
          "Gen. purpose validation error.  Invalid input."
DATA #1 : String, 39 bytes
Error scanning alert directory for host
DATA #2 : String, 21 bytes
srvdb2pd2.tjms.jus.br
DATA #3 : String, 56 bytes
/db2sd_20141122012550/db2sdin/sqllib_shared/ctrlha/alert
DATA #4 : String, 30 bytes
.srvdb2pd1.tjms.jus.br.fsalert
DATA #5 : String, 0 bytes
Object not dumped: Address: 0x00007FFF10C25370 Size: 0 Reason:
Zero-length data
DATA #6 : String, 0 bytes
Object not dumped: Address: 0x00007FFF10C24370 Size: 0 Reason:
Zero-length data

The error occurs because the hostname retrieved from the
db2nodes.cfg file is not shortened i.e. the domain name is not
removed when creating a fsalert file. This needs to be fixed.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 10.5 Fix Pack 5                               *
****************************************************************
Local Fix:
It can be safely ignored if a local fix is not available.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT12801 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.05.2017
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)