ORA-12154 on database link

I have two oracle databases which I want to connect,
these are the entries in tnsnames.ora
UAT =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.16.72.166)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = uat849)
itdev6 =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 10.16.72.167)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = itdev6)
)I logged into UAT and create the link.
this is my sql for dblink creation
CREATE public DATABASE LINK test1 CONNECT TO username IDENTIFIED BY password USING 'itdev6';
this database link created successfully. But when I try to run a query against it I'm getting an error
select * from kh_gps_email_info_tab@test1
ORA-12154: TNS:could not resolve the connect identifier specified
Can anyone help me on this please?

Try this
itdev6.world =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 10.16.72.167)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = itdev6.world)
CREATE public DATABASE LINK test1 CONNECT TO username IDENTIFIED BY password USING 'itdev6.world';

Similar Messages

PL/SQL :ORA-04052 with Database link

i have created a database link in my producation database as following
CREATE PUBLIC DATABASE LINK <NAME>
CONNECT TO <USER>
IDENTIFIED BY <P/W>
USING <CONNECT STRING OF TARGET DATABASE
oracle version 9.0.2.8
OS : Windows 2003 EE R2 SP2
Using oracle failsafe 3.3.4 with windows cluster
Problem Description :
whenever i run my pl/sql procecdure to pull the data from the target database i get the following error
ERROR at line 3
ORA-06550:line 3 column 2
PL/SQL : ORA-04052: error occured when looking up remote object _<SCHEMA>.<TABLE>@<DATABASE LINKE NAME>_
ORA-00604 : ERROR occured at recursive SQL level 1
ORA-03106 : fatal tow-task communication protocol error
ORA-02063: preceding line from <DATABASE LINK NAME>
I have tested the same way in the test environment the same oracle version as well the OS but without oracle failsafe and windows cluster
the script goes smoothly with out any errors.
i have google and checked the OTN for all available solutions but still nothing its not getting throw
i will be very thankful for your replys and solutions
any farther clarification i am ready
thanks in advance

Hi,
This forum is for issues connecting to non-Oracle databases. As the problem is using PL/SQL to connect to another Oracle database then it would be better to post a thread in the PL/SQL forum -
PL/SQL
If you are trying to connect to a non-Oracle database then please give us the details of which non-Oracle database and the software you are trying to use to connect.
Regards,
Mike

ORA-00022 with Database Link and Trigger

Hello altogether,
I got a very strange behaviour with my oracle 10.2.
I have two nets N1 and N2, where N1 can access the servers in N2, but not the other way round. In both nets I have an Oracle database running (D1 and D2).
In N1 I calculate some data, which must be replicated to the database in N2. I do this by using triggers on my tables in database D1 copying the inserted or changed data to D2 by using a shared public database link.
This works fine most of the time. But sometimes I get the following error:
ERROR [STDERR] Caused by: java.sql.SQLException: ORA-02068: following severe error from D2
ORA-00022: invalid session ID; access denied
ORA-06512: at "CUSTOMER", line 13
ORA-04088: error during execution of trigger 'CUSTOMER'
When I use the database links manually, they work.
Any idea?
Thank you!!
Daniel

The ORA-02068 message might be important
02068, 00000, "following severe error from %s%s"
// *Cause: A severe error (disconnect, fatal Oracle error) received from
// the indicated database link. See following error text.
// *Action: Contact the remote system administrator.Have you searched Oracle support for any bugs associated with the ORA-02068?
Was the remote session killed, the remote database changed to restricted session, or bounced?
I take it the distributed session is created using a dedicated session and not shared server?
HTH -- Mark D Powell --

ORA-03113 using Database Link

