The following table shows the collected content of performance trace information.

Table 28-1 Collected content of performance trace information

No.	Item	Collected content
1	IP address	IP address of the server machine from which the trace was collected
2	Process ID	Process ID from which the trace was collected
3	Server name, process name	Server name (user server name) or process name from which the trace was collected For details about process names, see Table 28-2 Main collection points for performance trace information (during execution of SQL code).
4	Thread ID	Thread ID within the process from which the trace was collected
5	Trace collection time	Time at which the trace was collected (down to microseconds#1)
6	Performance trace sequence number	Performance trace sequence number within a process
7	Event ID	ID indicating the event content For details about event IDs, see Table 28-2 Main collection points for performance trace information (during execution of SQL code).
8	Client IP address	Client's IP address#2
9	Client process ID	Client's process ID#2 0 is output if the connection was made from a Type4 JDBC driver.
10	Client port number	Client's receiving port number#2
11	Client connect sequence number	Client's connect sequence number#2
12	Performance attachment ID	ID that is unique within HiRDB#3 This ID is output in the following format: aaaabbbbbbbb aaaa: Name of the unit where the connected FES is located bbbbbbbb: Connect sequence number (hexadecimal)
13	Performance user information	When integrated with Hitachi Application Server: Root application information#3 This information is output in the following format: aa....aa/bb....bb/cc....cc aa....aa: Identifier bb....bb: Process ID cc....cc: Communication number Other: Maintenance information#3
14	Unique data	Maintenance information

#1

The time precision depends on the platform.

#2

Collected when there is client application information. However, 0 or 0.0.0.0, indicating that no information has been collected, might be output in some cases even when there is no client application information.

#3

Collected when there is performance-included information.