Re: Migrate EBS on a Single DB Instance to a RAC DB
Administrator
5738 posts
The following error is normal!
SQL> connect system/*****@//prdc1pdb01:1521/DBOFINP11
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
DBOFINP11 is SID, but the command syntax requires SERVICE_NAME.
So you can connect with DBOFINP1, which is the SERVICE_NAME, but you can not connect with DBOFINP11, which is the SID.
So it is normal! not an issue.
Re: Migrate EBS on a Single DB Instance to a RAC DB
Administrator
5738 posts
as for the IP addresses in tnsnames.ora ->
These IP addresses are for SCAN right?
I mean -> 10.128.178.24, 10.128.178.25 and 10.128.178.26
So, it seems it is an expected behaviour.
Look at the following note:
12.13 RAC Setup, Why Scan IPs Are Generated Instead Of Scan Name In tnsnames.ora (Doc ID 2141287.1)
In 12.1.3+, E-Business Suite instance with RAC enabled and scan enabled database, one can observe that scan IPs are generated in the tnsnames.ora instead of scan name.
It says :
" This is due to known limitation in 11.2.0.3 database. This is documented in Note 1448717.1. Failover of the instances may not happen properly, if the all the instance services are not registered with scan listeners. The fix for this issue is to generate the tnsnames.ora with all the scan ip addresses instead of scan hostname."
So, ignore it. It is better to have tnsnames.ora with the scan ip addresses. However if you change the scan ips, then you need to be aware , so that you can run autoconfig on the database thier.
Here it says
"Patch 10427234 was released for 12.1.3 specifically to enable Autoconfig to generate all 3 IP addresses. The code is already present in 12.2 AD/TXK.C.D5+ so no patch is required for 12.2."
These IP addresses are for SCAN right? Yes as command line result:
host prdc1pdb01-scan
prdc1pdb01-scan.dalkia.net has address 10.128.178.26
prdc1pdb01-scan.dalkia.net has address 10.128.178.25
prdc1pdb01-scan.dalkia.net has address 10.128.178.24