DB2 - Problem description
| Problem IC80392 | Status: Closed |
MEANINGLESS EVENT RECORD MIGHT BE LOGGED IN WINDOWS APPLICATION EVENT LOG | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
When DB2 Remote Command Server Service starts up in Windows
environment,
a meaningless event record might be logged in Windows
Application Event Log.
The following is an example of the event record in XML format.
<Event
xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="DB2REMOTECMD_DB2COPY1" />
<EventID Qualifiers="49152">1</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-11-09T13:26:00.000000000Z" />
<EventRecordID>12762</EventRecordID>
<Channel>Application</Channel>
<Computer>mycomputer.ibm.com</Computer>
<Security />
</System>
<EventData>
<Data>rcmdTcpipListener</Data>
<Data>Failed to configure listener's socket address. Check
for
port (db2ccmsrv) in SERVICES file, rc = 118423736.</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
The customer can ignore the above record safely. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 Server on Windows platform. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V9.7 Fix Pack 6. * **************************************************************** | |
| Local Fix: | |
The user can disable auto start-up of DB2 Remote Command Server Service if it is not used. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in Version 9.7 Fix Pack 6. | |
| Workaround | |
The user can disable auto start-up of DB2 Remote Command Server Service if it is not used. | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84468 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.12.2011 05.06.2012 05.06.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|