Asking help Urgently..
We need to create a DB link from 7.3 to 10g. After initial problems, the DB link is finally established and we can query and do DML on the 10g DB from 7.3. using SQLPLUS.
Now the problem: We want to create triggers on tables in 7.3 DB to insert the same rows in 10g DB using the DB Link. The moment we create the trigger the connection is dropped with the error: ORA-03113: end-of-file on communication channel. We tried to write the insert statement inside a procedure/function but still the same problem.
Please help as we are desperate to find a solution for the said problem. The objective is to be able to insert a row in 10g (DB Linked) Database based on a trigger fired in 7.3 Database (Reference DB). Any help will be appreciated.
Thanks and regards.
Rajeev.

I know that 7.x to 10g is not supported officially and should not be used in production environment.
But in our case, we need it for a short duration (duration of Parallel run) and my query is that, if I am able to do inserts from the SQLPLUS using the said DB Link, then why this cannot be done thru a procedure or a trigger.
if anyone has an explanation or workaround, it will be great.
Rajeev.

ORA-02068+ORA-03113 on database link

Hi all
I have the following scenario:
The application is connecting to DB (Oracle 10.2.0.5) using jdbc connection pool.
The database is a 3-node RAC.
Using DB Link we access a PLSQL package on a remote database (10.2.0.4).The remote database is a single instance.
The remote database is not located behind FW.
Sometimes the remote DB is restarted, but we seem to hit these errors about 30 mins afterwards.
From time to time we get these errors and we cant find the root cause.
Any ideas how to address this?
Thanks,
Rudi

Rudi wrote:
Hi all
I have the following scenario:
The application is connecting to DB (Oracle 10.2.0.5) using jdbc connection pool.
The database is a 3-node RAC.
Using DB Link we access a PLSQL package on a remote database (10.2.0.4).The remote database is a single instance.
The remote database is not located behind FW.
Sometimes the remote DB is restarted, but we seem to hit these errors about 30 mins afterwards.
From time to time we get these errors and we cant find the root cause.
Any ideas how to address this?
Thanks,
RudiORA-00600/ORA-07445/ORA-03113 = Oracle bug => search on Metalink and/or call Oracle support

Forms ORA-03115 on database link

Hi,
I'm not new to forms but I'm going crazy about one error:
When I try to connect in forms to oracle8 from oracle7
I get this message: ORA-31015 unsupported network datatype or representation.
The mad is that it works with Oracles TOAD, and on any other PC of my colleagues, but not on mine.
Has someone any ideas?
Here's my syntax:
-- SELECT COUNT(LOT) INTO mycount FROM [email protected]

i work in forms 6i with oracle 8i and the solution in my case was: i create a view ( my_view as select * from table@databaselink) and i used the view my_view in my form. can you create too a synonym private or public of your view.

Problem creating a database link

Hi,
I tried to create a database link, but it doesn't work. When I connect to the database via SQL*Plus or SQL Developer, the entries in the tnsnames.ora work.
create database link DBOPBWS2.BAG connect to demo identified by demo
using 'DBOPBWS2.BAG';
Entry in tnsnames.ora:
DBOPBWS2.BAG =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =serv01.server.spub-systeme.de)(PORT = 1485))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SID = DBOPBWS2)
Entry in sqlnet.ora:
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
select * from [email protected];
Error:
ORA-12154: TNS: Angegebener Connect Identifier konnte nicht aufgelöst werden
12154. 00000 - "TNS:could not resolve the connect identifier specified"
What is wrong with the datbase link?
Please help me
Siegwin

Hi,
You could also "skip" the TNSNAMES use :Scott@my11g SQL>create database link DBOPBWS2.BAG connect to demo identified by demo
using '(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =serv01.server.spub-systeme.de)(PORT = 1485)) (CONNECT_DATA = (SERVER = DEDICATED) (SID = DBOPBWS2)))'
Database link created.

ODBC-datasource generating ORA-12154 (possible listener issue)

