Publisher server cannot connect to the target Oracle DB using Oracle Service name

Products

• CA Automic Dollar Universe

Issue/Introduction

Affects Release version(s): 5

Error Message :
Error: the database connection is not working. Reason: Listener refused the connection with the following error:ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

Patch level detected:Publisher 3.1.0
Product Version: Dollar.Universe 5.6.0 FX25010

Description :Publisher server cannot connect to the target Oracle DB using Oracle Service name.

Additional information:

Using the command "lsnrctl status" to be executed on the machine where Oracle DB is installed, you should see a similar output as shown below:

Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...


The "Service" has an "Instance". For example, The Service "XEXDB" contains an Instance "xe". If "XEXDB" is used as a "DB Instance ID" for Publisher, it will fail. But, if instance "xe" is used, it will work

Environment

OS: All
OS Version: ALL

Cause

Cause type:
By design
Root Cause: The current version of Publisher v3.1 only supports "Instance" name connectivity to Oracle.

Resolution

Use the "Instance" name of the Oracle DB.

Fix Status: Released

Fix Version(s):
Component: Publisher
Version: Dollar.Universe 5.6.0 FX25010

Additional Information

Workaround :
N/A