Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Parent CM shuts down if the EM (external manager) cannot be reached by one of the CM children instances, hence preventing any new CM connections to that BRM instance at all.
When the BRM Communications Manager (CM) attempts to send an op-code request to any BRM External Manager (EM) and fails to do so, the CM child process that experiences the failure sends a signal to the parent CM (the one that allows new CM connections) to kill itself. As a results, if the EM is not available, BRM will not accept any new CM connections until the CM is restarted (after any remaining running child CMs are shut down, of course).
NOTE - When the CM (FM op-codes) call an EM op-code there is no issue, i.e. the CM child continues to work and no self-shutdown or shutdown of the parent CM occurs. It appears we can only reproduce the problem when executing the EM op-codes (any of them) via testnap directly.
Using testnap; sample input flist:
Note here the unexpected "shutdown" request.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms