Fixes are available
APAR status
Closed as program error.
Error description
When DB2 is installed in a directory whose name is longer than 52 characters, the DB2 agent does not start. Attempts to start the agent fail with this message: KCIIN0206E Could not start/stop agent : java.util.NoSuchElementException In a complete install trace (TRACE_LEVEL=DEBUG_MAX), we can see that the underlying cause is that db2level splits lines that are longer than 80 bytes: 2011-08-23 10:55:59.989+01:00 ITMinstall.Utilities execCmd1 [DEBUG_MID] Entry, parm 1 = /opt/IBM/ITM/bin/ITMLangC db2ecdea db2level 2011-08-23 10:56:01.075+01:00 com.ibm.tivoli.monitoring.install.utils.process.StreamReader run [DEBUG_MAX] STDOUT: DB21085I Instance "db2ecdea" uses "64" bits and DB2 code release "SQL09074" 2011-08-23 10:56:01.076+01:00 com.ibm.tivoli.monitoring.install.utils.process.StreamReader run [DEBUG_MAX] STDOUT: with level identifier "08050107". 2011-08-23 10:56:01.077+01:00 com.ibm.tivoli.monitoring.install.utils.process.StreamReader run [DEBUG_MAX] STDOUT: Informational tokens are "DB2 v9.7.0.4", "s110330", "IP23236", and Fix Pack 2011-08-23 10:56:01.078+01:00 com.ibm.tivoli.monitoring.install.utils.process.StreamReader run [DEBUG_MAX] STDOUT: "4". 2011-08-23 10:56:01.079+01:00 com.ibm.tivoli.monitoring.install.utils.process.StreamReader run [DEBUG_MAX] STDOUT: Product is installed at 2011-08-23 10:56:01.080+01:00 com.ibm.tivoli.monitoring.install.utils.process.StreamReader run [DEBUG_MAX] STDOUT: "/apps/ECOMMERCE-DEV/db2/DB2ECDEA/product/db2_v9.7_fp4". 2011-08-23 10:56:01.081+01:00 com.ibm.tivoli.monitoring.install.utils.process.StreamReader run [DEBUG_MAX] STDOUT: 2011-08-23 10:56:01.082+01:00 ITMinstall.Utilities execCmd1 [DEBUG_MID] Exit 2011-08-23 10:56:01.114+01:00 ITMinstall.CandleAgent main [LOG_INFO] Could not start/stop agent : java.util.NoSuchElementException (traceKey:1314089761084) We confirmed with DB2 support that the db2level command has RECREATE INSTRUCTIONS: 1. Install DB2 in a directory whose name is > 52 characters. 2. Install and configured DB2 agent. 3. Attempt to start DB2 agent.
Local fix
Problem summary
DB2 agent will not start when DB2 has long install path. When the DB2 application is installed into a directory with an install path greater that 52 characters, the DB2 Monitoring agent will fail to start with the following message: KCIIN0206E Could not start/stop agent : java.util.NoSuchElementException
Problem conclusion
The code was modified to handle a long install path for the DB2 application. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.2-TIV-ITM-FP0008 | fix pack | 6.2.3-TIV-ITM-FP0002
Temporary fix
Comments
APAR Information
APAR number
IV07884
Reported component name
OMEG DIST INSTA
Reported component ID
5608A41CI
Reported release
622
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-16
Closed date
2011-11-22
Last modified date
2012-05-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
OMEG DIST INSTA
Fixed component ID
5608A41CI
Applicable component levels
R622 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"622","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 November 2022