How to Resolve Error "pcmdd: bad connect for hostname, errno 146"
Last updated on JUNE 25, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version,
While upgrading from PS15 to PS17, there were errors right in the beginning of the script execution:
There was no relevant error on dm_pinlog, and cm_pinlog was empty because cm did not start up during execution.
Even that all the Oracle documentation points to the approach of using the HOSTNAME in the configuration files, it worked after the user replaced the hostname with the IP.
Is there any error known related to this?
For another environment which is in MPS1 and to be upgraded to PS17, should it be setup with IP or with HOSTNAME?
It was working with HOSTNAME before when upgraded from BRM 7.4 to 7.5 PS15.
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