Hi,
I am trying to configure ao ODBC-datasoure from a client (using instant client 11.2) to a 11.2g Oracle DB server. The database listener is configured to use a non standard port 1700 in this case.
There is a firewall between the client and the server which is configured to allow connections to the database server on the specified port, when I use telnet from the client to the server, the connection opens on this port, but when I try to test the odbc-datasource I have configured ig et the error ORA-12154.
The link below outlines the details of the error:
http://ora-12154.ora-code.com/
To the context should be added, that there is no problem to use SQL Plus from a computer behind the firewall to connect to the database server using the TNS name that is being used in the ODBC-datasource.
I have tried to configure the odbc-datasource using both a tns_names.ora file, and also directly in the odbc-datasource using //[ip address] : [port]/TNS_NAME. Both ways of configuring the odbc-datasource generates the same error. I am currently suspecting that the error might be due to some sort of connection redirection on the part of the tns listener on the database server which triggers the firewall to terminate the connection. Could this be the case?
Does anyone have any suggestions what this error might be caused by. Any suggestions on how to continue my troubleshooting would also be valueble. Further, what kind of configuration would need to be inplace, on the tns-listener / database server side to make this sort of configuration to work.
Finally, I should also ask that I have tested the same ODBC-datasource configuration in a test system without any firewall inbetween, and that configuration works fine, so there seems to be no problem with the client software configuration per se.
Any help is apprichated.
/Eaglecoth

