Current situation
Currently, when PE Agent for DB2 Connect Monitoring is not working as expected, customers must check the agent log file (e2elog.DB2) in the corresponding instances directory. The messages in this log are not self-explanatory and do not allow customers to determine the status of an agent that is running, or sending collected performance data to the registered host subsystems.
New agent start-up messages
With PK58391 a set of new status messages is introduced to help customers identify the status of each registered server.
The following sections provide some examples based on some potential error scenarios.
Proper configuration messages
The following lists typical messages that should be displayed on the command line at agent startup, if the configuration is correct.
c:\Program Files\IBM\IBM DB2 Performance Expert Agent V3\bin>e2e --start
IBM(c) Performance Expert Agent.
1: [2008-05-20 15:12:43.687] Performance Expert Agent is started.
2: [2008-05-20 15:12:43.687] Build level : E7024
3: [2008-05-20 15:12:43.843] Checking configured servers in the 'e2e.ini' file...
4: [2008-05-20 15:12:45.093] Server configuration 'BOEOMP1, D6573219' accepted.
5: [2008-05-20 15:12:46.000] Server configuration 'BOEOMP1, D8949172' accepted.
6: [2008-05-20 15:12:48.265] Server configuration 'BOEOMP1, D9141110' accepted.
7: [2008-05-20 15:12:48.281] --------------------------------------------------
8: [2008-05-20 15:12:48.281] The following servers are active :
9: [2008-05-20 15:12:48.296] BOEOMP1 5711 OMP1D711 D6573219 MTS
10: [2008-05-20 15:12:48.296] BOEOMP1 5811 OMP1D811 D8949172 MTS
11: [2008-05-20 15:12:48.296] BOEOMP1 5090 OMPDB2I D9141110 MTS
12: [2008-05-20 15:12:48.312] --------------------------------------------------
Each message starts with a timestamp. Following the timestamp is the message text.
Line 1 shows that the agent has started.
Line 2 indicates which agent build level the customer is running. This is important information for problem determination.
In line 3, the agent starts to check which servers are configured in the e2e.ini file, and lists in lines 4 through 6 that three servers have been accepted.
Lines 8 thru 11 display summary information for the three accepted servers. Lines 9 thru 11 list the Host name, DB2 port number, DB2 location name, generated alias name and user ID used to log on for each configured server.
Once line 12 is displayed the agent is up and running and reporting collected performance data to all three servers.
Agent refresh messages
The agent re-reads the ini file every 10 minutes. Servers can be added or removed and configuation errors can be corrected while the agent is running. Current status messages will appear starting with:
3: [2008-05-20 15:12:43.843] Checking configured servers in the 'e2e.ini' file...
On a system with three correctly configured and active servers, messages like the following will appear in the first 15 minutes:
c:\Program Files\IBM\IBM DB2 Performance Expert Agent V3\bin>e2e --start
IBM(c) Performance Expert Agent.
1: [2008-05-20 15:12:43.687] Performance Expert Agent is started.
2: [2008-05-20 15:12:43.687] Build level : E7024
3: [2008-05-20 15:12:43.843] Checking configured servers in the 'e2e.ini' file...
4: [2008-05-20 15:12:45.093] Server configuration 'BOEOMP1, D6573219' accepted.
5: [2008-05-20 15:12:46.000] Server configuration 'BOEOMP1, D8949172' accepted.
6: [2008-05-20 15:12:48.265] Server configuration 'BOEOMP1, D9141110' accepted.
7: [2008-05-20 15:12:48.281] --------------------------------------------------
8: [2008-05-20 15:12:48.281] The following servers are active :
9: [2008-05-20 15:12:48.296] BOEOMP1 5711 OMP1D711 D6573219 MTS
10: [2008-05-20 15:12:48.296] BOEOMP1 5811 OMP1D811 D8949172 MTS
11: [2008-05-20 15:12:48.296] BOEOMP1 5090 OMPDB2I D9141110 MTS
12: [2008-05-20 15:12:48.312] --------------------------------------------------
13: [2008-05-20 15:23:53.843] Checking configured servers in the 'e2e.ini' file...
14: [2008-05-20 15:23:55.093] Server configuration 'BOEOMP1, D6573219' accepted.
15: [2008-05-20 15:23:56.000] Server configuration 'BOEOMP1, D8949172' accepted.
16: [2008-05-20 15:23:58.265] Server configuration 'BOEOMP1, D9141110' accepted.
17: [2008-05-20 15:23:58.281] --------------------------------------------------
18: [2008-05-20 15:23:58.281] The following servers are active :
19: [2008-05-20 15:23:58.296] BOEOMP1 5711 OMP1D711 D6573219 MTS
20: [2008-05-20 15:23:58.296] BOEOMP1 5811 OMP1D811 D8949172 MTS
21: [2008-05-20 15:23:58.296] BOEOMP1 5090 OMPDB2I D9141110 MTS
22: [2008-05-20 15:23:58.312] --------------------------------------------------
No servers configured message
If you have not configured any servers you will see the following output when the agent is started:
c:\Program Files\IBM\IBM DB2 Performance Expert Agent V3\bin>e2e --start
IBM(c) Performance Expert Agent.
[2008-05-20 15:24:19.625] Performance Expert Agent is started.
[2008-05-20 15:24:19.625] Build level : E7024
[2008-05-20 15:24:19.781] Checking configured servers in the 'e2e.ini' file...
[2008-05-20 15:24:20.546] WARNING: No active servers found on the DB2 gateway.
Incorrect password message
In the following scenario one server is configured, but the password specified during configuration was wrong. Server processing is paused.
c:\Program Files\IBM\IBM DB2 Performance Expert Agent V3\bin>e2e --start
IBM(c) Performance Expert Agent.
[2008-05-20 15:29:23.281] Performance Expert Agent is started.
[2008-05-20 15:29:23.281] Build level : E7024
[2008-05-20 15:29:23.421] Checking configured servers in the 'e2e.ini' file...
[2008-05-20 15:29:24.343] ERROR: Cannot establish connection to the server
'BOEPMO1, D0113126' : SQL30082N Attempt to establish
connection failed with security reason "15"
("PROCESSING FAILURE"). SQLSTATE=08001, SQLState=<08001>,
ErrorCode=<-30082>.
[2008-05-20 15:29:24.359] ERROR: The server 'BOEPMO1, D0113126' is changed
from active mode to paused mode.
[2008-05-20 15:29:24.359] WARNING: No active servers found on the DB2 gateway.
To resolve this, you can use the e2e --change command to change the password. On Windows, you can also use the Configuration GUI to change the password. You do not need to stop and restart the agent. The agent checks periodically (every ten minutes) for updates in the e2e.ini file.
If the password is corrected, the next time the agent refreshes the following messages will appear:
….
[2008-05-20 15:29:24.359] WARNING: No active servers found on the DB2 gateway.
[2008-05-20 15:39:24.421] Checking configured servers in the 'e2e.ini' file...
[2008-05-20 15:39:25.218] Server configuration 'BOEPMO1, D0113126' accepted.
[2008-05-20 15:39:25.500] --------------------------------------------------
[2008-05-20 15:39:25.500] The following servers are active :
[2008-05-20 15:39:25.500] BOEPMO1 5711 PMO1D711 D0113126 MTS
….
Incorrect configuration messages
For the PE Agent for DB2 Connect Monitoring to work correctly, you need to set up the server properly. Otherwise, when you start the agent, you see the following error messages in the new log output.
Example 1: No Tables created at all
[2008-05-20 15:55:46.015] ERROR: Cannot access tables of the performance database on
the server 'BOEOMP1, D1724876' : DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: DB2PM.VERSION, SQLState=<42704>, ErrorCode=<-204>. SQLCA=<
Example 2: Tables created, but configuration not OK (History disabled)
…
[2008-05-20 16:04:14.000] WARNING: The history collection flag is not set on the server
'BOEOMP6, D2222563'. The server is paused. Set the startup
parameter PERFORMANCEWAREHOUSE=Y to create DB2 tables.
Grant DB2 privileges. Set the parameters SNAPSHOTHISTORY=Y,
SHDB2CONNECTAPPLICATION and SHDB2CONNECTSYSTEM for the
collection of history data. Optionally, set the parameter
AUTOMATICAGENTUPDATE=YES to activate the automatic update
function for Performance Expert Agent.
…
Runtime error messages
This PTF also includes new messages that indicate runtime errors.
Example 1: Server not up and running to retrieve snapshot data
….
[2008-05-20 15:39:25.500] --------------------------------------------------
[2008-05-20 15:39:25.500] The following servers are active :
[2008-05-20 15:39:25.500] BOEPMO1 5711 PMO1D711 D0113126 MTS
[2008-05-20 15:39:25.500] --------------------------------------------------
[2008-05-20 15:40:27.796] ERROR: Cannot store application data to the performance
database of the server 'BOEPMO1, D0113126'. Waiting for the
next collection interval...
[2008-05-20 15:41:26.984] ERROR: Cannot store system data to the performance database
of the server 'BOEPMO1, D0113126'. Waiting for the next
collection interval...
….
Example 2: Missing GRANTs for user MTS
…
[2008-05-20 15:52:09.578] ERROR: Cannot access tables of the performance database on
the server 'BOEOMP1, D1505547' : DB2 SQL error: SQLCODE: -551,
SQLSTATE: 42501, SQLERRMC: MTS;SELECT;DB2PM.VERSION,
SQLState=<42501>, ErrorCode=<-551>.
SQLCA=<MTS DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
SELECT ON OBJECT DB2PM.VERSION>.
…
Agent shutdown message
When the agent is stopped the following message is displayed:
[2008-05-20 15:24:06.609] Performance Expert Agent is stopped.
Improved agent JDBC connection handling
Configuring multiple servers on a single gateway can cause significant overhead during processing as database connections were frequently opened and closed.
With PK58391 the agent code has been improved so that the JDBC connections are not closed if the specified interval between collections is less than or equal to 30 seconds.
If you select intervals of 10 seconds or less the agent might return messages indicating that a duplicate insert has occurred. This is because the agent needs more time to collect the information then the server needs to consume it. This will result in the previous snapshot being displayed and logical gaps in the history.
Note:
The agent modifies the following db2 monitoring switches of the db2 instance, where it runs: DFT_MON_STMT and DFT_MON_UOW will be set to ON.
In case the local db2 could not modify the switches dynamically, restart the db2 instance so that the monitoring switches take effect. Check the current state of monitoring switches issuing "db2 get dbm cfg show detail" command on the db2 instance where the agent runs.
| 
