asked on
Connecting to Oracle 10g from remote server (L2TP IPSEC VPN)
Hi,
-- Question 1 --
2 Windows 2003 servers, each of them with 1 Oracle 10g database.
Objective = connect to DB 2 (on server 2...) from server 1.
Just for info / background: would like to remove as soon as possible the DB1 on server 1, and install only oracle client on server 1, and use a common/single one and only DB (on server 2...).
Tunnel has been setup successfully from what I can see and port 1521 on server 2 is open.
1. PINGING server 2 from server 1 => successful.
2. TNSPING from server 1 trying to reach the target DB on server 2 => successful too.
3. SQLPLUS from server 1 trying to reach target DB on server 2 ends up on the typical ORA-12514 error message. Looking at the listener.log file, I have:
(CONNECT_DATA=(SERVICE_NAM
TNS-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor
I tried the following:
Set the variable USE_SHARED_SOCKET to TRUE in the registry => did not help / still getting the same error message.
Wanted now to investigate more on the connection manager in 10g / cman.ora but prefer to come back to you first to get your opinion. What should I do?
-- Question 2 --
Last point / just a question: the listener.log on the server1 shows everytime I try SQL a different port (in the ex. given above: port 1038 this time). Something I was expecting - but with the use of the USE_SHARED_SOCKET = TRUE on the target DB server, I would imagine only 1521 would then be retained after the connection has been engaged on 1521 since only this port is open on the firewall... Am I correct / what I do I miss here?
Any hint very much welcome !
Thanks a lot in advance.
-- Question 1 --
2 Windows 2003 servers, each of them with 1 Oracle 10g database.
Objective = connect to DB 2 (on server 2...) from server 1.
Just for info / background: would like to remove as soon as possible the DB1 on server 1, and install only oracle client on server 1, and use a common/single one and only DB (on server 2...).
Tunnel has been setup successfully from what I can see and port 1521 on server 2 is open.
1. PINGING server 2 from server 1 => successful.
2. TNSPING from server 1 trying to reach the target DB on server 2 => successful too.
3. SQLPLUS from server 1 trying to reach target DB on server 2 ends up on the typical ORA-12514 error message. Looking at the listener.log file, I have:
(CONNECT_DATA=(SERVICE_NAM
TNS-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor
I tried the following:
Set the variable USE_SHARED_SOCKET to TRUE in the registry => did not help / still getting the same error message.
Wanted now to investigate more on the connection manager in 10g / cman.ora but prefer to come back to you first to get your opinion. What should I do?
-- Question 2 --
Last point / just a question: the listener.log on the server1 shows everytime I try SQL a different port (in the ex. given above: port 1038 this time). Something I was expecting - but with the use of the USE_SHARED_SOCKET = TRUE on the target DB server, I would imagine only 1521 would then be retained after the connection has been engaged on 1521 since only this port is open on the firewall... Am I correct / what I do I miss here?
Any hint very much welcome !
Thanks a lot in advance.
Oracle Database
Last Comment
csi-consulting
ASKER
Thanks for the swift reply.
Adapter TNSNAMES zur Auflösung des Alias benutzt
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <MY DB SERVER IP>)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = <MY SERVICE NAME>)))
OK (40 ms)
Since the TNSPING is fine, it can be "only" at Port level then?
Adapter TNSNAMES zur Auflösung des Alias benutzt
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <MY DB SERVER IP>)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = <MY SERVICE NAME>)))
OK (40 ms)
Since the TNSPING is fine, it can be "only" at Port level then?
> tnsping ntserver/pre.nonsenseAdapter HOSTNAME zur Auflösung des Alias benutztAttempting to contact (DESCRIPTION=(CONNECT_DATA
That service name pre.nonsense is nonsense. TNSPing only checks for the server and port (and some compatibility issues maybe), the service name is of no use.ASKER
- Thanks -
Which means at least the IP + port 1521 are fine / open.
I will investigate differently / any problem theoretically you are aware of concerning IPSEC? Any risk it is not supported by Oracle in general?
Thanks again
Which means at least the IP + port 1521 are fine / open.
I will investigate differently / any problem theoretically you are aware of concerning IPSEC? Any risk it is not supported by Oracle in general?
Thanks again
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Changes have been performed on the listener side on the DB server.
Thanks in any case for your swift replies.
Thanks in any case for your swift replies.
I suppose the problem lies in the service name created. Global name, DNS domain, computer name may all play a role. Look into the listener log or lsnctrl to see which name the service uses actually.