Ora-03121 connect to odbc datasource

I am running 8i 8.1.6 oracle, forms 6i, and am trying to connect to a AS400 DB2 database. I have the ODBC driver for the AS400 setup properly. When I try to connect in Forms 6i or SQL*Plus with the connect string odbc:datasource_name I get an error ORA-03121 error saying "No interface driver connected - function not performed". Any ideas? I have searched all over reguarding this error but none are specific to this. Net8 is up and running fine as well....
Thanks in advance,
Jeff

Thanks for the replies! I have used the ODBC test utility that comes with Oracle. It actually works and I am able to run ad hoc queries and such against this as400 datasource (this was prior to my posting). However if I try to connect to it in Forms using the odbc:data_source connect string, I get the ora-03121 error.
I don't think it ever gets to the point of checking the datasource name because I get the same error no matter what datasource name I use, even if I leave it blank.
Could I be using the wrong syntax? My AS400 datasource name is "rainier" and the connect string I use is "user/pword@odbc:rainier".
Thanks again for the replies!

Similar Messages

  • ORA-03121 when trying to connect to Access

    Hello all,
    maybe somebody can help: while trying to establish ODBC connection from Discoverer 3.1 to MS Access database I get an error:
    "Failed to connect to Database ORA-03121: no
    interface driver connected - function not performed "
    I was using DNS created for Access and connect string like:
    username/password@ODBC:DNSname
    Regards,
    Alex
    [email protected]

    Thanks for your reply.
    But the funny thing on this compatibility issues is, that this configuration worked before. The only thing we did, was to setup the client-PC on a new hardware with also a new operating system (upgrading from Solaris 5.8 to 5.10). And from that time we encountered this problem.
    Are there any OS-related problems known or better to say: is (was) ORACLE 7.1.3 supported on Solaris 5.10 ? Should we look for any patches which might help us ?

  • 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 <b><i><u>NOTHING</u></i></b> 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.
    =====================================

  • Datasource: ORA-02019: connection description for remote database not found

    Hi,
    I recently made the datasource to point to a new host, and using the EM console tested the connectivity to the datasource to be successful.
    Java code that refers to the DS is also the same as before that was working as only the connection string has been changed, but now trying to access the web-application shows the following error in the logs:
    ==============
    Exception::java.sql.SQLException: ORA-02019: connection description for remote database not found
    oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
    oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
    oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
    oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
    oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:113)
    oracle.jdbc.driver.T4CStatement.execute_for_describe(T4CStatement.java:431)
    oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:1029)
    oracle.jdbc.driver.T4CStatement.execute_maybe_describe(T4CStatement.java:463)
    oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1126)
    oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1274)
    oracle_jdbc_driver_T4CStatement_Proxy.executeQuery()=====================================
    What could be the reason? Is there any other app server datasource related setting that needs to be done or is it some other issue - as I said 'testing the connection from EM console connects successfully'.
    Thanks,
    Rommel.

    The issue is resolved now.
    One of the queries used a db link that was missing on the new database and therefore the error from the java code.
    Since testing for connectivity using DS through EM console does not check for any db link (using the default query it executes) connectivity was successful.
    Thank a lot,
    Rommel.

  • [S1000][unixODBC][Oracle][ODBC][Ora]ORA-03134: Connections to this server version are no longer supported

    Hello,
    I'm using  unixODBC with ODBC Oracle client 11 (Debian 7) to connect to Oracle database version 9.2.0.6 (Solaris 10),  but show me this message:
    [S1000][unixODBC][Oracle][ODBC][Ora]ORA-03134: Connections to this server version are no longer supported.
    Note: I can connect to Oracle database version 10+.
    Please can you help me.
    Thank you

    Are you positive you're using version 11 Oracle client and 9206 database?  That combination should work, and Ive never seen that error message occur for anything but the expected reason.  
    If you have MOS access you can check the client/database compatibility with the following note:
    Client / Server / Interoperability Support Matrix For Different Oracle Versions (Doc ID 207303.1)
    Hope it helps,
    Greg

  • ORA-03121: No interface driver connect

    Hi there,
    can anybody solve my problem? i have installed Personal Oracle8 and then i installed Developer 2000 forms 4.5.
    Now i am trying to connect with Oracle 8 from developer but it is showing ORA-03121 error.
    when i check the error detail, it says Net8 driver not load in memory or there is mismatch of version.
    one thing noticible that i have SQL*PLUS 8 and SQL*PLUS 3.2 both installed .
    i want to be able to connect with database from Developer so that i can run form.
    Any kind of help or advice from you professionals will be extremely helpful.
    Regards
    Abid Malik

    To start the listener from command line issue lsnrctl start.
    To configure SQLNET use the SQLNET easy config utility that came with the Forms installation.
    More info:
    http://www.orafaq.org/faqnet.htm

  • [b]ora-03121[/b] no interface driver connected.

    After succesful installation of Oracle9i Enterprise Edition on windows2000 server.When we installed Forms5 on same machine it shows ora-03121 no interface driver connected.
    Another message is ora-12203 TNS unable to connect to destination.Kindly suggest where things got wrong
    regards
    vikas

    Forms 5.0 expects to be installed into the "Default" oracle home - this generally means that you have to install it onto the box first and then install any multi-Oracle home products such as the database afterwards.
    Forms 5.0 should certainly not be installed into the same oracle home as a 9i database

  • Error ORA-03121: not driver connected

    Installed Oracle client 7.3.4 trying to connect to an Oracle 7.3.4 DB. I am getting error ORA-03121: not driver connected -
    function not perfomed when I try and connect our client application. When I use SQL*Plus 3.3, I have no problems connecting, but when I try and connect through my client application, I get the error.
    Any ideas?
    Thanks
    null

    SQL*Plus 3.3 is for Oracle 7 while SQL*Plus 8.0 is for Oracle 8. So, 3.3 will load the Oracle 7 DLLs while 8.0 will load the 8i DLLs. Do you have Net8 installed and configured on the client?

  • Migrate tables and data from ODBC datasource to Oracle 11.2

    Hiya
    I have a database file in Dynamics NAV 5.0 native format - about 200-300 tables totalling maybe 10 GB worth of data.
    My task is to migrate those tables with their data into a schema in our Oracle 11.2 database.
    No tools support the NAV format directly :-) But I have a windows ODBC driver for that format that works.
    The Oracle database runs on Linux and I have no ODBC transparent gateway and no linux ODBC driver that would let me access the NAV datafile directly from within Oracle.
    I tried migration wizard in SQL Developer, but it seems it cannot use a "generic ODBC" datasource (even with JDBC-ODBC bridge), it must be a supported database format?
    Then I have tried trial of product Altova MapForce, but it can't seem to read the schema (table/columns) from the ODBC datasource for some reason.
    I know reading the schema from the ODBC datasource is possible - I have used third party product "Database Browser" that reads the ODBC with no problems.
    And a colleague has read the schema of the ODBC in C# also.
    I am primarily a SQL developer. My colleague said he could write in C# a program that looped over the tables in the ODBC, read the columns, executed "create table" in Oracle, read data from the ODBC, inserted data in Oracle.
    But he is going on vacation right now :-( And I keep thinking that someone else must have written such a migration program ;-)
    I just can't seem to find it by googling? Altova Mapforce was my best bet, but it just seems to have problems with this specific ODBC datasource.
    Any ideas for a migration tool that can accept a generic ODBC datasource and not specifically SQL Server, MySQL, DB2, etc.?
    Thanks for any hints that might help ;-)
    Regards
    Kim Berg Hansen

    Hi Kim,
       The earlier 9i and 10g generic connectivity option - HSODBC - could only run as part of the RDBMS but the 11g DG4ODBC can be installed and run standalone without an RDBMS.  You then connect using database links from Linux using an entry in the RDBMS tnsnames.ora as you have said.
    See these notes depending if Windows is 32-bit or 64-bit -
    How to Configure DG4ODBC (Oracle Database Gateway for ODBC) on Windows 32bit to Connect to Non-Oracle Databases Post Install (Doc ID 466225.1)
    How to Configure DG4ODBC (Oracle Database Gateway for ODBC) on 64bit Windows Operating Systems to Connect to Non-Oracle Databases Post Install (Doc ID 1266572.1)
    The latest 11.2 version is available from My Oracle Support as -
    Patch 13390677: 11.2.0.4.0 PATCH SET FOR ORACLE DATABASE SERVER
    and for the gateways you only need to download -
    p13390677_112040_WINNT_4of6.zip
    for 32-bit but
    p13390677_112040_MSWIN-x86-64_5of7.zip
    for 64-bit.
    The downloads have everything necessary for a gateway standalone install.
    Regards,
    Mike

  • ORA-03121 After installing Gateway

    Hello Experts,
    i am trying to connec to MS Sql Server 2000 on remote win2003 machine by using my machine which is WinXP Oracle 10g 10.1.0.2. I installed and configure Gateway as well which is on diffrent home than the oracle in my machine.
    when i issue command on SQL Prompt
    connect imosadmin/imos@odbc:dsnimos
    i got
    ORA-03121: no interface driver connected - function not performed
    where as dsnimos is a dsn to MS SQL Server2000
    and imosadmin/imos is a username and password for the database.
    After doing all this my other database services also stop working :(
    Please check the configurations which i made as well may be i am wrong somewhere.....
    For further info i am pasting my configuration files.
    Gateway Home C:\OraHome_1\network\admin\listener.ora
    LISTENER =
    (ADDRESS_LIST=
         (ADDRESS=(PROTOCOL=tcp)(HOST=zahid)(PORT=1522))
         (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY)))     
    SID_LIST_LISTENER=
    (SID_LIST=
    (SID_DESC=
    (SID_NAME=tg4msql)
    (ORACLE_HOME=C:\OraHome_1)
    (PROGRAM=tg4msql)
    Rest everything is commented
    Oracle Database home C:\oracle\product\10.1.0\Db_1\NETWORK\ADMIN\listener.ora
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = zahid)(PORT = 1521))
    C:\oracle\product\10.1.0\Db_1\NETWORK\ADMIN\tnsnames.ora
    tg4msql=
    (DESCRIPTION=
    (ADDRESS= (PROTOCOL=TCP) (HOST=zahid) (PORT=1522) )
    (CONNECT_DATA=
    (SID=tg4msql))
    (HS=OK))

    ORA-12154 means that the Oracle database cannot resolve the tnsnames entry 'tg4msql'. Just make sure that your oracle database has the following entry in the $ORACLE_HOME/network/admin/tnsnames.ora entry:
    tg4msql=
    (DESCRIPTION=
    (ADDRESS=
    (PROTOCOL=TCP)(HOST=zahid)(PORT=1522)
    (CONNECT_DATA=
    (SID=tg4msql)
    (HS=OK)
    But checking your config you have...
    To start with, activate an sqlnet trace on your database, add following lines to the sqlnet.ora in your C:\oracle\product\10.1.0\Db_1\NETWORK\ADMIN\ path:
    TRACE_LEVEL_CLIENT=16
    TRACE_FILE_CLIENT=client.trc
    TRACE_FILE_DIRECTORY=C:\TEMP
    and restart your SQL*Plus session and try the select again. This should generate a sqlnet client trace which hopefully will show why the database cannot resolve 'tg4msql' to the tnsnames.ora entry specified. For example are you using the TNS_ADMIN variable?
    Regards,
    Ed

  • Ora - 03121

    I have installed the ODBC software on an NT workstation. When I run the 'Oracle ODBC Test' application I can successfully make a connection to a connx.cdd odbc database using an 'ODBC data source'. Then I can successfully use sql queries on the connx system.
    However, when I try to connect using Oracle Reports6i or Forms 6i using the same 'ODBC data source' an 'ORA - 03121 No interface driver connected' error message appears.
    The connect string that I am using for Reports6i and Forms6i is:
    obdc:rjtest and/or odbc:rjtest:connx.cdd
    Any ideas on what the problem is?
    Thanks
    rj
    null

    this question is best directed to the reports or forms forums do to the specific issues of connecting to those products.

  • MS Visual Studio 2005 + Oracle 10g = Cannot connect to ODBC error: 12154

    Hi there!
    I've read so many threads of same kind of problems but always some key elements seems to be missing so I cannot solve my problem with the solutions in those threads. So, I'll do my own.
    Our environment is...
    We have Oracle 8 database with all the data that we have. Now we have our new server, SQL Server 2005 installed and I am trying to transfer data from Oracle to SQL using MS Visual Studio 2005 using available ODBC drivers. System is Windows 2003 64Bit on intel based hardware.
    Current installations and settings
    I have installed Oracle 10g 32bit and 64bit to separate foldes. Then I made tnsnames and sqlnet files with right settings to specified folders and tested connection with tnsping <servername> command.
    Both, 64bit and 32bit connections are working. (Used 32bit CMD for 32bit connection test)
    ODBC
    I added Microsoft ODBC for Oracle as 32bit driver and Oracle 10g driver for 64bit environment as ODBC driver.
    Both environments uses same ODBC names: Myserver and Mytestserver
    Debug
    First, when I only had 64bit version of ODBC, I had a warning which said that I am using incompatible version of ODBC driver. Then I read from here that I can install 32bit client also and use drivers from that on 32bit ODBC environment and get rid of that message.
    Tried to connect Oracle DB with SQL-Plus and it works.
    Visual studio 2005 SP2
    I have tried to use .Net Providers/Oracle Client dataprovider and .Net Providers for OleDB/Microsoft Old DB for Oracle and also .Net Providers for OldDB/Oracle provider for OldDB
    Frist two gives me an error: ORA-12154 TNS: Could not resolve the connect identifier specified
    Last one says that OraOldDB.oracle.1 is not registered on local machine
    I have absolutily no idea what I can try next?
    Anyone who has more ideas? Suggest anything. I might have tried that already, but give a shot anyway. :)
    Message was edited by:
    user640570

    Hi,
    From where you got Oracle 10g driver for 64bit environment as ODBC driver. I am searching for the same.
    Are you got solution. I am facing same problem.
    Thanks,
    Vijay
    Edited by: user3976154 on Sep 6, 2008 5:12 PM

  • ORA-28500: connection from ORACLE to a non-Oracle system returned this message: ORA-02063: preceding line from OWB_75

    ORA-28500: connection from ORACLE to a non-Oracle system returned this message: ORA-02063: preceding line from OWB_75
    Scenario:
    I am having difficulty getting ODBC connection between Oracle OWB app with an 11gR2 DB (running on a VirtualBox Linux) and SQL Server 2008 running directly on the host. (Windows 8)
    I am trying to take a SQL Server 2008 feed into Oracle Ware house Builder, and think(!) I have read everything and configured it in accordance (but I presume not given 3 days of failed attempts to fix it). I have also read several blogs, hence there might be a few more settings in the configuration files than the formal documentation says, but these have come from blogs that have “Solved” problems for other similar situations.
    The environments:
    HOST:
    Name: RESOLVEIT-PC
    IP: 192.168.1.80
    Windows 8 (64bit) , with system DSN ODBC connection ACME_POS created with 32 bit ODBC set up (This setting still shows up fine in the 64 bit ODBC).
    GUEST VM:
    Name: OraDBSvr.com
    GUES fixed IP Address: 192.1.200
    Oracle VirtualBox (4.2.16)
    Oracle Redhat Linux 6 (x86)
    Oracle 11gR2 Enterprise Edition (11.2.0.1.0)
    ODBC: Freetds driver
    Configuration files:
    initacmepos.ora
    HS_FDS_CONNECT_INFO = 192.168.1.80/SQLEXPRESS/ACME_POS
    HS_FDS_TRACE_LEVEL = 0
    HS_FDS_SUPPORT_STATISTICS=FALSE
    HS_RPC_FETCH_REBLOCKING= OFF
    HS_FDS_FETCH_ROWS = 1
    HS_FDS_SHAREABLE_NAME = /usr/local/lib/libtdsodbc.so
    set ODBCINI=/opt/odbc/odbc.ini
    # set <envvar>=<value>
    odbc.ini
    [ACME_POS]
    Driver     = FreeTDS
    Description = ODBC Connection via FreeTDS
    Trace       = 1
    Servername  = 192.168.1.80
    Database    = dbo
    odbcinst.ini
    [PostgreSQL]
    Description                        = ODBC for PostgreSQL
    Driver                   = /usr/lib/psqlodbc.so
    Setup                    = /usr/lib/libodbcpsqlS.so
    Driver64                              = /usr/lib64/psqlodbc.so
    Setup64                              = /usr/lib64/libodbcpsqlS.so
    FileUsage                           = 1
    [MySQL]
    Description                        = ODBC for MySQL
    Driver                   = /usr/lib/libmyodbc5.so
    Setup                    = /usr/lib/libodbcmyS.so
    Driver64                              = /usr/lib64/libmyodbc5.so
    Setup64                              = /usr/lib64/libodbcmyS.so
    FileUsage                           = 1
    [FreeTDS]
    Discription             = TDS driver (Sybase / MS SQL)
    Driver                           = /usr/local/lib/libtdsodbc.so
    # Setup                         = /usr/local/lib/libtdsS.so
    FileUsage                           = 1
    CPTimeout               =
    CPReuse                 =
    [oracle@oraDBsvr etc]$
    freetds.conf
    #   $Id: freetds.conf,v 1.12 2007-12-25 06:02:36 jklowden Exp $
    # This file is installed by FreeTDS if no file by the same
    # name is found in the installation directory. 
    # For information about the layout of this file and its settings,
    # see the freetds.conf manpage "man freetds.conf". 
    # Global settings are overridden by those in a database
    # server specific section
    [global]
            # TDS protocol version
    ;              tds version = 4.2
                   # Whether to write a TDSDUMP file for diagnostic purposes
                   # (setting this to /tmp is insecure on a multi-user system)
    ;              dump file = /tmp/freetds.log
    ;              debug flags = 0xffff
                   # Command and connection timeouts
    ;              timeout = 10
    ;              connect timeout = 10
                   # If you get out-of-memory errors, it may mean that your client
                   # is trying to allocate a huge buffer for a TEXT field.
                   # Try setting 'text size' to a more reasonable limit
                   text size = 64512
    # A typical Sybase server
    [egServer50]
                   host = symachine.domain.com
                   port = 5000
                   tds version = 5.0
    # A typical Microsoft server
    [ACME_POS]
      host = 192.168.1.80
      port = 60801                                # also tried 1433
      instance = SQLEXPRESS
      tds version = 8.0
      client charset = UTF-8
    tsql -LH 192.168.1.80
         ServerName RESOLVEIT-PC
       InstanceName SQLEXPRESS
        IsClustered No
            Version 10.50.4000.0
                tcp 60801
                 np \\RESOLVEIT-PC\pipe\MSSQL$SQLEXPRESS\sql\query
                via RESOLVEIT-PC,0:1433
    Oracle listener:
    [oracle@oraDBsvr log]$ cat /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    # listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = acmepos)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (PROGRAM = dg4odbc)
    (HS = OK)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = oraDBsvr)(PORT = 1521))
    ADR_BASE_LISTENER = /u01/app/oracle
    [oracle@oraDBsvr log]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 16-SEP-2013 13:57:41
    Copyright (c) 1991, 2009, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oraDBsvr)(PORT=1521)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date                16-SEP-2013 13:50:34
    Uptime                    0 days 0 hr. 7 min. 7 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oraDBsvr/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraDBsvr)(PORT=1521)))
    Services Summary...
    Service "acmepos" has 1 instance(s).
    Instance "acmepos", status UNKNOWN, has 1 handler(s) for this service...
    Service "dw" has 1 instance(s).
    Instance "dw", status READY, has 1 handler(s) for this service...
    Service "dwXDB" has 1 instance(s).
    Instance "dw", status READY, has 1 handler(s) for this service...
    The command completed successfully
    Oracle tnsnames.ora
    [oracle@oraDBsvr admin]$ cat tnsnames.ora
    # tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
    # Generated by Oracle configuration tools.
    dw =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = dw)
    acmepos  =
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
    (CONNECT_DATA=(SID=acmepos)
    (HS=OK)
    Oracle sqlnet.ora
    [oracle@oraDBsvr admin]$ cat sqlnet.ora
    # sqlnet.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
    # Generated by Oracle configuration tools.
    NAMES.DIRECTORY_PATH= (EZCONNECT, TNSNAMES)
    ADR_BASE = /u01/app/oracle
    I can connect from the linux server to SQL Server, and query the database:
    [oracle@oraDBsvr etc]$ tsql -S acme_pos -U acme_dw_user -P acme1234
    locale is "en_US.utf8"
    locale charset is "UTF-8"
    using default charset "UTF-8"
    1> select last_name from dbo.employees;
    2> go
    last_name
    Davolio
    Fuller
    Leverling
    Peacock
    Buchanan
    Suyama
    King
    Callahan
    Dodsworth
    (9 rows affected)
    1>
    However, I can’t get a response through Oracle OWB , and I get:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message: ORA-02063: preceding line from OWB_75
    In the hs log file I get:
    [oracle@oraDBsvr log]$ cat acmepos_agt_3821.trc
    Oracle Corporation --- MONDAY    SEP 16 2013 13:51:22.170
    Heterogeneous Agent Release
    11.2.0.1.0
    HS Gateway:  NULL connection context at exit
    [oracle@oraDBsvr log]$
    I am really stuck now and going round in circles and can’t see the wood for trees! Can anyone please help?!!
    Many Thanks.
    Rafe.

    Let us rewrite your ODBC DSN a little bit... Your current odbc.ini looks like:
    [ACME_POS]
    Driver     = FreeTDS
    Description = ODBC Connection via FreeTDS
    Trace       = 1
    Servername  = 192.168.1.80
    Database    = dbo
    Let us change it a little bit so that we only need one config file - no odbcinst.ini nor freetds.conf file anymore:
    [ACME_POS]
    Driver =/usr/local/lib/libtdsodbc.so
    Server = 192.168.1.80
    Database
    = dbo     ####  I have some doubts that you have a SQL Server database called dbo - one database that always exists is master - so as a test use master here or get the real database name of the SQL Server database you want to connect
    Port = 60801 ## make sure it really is the correct port - best would be to check on the SQL server and then try telnet <ip> <port> if you can connect to the SQL server
    TDS_Version = 8.0
    QuotedId=YES
    Especially the last 2 parameters are mandatory. TDS_Version specifies the TDS Version you have to use to connect to the SQL Server and QuotedID is required for DG4ODBC as it surrounds objevt names by double quotes.
    What happens now when you try to connect with for example isql - the ODBC test utility shipped with the ODBC Driver manager?
    In addition, could you please do me another favour and check the word size of DG4ODBC and the ODBC Driver Manager as well as the ODBC Driver - just execute:
    file /u01/app/oracle/product/11.2.0/dbhome_1/bin/dg4odbc
    file /usr/local/lib/libtdsodbc.so
    file < the patch to your libodbc.so library>/libodbc.so
    and post the output.

  • Connecting on ODBC to an old installation of 7.1 running on DEC Unix 4.0f

    We are attempting to connect on ODBC to an existing installation of Oracle 7.1.6.2 running on DEC Unix 4.0f, and are facing a problem.
    The TCP/IP adaptor is installed (using CD of Oracle 7.2) and the listener service is running.
    We are unable to connect to the server from our client (client is a PC in windows).
    The error reported is ORA 12500
    Any input will be helpful
    Tx

    The newer technology stacks (e.g. .NET data access) requires higher versions of Oracle, which in turn is not compatible with that old server.
    The long gone Microsoft ODBC for Oracle driver, was built with Oracle7 in mind (but 7.3), but I can't remember ever seeing it with Sql*net v1. In any case you would need to get your hands on a 7.x Client for Windows, which may not be easy, and then you need to get it to install, which probably means you need an old version of Window.
    Even if some combination do exist, you will be far off from supported (or supportable) territory. Why can't you upgrade? Developing a new app for such an old environment seems ver far fetched. Are there no other options available to you?
    Message was edited by:
    orafad

  • ORA-28500: connection from ORACLE to a non-Oracle system

    Hi, I need to connect to a OWB mysql database, but when making a query in sql plus sends me this error.
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [Generic Connectivity Using ODBC][H006] The init parameter
    <HS_FDS_CONNECT_INFO> is not set. Please set it in init<orasid>.ora file.
    ORA-02063: preceding 2 lines from MYSQLINK
    listener.ora
    # listener.ora Network Configuration File: C:\oraclebi\db\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
         (SID_NAME = PLSExtProc)
         (ORACLE_HOME = C:\oraclebi\db)
         (PROGRAM = extproc)
         (SID_DESC =
         (SID_NAME = MYSQL)
         (ORACLE_HOME = C:\oraclebi\db)
         (PROGRAM = hsodbc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (ADDRESS = (PROTOCOL = TCP)(HOST = bi.oratechla.com)(PORT = 1521))
    tnsnames.ora
    # tnsnames.ora Network Configuration File: C:\oraclebi\db\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    BISE1DB =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = bi.oratechla.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = bise1db)
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    OTCL_MORDOR =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.31.210)(PORT = 1620))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = TEST)
    MYSQL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = bi.oratechla.com)(PORT = 1521))
    (CONNECT_DATA =
    (SID = MYSQL))
    (HS = OK)
    inithMYSQL.ora
    # This is a sample agent init file that contains the HS parameters that are
    # needed for an ODBC Agent.
    # HS init parameters
    HS_FDS_CONNECT_INFO = MYSQL
    HS_FDS_TRACE_LEVEL = off
    # Environment variables required for the non-Oracle system
    #set <envvar>=<value>
    system dsn --> MYSQL
    databaselink
    CREATE PUBLIC DATABASE LINK mysqlink CONNECT TO "oracle" IDENTIFIED BY "oracle" using 'ejemplo';
    Database link created.
    select * from empleado@mysqlink;
    ERROR at line 1:
    ORA-12154: TNS:could not resolve the connect identifier specified
    or
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [Generic Connectivity Using ODBC][H006] The init parameter
    <HS_FDS_CONNECT_INFO> is not set. Please set it in init<orasid>.ora file.
    ORA-02063: preceding 2 lines from MYSQLINK
    tnsping
    C:\Documents and Settings\Administrator>tnsping MYSQL
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 06-AUG-2
    010 06:31:57
    Copyright (c) 1997, 2005, Oracle. All rights reserved.
    Used parameter files:
    C:\oraclebi\db\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = bi.orate
    chla.com)(PORT = 1521)) (CONNECT_DATA = (SID = MYSQL)) (HS = OK))
    OK (30 msec)

    Use the setup failing with
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [Generic Connectivity Using ODBC][H006] The init parameter
    <HS_FDS_CONNECT_INFO> is not set. Please set it in init<orasid>.ora file.
    ORA-02063: preceding 2 lines from MYSQLINK
    There is a typo in the name of you gateway init file. You posted the content of inithMYSQL.ora but the naming is init<SID>.ora which is in your case initMYSQL.ora.
    In addition please keep in mind HSODBC has been desupported since 2008 and when starting a new configuration you should use the follow up product dg4odbc (Database Gateway for ODBC) V11.

Maybe you are looking for