The maximum time for accessing Oracle can be set as a timeout value, for the time it takes to collect 1 record.
When record data is collected while Oracle and the machine are experiencing heavy load, it may take a significant amount of time to perform record collection, depending on the amount of data collected. In this case, PFM - RM for Oracle requests may impact Oracle operation. As such, a timeout value can be set to cancel requests from PFM - RM for Oracle to Oracle, to prevent impact on Oracle operation.
Record collection is performed in the following order for each record:
However, when a timeout value is set, and a timeout occurs during Oracle access, collection for that record is canceled.
This facility is implemented using the OCIBreak function of the Oracle OCI (Oracle Call Interface).
The timeout value can be set as follows:
The values that can be set are 0, or anything from 10 to 3,600 (in seconds). If 0 is specified, this facility is not used. Out-of-range values will be disregarded. 0 is set as the default.
The following table lists the values that can be entered as timeout values, for each setting method.
Table 2-33 Possible timeout values
Setting method | Value input | ||||
---|---|---|---|---|---|
-1 or less | 0 | 1 to 9 | 10 to 3,600 | 3,601 or more | |
Setting/update from the jpcconf inst setup command | Input error (cannot be input) | Yes | Yes, but replaced on restart | Yes | Input error (cannot be input) |
Change from PFM - Web Console | Yes, but not updated | Yes | Yes, but not updated | Yes | Yes, but not updated |
For details about the timeout values set by the jpcconf inst setup command, see 2.1.4(3) Set up an instance environment.
Note that the following records are not subject to cancellation:
When a timeout occurs, the following message is output to the common log (agtoinf0x.log) of the agent log.
KAVL18636-I
The cancellation of the record collection (record-name) by the time-out was accepted.
Note that when records are not collected due to cancellation, a KAVL18401-W message is output to the common message log.
When a collection of multiple records, such as historical data, is performed at the same time, even if a timeout occurs for a single record, collection of other records is not performed.
In the following cases, a record collection is not canceled even when a cancellation request occurs due to a timeout: