Unable To Customise TNSNAMES Alias For Remote DB Installation
(Doc ID 2737825.1)
Last updated on DECEMBER 22, 2020
Applies to:Oracle Communications Network Charging and Control - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC) 22.214.171.124.0 version,
Consider a Customer have provisioned remote databases for all NCC nodes. The production Service Managment System (SMS) node is Real Application Clusters (RAC) based, and the Transparent Network Substrate (TNS) defined uses the "SERVICE_NAME" directive to identify the instance. It appears that NCC doesn't appear to configure the tnsnames.ora, as this is embedded deep inside the packages .jar files and the only options for the installer are:
- Oracle SID: SMF/SCP/E2BE
- Database hostname:
- Database user: (hard coded based on machine type)
- Oracle database password
As such, they can't get past this step, the database connection doesn't recognize the far end, and if they proceed it fails to connect.
Is there a way to customize the TNSNAMES entry for "SMF" so the installation scripts can function?
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