BatchController Becomes Unusable Once CM Restarted
Last updated on DECEMBER 23, 2014
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.3.1]
Information in this document applies to any platform.
Batch controller becomes unusable once the CM is restarted.It is not able to automatically establish connection with the newly started CM so batch controller also requires a restart if CM is restarted.
Steps to Reproduce
1. Start CM
2. Start Batch controller
3. Stop CM
4. Start CM
Error messages in cm.pinlog:
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