Cabelcow wrote:
I managed to solve this issue myself.
Since there seems to be some problem locating the server I added "HOSTNAME" to the following line in the SQLNET.ORA file on the server:
names.directory_path = (HOSTNAME,TNSNAMES)
This solved the issue by using the following syntax in the ODBC Configuration:
TNS Service Name: [ip-address]:[port]/[TNS NAME]
Where the TNS_NAME should be that of the TNS_NAME for the database defined in the TNSNAMES_ORA at the server. Note that this value is case sensetivetnsnames.ora is ONLY used by the client side application. It is the tns complement to the local 'hosts' file. It is used by the CLIENT to resolve an alias (tns net service name) to a host (ultimately an ip), port, and service name. Your assertion that the tns_name should be ... hmm, now that I read that again, are you saying that the tnsnames entry on the client should match the one in the tnsnames file on the server? If so, yes and no. There is no technical requirement that they match. It is simply that it is usually assumed that the one on the server is correct and may be used as a model for what to do on the client. The server - acting as a server - doesn't even use the tnsnames.ora file. It exists on the server only to support any client process that may happen to be running on the same box as the db.
Maybe this will help you understand the connections
=================================
ORA-12154: TNS:could not resolve the connect identifier specified
This error means one thing, and one thing only. The client could not find the specified entry in the tnsnames.ora file being used.
As a follow-on to that statement, remember that when you use a dblink, the database in which the link is defined is acting as a client to the database that is the target of the link. So in this case, the tnsnames.ora file on the host of your source should have an entry for your target db, as defined in the db_link.
And for the umpteenth time ... this error has NOTHING to do with the status of a listener. The connection request never got far enough to reach a listener. If anyone tells you to check a listener in response to ora-12154, they are not paying attention, or do not understand how TNS works. This error is the equivalent of not being able to place a telephone call because you don't know the number of the party you want to reach. You wouldn't debug that situation by going to the other guy's house and testing his telephone, or by going to the phone company and testing the switchboard. And you don't debug a ORA-12154 by checking the listener. If I had a top ten list of "Incredibly Simple Concepts (tm)" that should be burned into the brain of everyone who claims to be an Oracle DBA, it would include "ORA-12154 Has Nothing To Do With The Listener".
=================================
A couple of important points.
First, the listener is a server side only process. It's entire purpose in life is to receive requests for connections to databases and set up those connections. Once the connection is established, the listener is out of the picture. It creates the connection. It doesn't sustain the connection. One listener, with the default name of LISTENER, running from one oracle home, listening on a single port, will serve multiple database instances of multiple versions running from multiple homes. It is an unnecessary complexity to try to have multiple listeners or to name the listener as if it belongs to a particular database. That would be like the telephone company building a separate switchboard for each customer.
Additional notes on the listener: One listener is capable of listening on multiple ports. But please notice that it is the listener using these ports, not the database instance. You can't bind a specific listener port to a specific db instance. Similarly, one listener is capable of listnening on multiple IP addresses (in the case of a server with multiple NICs) But just like the port, you can't bind a specific ip address to a specific db instance.
Second, the tnsnames.ora file is a client side issue. It's purpose is for address resolution - the tns equivalent of the 'hosts' file further down the network stack. The only reason it exists on a host machine is because that machine can also run client processes.
Assume you have the following in your tnsnames.ora:
larry =
(DESCRIPTION =
 (ADDRESS_LIST =
 (ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 1521))
 (CONNECT_DATA =
 (SERVICE_NAME = curley)
)Now, when you issue a connect, say like this:
$> sqlplus scott/tiger@larrytns will look in your tnsnames.ora for an entry called 'larry'. Finding it, tns sends a request through the normal network stack to (PORT = 1521) on (HOST = myhost) using (PROTOCOL = TCP), asking for a connection to (SERVICE_NAME = curley).
Where is (HOST = myhost) on the network? When the request gets passed from tns to the next layer in the network stack, the name 'myhost' will get resolved to an IP address, either via a local 'hosts' file, via DNS, or possibly other less used mechanisms. You can also hard-code the ip address (HOST = 123.456.789.101) in the tnsnames.ora.
Next, the standard networking process delivers the message to port 1521 on myhost. Hopefully, there is a listener on myhost configured to listen on port 1521, and that listener knows about SERVICE_NAME = curley. If so, the listener will spawn a server process to act as the intermediary between your client and the database instance. Communication to the server process will be on a randomly selected available port. At that point the listener is out of the process and continues to user port 1521 to await other connection requests.
What can go wrong?
First, there may not be an entry for 'larry' in your tnsnames. In that case you get "ORA-12154: TNS:could not resolve the connect identifier specified" No need to go looking for a problem on the host, with the listener, etc. If you can't place a telephone call because you don't know the number (can't find your telephone directory (tnsnames.ora) or can't find the party you are looking for listed in it (no entry for larry)) you don't look for problems at the telephone switchboard.
Maybe the entry for larry was found, but myhost couldn't be resolved to an IP address (say there was no entry for myhost in the local hosts file). This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe there was an entry for myserver in the local hosts file, but it specified a bad IP address. This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe the IP was good, but there is no listener running: "ORA-12541: TNS:no listener"
Maybe the IP was good, there is a listener at myhost, but it is listening on a different port. "ORA-12560: TNS:protocol adapter error"
Maybe the IP was good, there is a listener at myhost, it is listening on the specified port, but doesn't know about SERVICE_NAME = curley. "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor"
Third: If the client is on the same machine as the db instance, it is possible to connect without referencing tnsnames and without going through the listener.
Now, when you issue a connect, say like this:
$> sqlplus scott/tigertns will attempt to establish an IPC connection to the db instance. How does it know the name of the instance? It uses the current value of the enviornment variable ORACLE_SID. So...
$> export ORACLE_SID=fred
$> sqlplus scott/tigerIt will attempt to connect to the instance known as "fred". If there is no such instance, it will, of course, fail. Also, if there is no value set for ORACLE_SID, the connect will fail.
check executing instances to get the SID
[oracle@vmlnx01 ~]$ ps -ef|grep pmon|grep -v grep
oracle 4236 1 0 10:30 ? 00:00:00 ora_pmon_vlnxora1set ORACLE_SID appropriately, and connect
[oracle@vmlnx01 ~]$ export ORACLE_SID='vlnxora1
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:37 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsNow set ORACLE_SID to a bogus value, and try to connect
SQL> exit
[oracle@vmlnx01 ~]$ export ORACLE_SID=FUBAR
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:57 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
Enter user-name: Now set ORACLE_SID to null, and try to connect
[oracle@vmlnx01 ~]$ export ORACLE_SID=
[oracle@vmlnx01 ~]$ sqlplus /scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:43:24 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-12162: TNS:net service name is incorrectly specifiedOk, that is how we get from the client connection request to the listener. What about the listener's part of all this?
The listener is very simple. It's job is to listen for connection requests and make the connection (server process) between the client and the database instance. Once that connection is made, the listener is out of the picture. If you were to kill the listener, all existing connections would continue. The listener is configured with the listener.ora file, but if that file doesn't exist, the listener is quite capable of starting up with all default values. One common mistake with the listner configuration is to specify "HOST=localhost" or "HOST=127.0.01". This is a NONROUTABLE ip address. LOCALHOST and ip address 127.0.0.1 always mean "this machine on which I am sitting". So, all computers are known as "localhost" or "127.0.0.1". If you specify this address, the listener will only be capable of receiving requests from the machine on which it is running. If you specified that address in your tnsnames file - on a remote client machine - the request would be routed to the machine on which the requesting client resides. Probably not what you want.
=====================================

ORA-24365 from db link

Hi:
I am on 10.2.0.3.
A db link has been created from another database to my database which has the following parms. An ORA-24365 was raised even on an attempt to select sysdate from dual. Any suggestions?
SQL> select sysdate from dual@dblink1 ;
select sysdate from dual@dblink1
ERROR at line 1:
ORA-02068: following severe error from dblink1
ORA-24365: error in character conversion
PROPERTY_NAME PROPERTY_VALUE
DICT.BASE 2
DEFAULT_TEMP_TABLESPACE TEMP
DEFAULT_PERMANENT_TABLESPACE USERS
DEFAULT_TBS_TYPE SMALLFILE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.3.0
GLOBAL_DB_NAME FSUAT.COVANCE.COM
EXPORT_VIEWS_VERSION 8
DBTIMEZONE 00:00

This is documented in ML Doc 212043.1 (ORA-24635 Using Database Link Between 8i and 9i Databases)
HTH
Srini

On deploy tries to recreate database link?

I have a problem when deploying a mapping.
I keep getting the error ORA-02011: duplicate database link name.
After I analyzed the Job Details of this deploy and the one of the mapping that is very similar to this one in the same location, I noticed that the one that gives problems tries to do Create of a location. The other one does a Replace of a location (database link). Both mappings are at the same location and the source and target locations are the same for both mappings.
Sounds familiar? What coud be the problem?

Hi!
Probably you can check the connector status. In Control Center, you can expand the connector status and see what you have.
Regards,
Sebastian

ORA-12154 when using Database Link

We're running 11r2 on our servers. I have a primary db and a standby db, using Data Guard. The standby is open for read-only querying. We are not using ASM.
The primary (and thus the standby) have a PUBLIC database link to a third db server.
When I run a query against the database link on the primary: select * from test@MyDBlink; Everything works fine.
When I run the same query against the database link on the standby: select * from test@MyDBlink; I get ORA-12154: TNS:could not resolve the connect identifier.
I check that the db link exists on the standby. It does.
I go to command prompt on the standby and run "tnsping MyDBlink". It executes fine. It says "Used TNSNAMES adapater to resolve the alias" and sure enough, MyDBlink is referenced in the TNSNAMES.ORA.
I also run "tnsping IP-of-MyDBlink" to doublecheck. No issues.
What is going on that is blocking the db link on the standby? Many reports utilize that standby and I'd hate to deny them the functionality of a db link.
Thanks

893968 wrote:
We're running 11r2 on our servers. I have a primary db and a standby db, using Data Guard. The standby is open for read-only querying. We are not using ASM.
The primary (and thus the standby) have a PUBLIC database link to a third db server.
When I run a query against the database link on the primary: select * from test@MyDBlink; Everything works fine.
When I run the same query against the database link on the standby: select * from test@MyDBlink; I get ORA-12154: TNS:could not resolve the connect identifier.
I check that the db link exists on the standby. It does.
I go to command prompt on the standby and run "tnsping MyDBlink". It executes fine. It says "Used TNSNAMES adapater to resolve the alias" and sure enough, MyDBlink is referenced in the TNSNAMES.ORA.
I also run "tnsping IP-of-MyDBlink" to doublecheck. No issues.
What is going on that is blocking the db link on the standby? Many reports utilize that standby and I'd hate to deny them the functionality of a db link.
ThanksMost people with this problem don't understand that the dblink is just another client, no different than sqplus running on the same machine - and therefore the link uses the tnsames in the ORACLE_HOME of the database containing the link. But it seems from the steps you've described that you've grasped that. The only thing I can think of off the top of my head is when you try sqlplus from the standby server you are hitting a different tnsnames than the one the database is using.

A question about CREATE PUBLIC DATABASE LINK and ORA-12154 error

Dear all,
I have a problem about public database link creation and I would appreciate if you could kindly give me a hand. I have the following connection parameters in my
tnsnames.ora file:
DGPAPROD.WORLD =
     (DESCRIPTION =
       (ADDRESS_LIST =
        (ADDRESS = (COMMUNITY=tcp.world)
          (PROTOCOL=TCP)(HOST=ORASR001)(PORT=1521)
       (CONNECT_DATA = (SID = DGPAPROD))
...Having the above mentioned parameters I can connect to this remote database directly in a SQL*Plus shell:
$ sqlplus username/[email protected] works pretty well and the connection is established without any problem.
Now, what I would like to do is to create a public database link to this remote database in order to avoid the user/connection switching for viewing the
content of this database. I proceeded according to the syntax indicated in the Oracle online documentation:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_5005.htm#SQLRF01205
Therefore I run the following in order to create a public database link
CREATE PUBLIC DATABASE LINK SR001_dblink CONNECT TO user IDENTIFIED BY password USING 'DGPAPROD.WORLD';Apparently there is no error and the link is created successfully. However it cannot resolve the remote host and whenever I run the following query
(myenterprise is the name of a table in that remote database)
SELECT *
FROM myenterprise@SR001_dblink
ERROR at line 1:
ORA-12154: TNS:could not resolve the connect identifier specifiedWhat causes this problem?
Thanks in advance,
Kind Regards,
Dariyoosh

spajdy wrote:
You must have defined DGPAPROD.WORLD in tnsnames.oar on server where you DB is runnig.Hello there,
Thanks a lot for this nice solution. In fact I had to add the connection parameters into the tnsnames.ora file of the server on which the link was created (not the tnsnames.ora of my oracle client stored on the localhost)
After a bit googling I found another solution that allows to create the database link:
CREATE PUBLIC DATABASE LINK SR001_dblink CONNECT TO user IDENTIFIED BY password USING '(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY=tcp.world)
(PROTOCOL=TCP)(HOST=ip_adresse)(PORT=1521)))(CONNECT_DATA = (SID = GPAPROD)))';Thanks a lot for your help!
Kind Regards,
Dariyoosh
Edited by: dariyoosh on 18 nov. 2009 07:15

Ora-12154 problem with database link and transparent gateway

Hello,
I’m trying to make a communication between oracle and SQL server 2005.
I use oracle 10g E.E Release 10.2.0.3.0 and the transparent gateway for SQL server 10201_gatway_win32.zip.
Install:
The oracle database is installed into a server named ss-serv. This server has two partition disk C and E. Oracle database is installed in E and the gateway in C. There is already a database (instance) running in the oracle home (in E).
I configured the gateway as described into: http://download.oracle.com/docs/cd/B...3/conf_sql.htm.
In sql server 2005, there is a database running named ClientTricks.
I created a user named Avogadro with a login.
In the partition C where the gateway is installed, the file inittg4msql.ora is like this:
HS_FDS_CONNECT_INFO= ss-serv. ClientTricks
The file sqlnet.ora where the gateway is installed is configured like this:
SQLNET.AUTHENTIFICATION_SERVICES=(NTS)
NAMES.DIRECTORY_PATH = (TNSNAMES, EZCONNECT)
I configured the listener that is in the C partition where the gateway is installed, and the tnsnames that is in the oracle database in E partition disk like this:
Listener :
LISTENER=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=ss-serv)
(PORT=1521))
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=tg4msql)
(ORACLE_HOME=C:\oracle\product\10.2.0\tg_1)
(PROGRAM=tg4msql)
tnsnames:
mytg4msql=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=ss-serv)
(PORT=1521)
(CONNECT_DATA=
(SID=tg4msql))
(HS=OK))
After edited the listener, I stop and start the listener for the transparent gateway from administrative tools in the services.
Then, connected in oracle (in a database named fakeclient) I created a database link in sqlplus.The the dblink were created, but when I tried to querry some data from ClientTricks by executing the following instructions:
select * from s_client@dblink
i got this fatal and terrible error :
ora-12154 TNS:could not resolve the connect identifier specified
I verified all my procedure and stapes, all seems to be good. I did a tnsping of mytg4msql
I got this error in the command prompt:TNS-03505 fail to resolve name
Could someone help me ?
Sorry for my English ,I’m French
best regards

