Pipeline Startup - Thread Hash Map Size Clarifications (Doc ID 1420915.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.0 to 7.3.0.0.1 - Release: 7.3.0 to 7.3.0
Information in this document applies to any platform.

Goal

There are discrepancies observed between default values of Hash Map sizes calculated based on documentation and actual Hash Map ( INF_FINAL_*_HASH_MAP_SIZE) sizes reported within the process log file.

Below are some questions around this :

Q1: Are values for parameters “ThreadAccountHashMapSize, ThreadServiceHashMapSize, etc” in registry configured per thread or overall HashMapSize?

Q2: Are values for reported parameters “INF_REG_VALUE_*_HASH_MAP” in process log file per thread or overall HashMapSize ?

Q3: Are values for reported parameters “INF_FINAL_*_HASH_MAP_SIZE” in process log file per thread or overall HashMapSize ?

Q4: What is the relationship between configured “ThreadAccountHashMapSize” and process log reported INF_REG_VALUE_ACCOUNT_HASH_MAP and INF_FINAL_ACCOUNT_HASH_MAP_SIZE ?

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