1. Configuration Reference for Oracle Essbase
  2. Essbase Configuration Settings
  3. Config Settings List
  4. LONGREQTIMETHRESHOLD

LONGREQTIMETHRESHOLD

The LONGREQTIMETHRESHOLD configuration setting enables you to log informational messages for long-running requests sent to the Essbase application. Specify the upper-limit request execution time, in seconds, before which you want to enable tracking.

Syntax

LONGREQTIMETHRESHOLD n

where n is the upper-limit execution time, in seconds, before which Essbase tracks the requests and logs alert messages. Default: 0 seconds (request tracking is turned off). Minimum: 60 seconds (if using request tracking).

Description

The logged messages include the following information.

  • REQ_ID: a unique number used to identify a request

  • REQ_INFO: a string describing the type of request (for example, Calculation, Data-load)

  • REQ_STATE: a string describing the current state of the request when this message is logged (for example, started, in_progress, or finished)

  • EXEC_TIME: time, in milliseconds, that the request has been running

  • LEVEL0_BLOCKS: number of level 0 blocks at the time the message is logged. Essbase only logs this information for requests that could potentially change the cube.

  • TOTAL_BLOCKS: number of total blocks at the time the message is logged. Essbase only logs this information for requests that could potentially change the cube.

Example

LONGREQTIMETHRESHOLD 600

Specifies message logging for requests running 600 seconds or longer.

The following request-pending message in the log shows that request [REQ_ID: 109] has been running for 650232 milliseconds. Therefore, it is considered a long-running request.

[2020-01-18T17:31:03.667-08:00] [Sample] [NOTIFICATION:16] [REQ-451] [REQ] [ecid: 1484789397502,0] [tid: 9664]  
[DBNAME: Basic] [REQ_ID: 109] [REQ_INFO: Calculate] [REQ_STATE: in_progress] [EXEC_TIME: 650232]