Hi Mkirtley,
i clarify you what i've done:
Pease have a look in the link in my first post. Then, i said that in oracle database home the listener is in port 1521
here is this listener:
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=PLSExtproc)
(ORACLE_HOME=E:\oracle\production\10.2.0\db_1)
(PROGRAM=extproc)
LISTENER=
(DESCRIPTION_LIST=
(DESCRIPTION=
(ADDRESS= (PROTOCOL=TCP)(HOST=ss-serv)(PORT=1521))
(ADDRESS= (PROTOCOL=IPC)(KEY=EXTPROC0))
Here is the tnsnames.ora in oracle database home:
N.B in this ora file, there's already some descriptions for the database running, so i just add these lines under the description in ora file.Here is:
Jest=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=ss-serv)(PORT=2000))
(CONNECT_DATA=
(SID=tg4msql)
(HS=OK)
for the listener of the gateway (installed in C partition):
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=tg4msql)
(ORACLE_HOME=C:\oracle\production\10.2.0\tg_1)
(PROGRAM=tg4msql)
LISTENER=
(DESCRIPTION_LIST=
(DESCRIPTION=
(ADDRESS= (PROTOCOL=TCP)(HOST=ss-serv)(PORT=2000))
(ADDRESS= (PROTOCOL=IPC)(KEY=EXTPROC1))
here are all i did.
Best regards

Using database-link in view to get around ORA-01031 error

I have been granted select rights on a users table. I am therefore able to select from his table. If however I try create a view against his table I run into the ORA-01031 problem. I have worked around this problem by creating a database-link to myself and then adding that to the view creation and it works. What are the downsides of using the database-link in this way?

The only down side I have been able to identify is that a extra session is created and that the CPU has a little extra work due to the LOOP BACK that takes place. I need to ensure the network is not unnessesarly used and therefore will need to ensure that 127.0.0.1 (local host) is used in the database connection discription. e.g.
create database link my_db_link connect to scott identified by tiger using '(description=(address=(protocol=tcp)(host=127.0.0.1) (Port = 1521) ) (connect_data= (sid=ora10g)))';

Error in database link(ORA-02063 and ORA-02391)

Hi
database link was working fine till this morning. now when i try to query using the database link, i get the following error
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
ORA-02063: preceding line from RMSLIVE
It would beof great help if you can advise why this error is occuring.
many thanks.

The error stack is quite obvious.
Either, the profile, with which the database user on remote database is running, must be modified to allow more connections or investigate the session leak in the application talking over database links.

ORA-12154 on database link

Similar Messages

Maybe you are looking for