Table 3-1 Collection level determined by the value of the pd_prf_level operand and the information that is collected
pd_prf_level operand value | Collection level | Positioning | Information that is collected |
---|---|---|---|
00000007 (Minimum level) | 00000004 | Provides the minimum amount of information. | Traces of CONNECT operation, utility execution, and specific events |
0000001f (Default level) | 00000004, 00000010 | Allows the boundaries with HiRDB (entry and exit) to be identified. | Traces mostly before and after communication with HiRDB in addition to the traces obtained at the minimum level |
0000007f (Detail level) | 00000004, 00000010, 00000040 | Provides the information required for tracing SQL processing. | Traces that can be used to check the flow of HiRDB's internal processing in addition to the traces obtained at the default level |
000001ff (Maintenance level) | 00000004, 00000010, 00000040, 00000100 | Provides the maintenance information that can be used in the event of an error. | Traces that includes iteration processing such as internal locking in addition to the traces obtained at the detail level |
00000000 (Suppression level) | Not collected | Suppresses the collection of trace data. | Not collected |
pd_prf_level operand value | Total capacity of performance trace information files | |
---|---|---|
Number of SQL statements executed per second is about 200 | Number of SQL statements executed per second is about 500 | |
00000007 | 750 MB (default value#) | 750 MB (default value#) |
0000001f | 750 MB (default value#) | 2 GB |
0000007f | 2 GB | 5 GB |