How To Set A Timeout On DM For Long Queries -Database_Request_Timeout_Duration (Doc ID 790820.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.0 to 7.3.1.0.0 [Release 7.0.0 to 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 04-Nov-2012***
***Checked for relevance on 4-MAR-2015***

Goal

In case the DM_ORACLE is waiting for the return of a statement from the database, the Out-Of-The-Box configuration is such that the DM will wait endlessly until the database returns.

There are cases where a timeout in this process is needed, to stop the DM waiting for the database.

An example is an operation which has already been timed-out on the client application, hence leaving orphan session on the CM, DM and DB.

Another example could be a very long query on the database within a real-time, or CRM scenario, which should be terminated after a predefined maximum wait time.

Note that while the DM is waiting for the DB to return from the statement call, a DM backend session will be reserved for that statement and this session is unavailable to the rest of the system.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms