Multiple Web Response Time summary records with the same timestamp

The problem: In the WRT_Transaction_Over_Time_H table, you might observe two or more summary records with the same timestamp for the same application, transaction, server, and client.

The solution: Suppose you are using the Web Response Time (WRT) agent to monitor multiple web sites through a load balancer frontend. Consequently, the transactions are reported for the same server (IP address). In the WRT_Transaction_Over_Time_H table in the Tivoli Data Warehouse (TDW), you observe two or more summary records with identical information in the following columns:

ORIGINNODE == 'ITCAMWRMAGENT:T5'
TMZDIFF == '18000'
APPLICATIN == 'CLAIMS'
TRANSACTN == 'MAINAPP'
CLIENT == 'All Clients'
SERVER == 'ip-address'

Here, the RootUUID and the response time data are different in each summary row. To simplify the explanation of this issue and the workaround, suppose that you are only monitoring this one application, transaction, and IP address. For example:

Samples Timestamp RootUUID
4 1100114120000000 5AF6E9EAE98C6074501E6F92E1CF5261
7 1100114120000000 BDAD76C3410C7128EF11F994D0A4F993

This issue is fixed in the following fix packs. See APAR IZ67167 (WRT WORKSPACE DISPLAYS DUPLICATE AVERAGES FOR SAME AGGREGATION):

ITCAM for Transactions 7.1 Fix Pack 4 (7.1.0.0-TIV-CAMRT-FP0004)
ITCAM for Transactions 7.2 Fix Pack 1 (7.2.0.0-TIV-CAMRT-FP0001)

Manual workaround: You can resolve this issue by removing RootUUID as a primary key in the dockt5 file:

Make a backup copy of the dockt5 file under ITM_HOME\CNPS (Windows) or under ITM_HOME/arch/cq/data (UNIX) on the Tivoli Enterprise Portal Server host.
Open the dockt5 file in a plain text editor.

Locate the following block in the dockt5 file:

*REM: ******************************************************************
*REM: ** T5TXOT
*REM: ** WRT Transaction Over Time Table
*REM: **
*REM: ******************************************************************

Scroll down and find *OPTION: PRIMARYKEY=x entries, where x is a sequentially incremented number. The following are the primary keys identified in dockt5 for the WRT Transaction Over Time table:
```
APPLICATIN
TRANSACTN
CLIENT
SERVER
ROOTUUID 
```
For example:
```
*ATTR: RootUUID
*CAPTION: RootUUID
*COLUMN: ROOTUUID
*NLSID: KT54238
*TYPE: S,32
*DSPORDER: 34
*OPTION: PRIMARYKEY=4
RootUUID 
```
In the block containing '*COLUMN: ROOTUUID', delete or comment out the line containing '*OPTION: PRIMARYKEY=4'.
Restart the Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server.

Note: In WRT aggregation records, you might notice that the transaction count with the same ROOTUUID is often greater than 1. The ROOTUUID is a calculated value that is used to identify the edge transaction. However, these ROOTUUID values are not necessarily unique during the same aggregation interval. If the WRT agent encounters the exact same edge transaction (that is, with the same application, transaction, server, and client), the transaction will have the same ROOTUUID. So in a given collection interval (5 minutes by default), it is possible for a single transaction to be seen more than once. This transaction, then, would have counts greater than 1.