Discrepancy Between BRM Documentation And DM Pin.conf : Stmt_cache_entries Parameter
(Doc ID 1486868.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.3.0]
Information in this document applies to any platform.
In BRM 731 documentation, below is mentioned about the parameter "stmt_cache_entries" at "Installation Guide · Getting started with BRM installation . Database configuration and tuning"
A minimum number for open_cursors is 1080. There is no penalty, however, for having this parameter set to a high value.
Set open_cursors to match the value of the stmt_cache_entries entry in the DM Oracle configuration (pin.conf) file. If using a statement cache size of 1080, for example, the stmt_cache_entries entry appears as follows in the DM pin.conf file:
- dm stmt_cache_entries -1080
Notice the negative value specified. Is this correct ?
And if we refer the dm_oracle pin.conf, below is the explanation about the same parameter :
# Specifies the maximum number of Oracle statement handles to cache, to
# improve Portal performance.
# The value for this entry can be:
# 0 = Disable the statement cache.
# 1 = (Default) 32
# For more details, see the online document
# "Portal Configuration and Tuning Guide."
- dm stmt_cache_entries 32
What should the user specify if one wants to have a value of 1080, given that a value of 1 means 32.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document