BRM Targets Shown DOWN After the BRM Application was Patched with BRM 7.5 PS20 and New Perl Version
(Doc ID 2477371.1)
Last updated on FEBRUARY 03, 2019
Applies to:Application Management Pack for Oracle Communications - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, BRM Plug-in
Executed the discovery for the target named "BATCH_CONTROLLER.xxxx_11971", which was running and UP before the patch 20, this discovery creating 4 core files, this discovery is done using the pin user through the autodiscovery method in OEM. Since core dump creating, the status of BATCH_CONTROLLER is showing as DOWN where as BATCH_CONTROLLER is in running.
The owner for these files is the user ABCD, which is used by the OEM monitoring agent to monitor this target, so the core dump are generated when the agent try to collect the info from the target but it can´t.
1. Here the core file information
The issue can be reproduced at will with the following steps:
1. Upgrade to BRM PS20, Login to cloud console/Oracle Enterprise Manager
2. Check for BRM process status.
NOTE:After upgrading to 7.5PS20, the perl version also upgraded to 5.24.0 and its related environmental variables also updated with 5.24.0 But while agent running it still referring the old 5.18.2 perl executable to run the pin_ctl.
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