Exalytics and Hyperion BI+:Unable to Modify Value Of DbNumMaxConnection Property via Configuration tool
(Doc ID 2112091.1)
Last updated on FEBRUARY 27, 2019
Applies to:Hyperion BI+ - Version 220.127.116.11.000 and later
Oracle Exalytics Software - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
EPM registry diagnostic report was missing dbNumMaxConnection property and had to manually add it using the ./epmsys_registry.sh addproperty command.
Then manually set the dbNumMaxConnection property to 600 using the command ./epmsys_registry.sh updateproperty.
Screenshot showing the dbNumMaxConnection value as 600:
Then tried to update the dbNumMaxConnection property using the Configuration tool to change it from 600 to 200.
Screenshot demonstrating the alteration of dbNumMaxConnection value to 200 via the Configuration tool:
Ran the registry diagnostics and it shows the dbNumMaxConnection value is currently 600.
After going through the configuration process and rerunning the registry diagnostics, the values have not changed. The value in the System Message has not changed either.
Sreenshot showing that the dbNumMaxConnection value is still shown as 600 after running the configuration tool:
Screenshot showing the value in System Message (From Consolidation Administration screen of EPM workspace):
Why isn't the dbNumMaxConnection value updated when changed using Configuration tool?
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