ODBC Link ans SQL Server

Hi!
So I tried to create a ODBC link with SQL server, but there is a problem during the authentification process.
When I try to use authentification thanks to SQL server, even with 'sa' user enabled, this error shows up
Connection failed:
SQLState: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'myUser'.
When I try to use authentification with Windows ID, another error shows up :
Connection faled:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
The server is a VPS server and there is no domain to configure.
I already tried to switch to mixed authentification, with it I can easily connect to SQL server with SQL server Management Studio. I also already browsed SQL Server Configuration Manager in order to set a static (not dynamic) port, TCP/IP are enabled in SQL
server Network Configuration / Protocols for SQLEXPRESS but it still doesn't work. Ofc I restarted SQL server several times and I even tried to uninstall/reinstall it.
Finally, this error shows up when I start SQL Server agent with SQL server Configuration Manager.
>The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details.
I tried to find out what is the problem by reading the logs but there is nothing about the failed authentification attempts there. It only shows some services starting or stopping.
I read somewhere that it the VIA protocol could be the problem, but I can't find it anywhere in SQL Server Configuration Manager.
I've been struggling for days with this. you're my only hope
thanks!

I juste forgot to explain that I have to do this for a client who will use a software of my company and this software needs this ODBC link to communicate with SQL Server. Also the users will connect to the server in TSE (so the application will be on the
same server than SQL Server). I don't know if this detail is important but I prefer specify.
"If it works in SSMS to connect with a SQL Login, then it should work with ODBC by using the same server name/credentials from the sam Client."
I entered 'sa' user and another user that I created in SQL Server but I have the same error (login fail for user)
"Are remote Connections enabled? Is a Firewall running on server and/or Client side? If so unblock the required TCP and UDP ports."
Remote Connections are enabled on the server and there's just Windows Firewall on the server. I unblocked resquired TCP and UDP Ports. Even with the Windows Firewall turned off I have this problem.

Similar Messages

Can't select char type columns using ODBC link to SQL Server 2K

I have set up a db link using hsodbc from 8.1.7 to SQL Server 2000. I can select numeric and date columns from the
SQL Server table with no problem. But any character datatype (nchar or nvchar) column name included in the query
returns an ORA-00904 ("invalid column name"). I know the column names are valid for SQL Server and can access
these columns via EXCEL using the same user id and data source that is used for the link. I don't have a clue as to why ORACLE can't "see" the character type columns. Following is the hs trace file (HS_FDS_TRACE_LEVEL = debug) generated for "select assay_name from bio_assay@sqlsrvl":
FRIDAY SEP 05 2003 10:39:47.674
(0) hoagprd(2); Entered.
(0) [Generic Connectivity Using ODBC] version: 2.0.4.0.0010
(0) connect string is:
(0) YEAR2000_POLICY=-1;CTL_DEBUG=T;CONSUMER_API=1;SESSION_BEHAVIOR_FLAGS=4;PARSER_-
(0) DEPTH=2000;EXEC_FLAGS =
(0) 131080;defTdpName=SQLSRVL;binding=(SQLSRVL,ODBC,"LIBERTY");
(0) ORACLE GENERIC GATEWAY Log File Started at 05-Sep-03 10:39:47
(0) Class version: 65
(0) hoagprd(2); Exited with retcode = 0.
(0) hoainit(3); Entered.
(0) hoainit(3); Exited with retcode = 0.
(0) hoalgon(7); Entered. name = XXXXXXXXXXX.
(0) Created new ODBC connection (28382608)
(0) Silent DB Function!!
(0) (Last message occurred 4 times)
(0) hoalgon(7); Exited with retcode = 0.
(0) hoaulcp(4); Entered.
(0) hoaulcp(4); Exited with retcode = 0.
(0) hoauldt(5); Entered.
(0) hoauldt(5); Exited with retcode = 0.
(0) hoabegn(9); Entered. formatID = 306206, hoagttid
(0) =XXXXXXXXXXXXXXXXXXXXXXXX, hoagtbid = , tflag = 0, initial = 1
(0) hoabegn(9); Exited with retcode = 0.
(0) hoapars(15); Entered. stmtType = 0, id = 1.
(0) nvOUT (P:\Src\QP\QP_SQTXT.C 55): SELECT * FROM "BIO_ASSAY"
(0) odbc_rec: select * from "BIO_ASSAY"
(0) Silent DB Function!!
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 929):
(0) SELECT "T0000"."WH_ADDED_DATE" AS c00010, "T0000"."ASSAY_MODIFIED_TIME" AS c0009, "T0000"."ASSAY_CREATED_TIME" AS c0008, "T0000"."ASSAY_DATE_COMPLETED" AS c0007, "T0000"."ASSAY_DATE_PLANNED" AS c0006, "T0000"."ASSAY_DATE_STARTED" AS c0005, "T0000"."ASSAY_STATUS_NO" AS c0004, "T0000"."TIMEFRAME_KEY" AS c0003, "T0000"."TARGET_KEY" AS c0002, "T0000"."ENVIRONMENT_KEY" AS c0001, "T0000"."ASSAY_KEY" AS c0000 FROM "BIO_ASSAY" T0000
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 932):
(0) <<<<<<<<<<<<<<<<<<< Execution Strategy Begin <<<<<<<<<<<<<<<<<<<<<<<<<<<<
(0) Original SQL:
(0) SELECT * FROM "BIO_ASSAY"
(0)
(0)
(0) Accessing Database "SQLSRVL" with SQL:
(0) SELECT "T0000"."WH_ADDED_DATE" AS c00010, "T0000"."ASSAY_MODIFIED_TIME" AS c0009, "T0000"."ASSAY_CREATED_TIME" AS c0008, "T0000"."ASSAY_DATE_COMPLETED" AS c0007, "T0000"."ASSAY_DATE_PLANNED" AS c0006, "T0000"."ASSAY_DATE_STARTED" AS c0005, "T0000"."ASSAY_STATUS_NO" AS c0004, "T0000"."TIMEFRAME_KEY" AS c0003, "T0000"."TARGET_KEY" AS c0002, "T0000"."ENVIRONMENT_KEY" AS c0001, "T0000"."ASSAY_KEY" AS c0000 FROM "BIO_ASSAY" T0000
(0)
(0)
Execution Strategy End >>>>>>>>>>>>>>>>>>>>>>>>>>>>(0) hoapars(15); Exited with retcode = 0.
(0) hoaopen(19); Entered. id = 1.
(0) hoaopen(19); Exited with retcode = 0.
(0) hoadscr(16); Entered. id = 1.
(0) hoastmt(195); Array fetch size is: 1.
(0) ------ hoadscr() -------:
(0) hoadamsz: 11, hoadasiz: 11, hoadambr: 1, hoadabrc: 1
(0) row 0 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 0 - hoadascl: 0, hoadanul: 0, hoadanml: 9, hoadanam: ASSAY_KEY, hoadabfl:
(0) 20, hoadamod: 0
(0) row 1 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 1 - hoadascl: 0, hoadanul: 0, hoadanml: 15, hoadanam: ENVIRONMENT_KEY,
(0) hoadabfl: 20, hoadamod: 0
(0) row 2 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 2 - hoadascl: 0, hoadanul: 1, hoadanml: 10, hoadanam: TARGET_KEY,
(0) hoadabfl: 20, hoadamod: 0
(0) row 3 - hoadambl: 20, hoadadty: 134, hoadaprc: 19, hoadacst: 0
(0) row 3 - hoadascl: 0, hoadanul: 0, hoadanml: 13, hoadanam: TIMEFRAME_KEY,
(0) hoadabfl: 20, hoadamod: 0
(0) row 4 - hoadambl: 2, hoadadty: 7, hoadaprc: 5, hoadacst: 0
(0) row 4 - hoadascl: 0, hoadanul: 1, hoadanml: 15, hoadanam: ASSAY_STATUS_NO,
(0) hoadabfl: 2, hoadamod: 0
(0) row 5 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 5 - hoadascl: 0, hoadanul: 1, hoadanml: 18, hoadanam: ASSAY_DATE_STARTED,
(0) hoadabfl: 7, hoadamod: 0
(0) row 6 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 6 - hoadascl: 0, hoadanul: 1, hoadanml: 18, hoadanam: ASSAY_DATE_PLANNED,
(0) hoadabfl: 7, hoadamod: 0
(0) row 7 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 7 - hoadascl: 0, hoadanul: 1, hoadanml: 20, hoadanam:
(0) ASSAY_DATE_COMPLETED, hoadabfl: 7, hoadamod: 0
(0) row 8 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 8 - hoadascl: 0, hoadanul: 0, hoadanml: 18, hoadanam: ASSAY_CREATED_TIME,
(0) hoadabfl: 7, hoadamod: 0
(0) row 9 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 9 - hoadascl: 0, hoadanul: 1, hoadanml: 19, hoadanam: ASSAY_MODIFIED_TIME,
(0) hoadabfl: 7, hoadamod: 0
(0) row 10 - hoadambl: 0, hoadadty: 0, hoadaprc: 0, hoadacst: 0
(0) row 10 - hoadascl: 0, hoadanul: 0, hoadanml: 13, hoadanam: WH_ADDED_DATE,
(0) hoadabfl: 0, hoadamod: 0
(0) hoadscr(16); Exited with retcode = 0.
Note, the query I entered doesn't appear and I never entered the query "select * from bio_assay" - it appears that this is
automatically generated by the hsodbc process and raises other questions (like wouldn't this return a lot of unneeded
data ?). It also appears that the "select * from bio_assay" gets translated somehow into a select statement listing each column - however, non of the columns listed are character type columns like assay_name.
Does this make sense to anyone? Any ideas ? HELP !

Remote view gives the same error. I think the problem has to do with nchar and nvchar fields. It seems that the hsodbc agent issues a "select * from bio_assay" at the beginning of the session (see above trace).
0) odbc_rec: select * from "BIO_ASSAY"
(0) Silent DB Function!!
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 929):
(0) SELECT "T0000"."WH_ADDED_DATE" AS c00010, "T0000"."ASSAY_MODIFIED_TIME" AS c0009, "T0000"."ASSAY_CREATED_TIME" AS c0008, "T0000"."ASSAY_DATE_COMPLETED" AS c0007, "T0000"."ASSAY_DATE_PLANNED" AS c0006, "T0000"."ASSAY_DATE_STARTED" AS c0005, "T0000"."ASSAY_STATUS_NO" AS c0004, "T0000"."TIMEFRAME_KEY" AS c0003, "T0000"."TARGET_KEY" AS c0002, "T0000"."ENVIRONMENT_KEY" AS c0001, "T0000"."ASSAY_KEY" AS c0000 FROM "BIO_ASSAY" T0000
Apparently, the list of fields that is returned from the "select *" does not include any of the nchar or nvchar type columns. After this initial "select *" the oracle server only looks at the initial list of columns and gives an "invalid column" error for any fields that are not in this initial list. So the question is: how do I make the hsodbc agent see the nchar/nvchar type fields and include them in the initial list ? I've tried setting the HS_NLS_LANGUAGE and HS_NLS_NCHAR parameters but these seem to have no effect.
Any clue as to what's going on ?

Link to SQL Server fails

Oracle: 11gR2 on Linux and tryed following the instructions found on (therefore some generic stuff inside the files):
http://www.gotodba.com/install-and-configure-db-link-to-sql-server-database-in-linux.html
Steps:
Step 1
Installed FreeTDS and configured /etc/unixODBC/odbc.ini with the following:
[ODBC Data Sources]
MYDB2=IBM DB2 ODBC DRIVER
SQLDB=FreeTDS
[SQLDB]
Driver = /usr/local/freetds/lib/libtdsodbc.so
#Driver = /usr/lib64/libodbc.so
Server = 10.0.0.9
Database = komspom_kanc
Port = 3488
TDS_Version = 8.0
Afterwards I can successfully login to the SQL server using:
isql -v SQLDB <userid> <password>
Step 2
Created the initSQLDB.ora file in $ORACLE_HOME/hs/admin with the lines:
# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
# HS init parameters
HS_FDS_CONNECT_INFO = SQLDB
HS_FDS_TRACE_LEVEL = 0
HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
HS_DB_NAME = SQLDB
HS_DB_DOMAIN = GOTODBA.COM
HS_FDS_SUPPORT_STATISTICS = FALSE
# ODBC specific environment variables
set ODBCINI=/etc/unixODBC/odbc.ini
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
Step 3
Added the following lines to listener.ora:
SID_LIST_LISTENER_TWNYCSLD04=
(SID_LIST=
(SID_DESC =
(ORACLE_HOME = /shared/app/komisija/product/11.2.0/dbhome_1)
(SID_NAME = SQLDB)
(PROGRAM = dg4odbc)
(ENVS=LD_LIBRARY_PATH=/usr/lib64:/usr/local/freetds/lib:/shared/app/komisija/product/11.2.0/dbhome_1/lib)
and reloaded the listener:
lisnrctl reload
Step 4
Added the following line to tnsnames.ora:
SQLDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = linux1.kons.gov.ba)(
(CONNECT_DATA =
(SERVICE_NAME = SQLDB)
(HS = OK)
afterwards tnsping SQLDB runs fine...
Step 5
Created a link as sys:
create database link sqldb.gotodba.com
connect to user
identified by "password"
using 'SQLDB';
But after I run
select * from "myTable"@sqldb.gotodba.com;
I get:
ERROR at line 1:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from SQLDB.GOTODBA.COM
What could be wrong and how to test where exactly shit hits the fan, pardon my language :)

Ok, my bad... Was editing the listener.ora blindly instead of reading the documentation. I think ths should now be more or less correct?
# listener.ora Network Configuration File: /shared/app/komisija/product/11.2.0/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = linux1.kons.gov.ba )(PORT = 1521))
ADR_BASE_LISTENER = /shared/app/komisija
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC =
(ORACLE_HOME = /shared/app/komisija/product/11.2.0/dbhome_1)
(SID_NAME = SQLDB)
(PROGRAM = dg4odbc)
(ENVS=LD_LIBRARY_PATH=/usr/lib64:/usr/local/freetds/lib:/shared/app/komisija/product/11.2.0/dbhome_1/lib)
lsnrctl status now returns:
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 16-MAY-2011 20:03:38
Uptime 0 days 0 hr. 5 min. 58 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /shared/app/komisija/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /shared/app/komisija/diag/tnslsnr/linux1/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=linux1.kons.gov.ba)(PORT=1521)))
Services Summary...
Service "SQLDB" has 1 instance(s).
Instance "SQLDB", status UNKNOWN, has 1 handler(s) for this service...
Service "orcl" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully
However the select now returns:
SQL> select * from "tblAktiCX"@sqldb;
select * from "tblAktiCX"@sqldb
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
And that's it..no error message... where to go from here?

DB Link to SQL Server (11gR2 64-bit Windows 7)

Without going into all the gruesome details, it is mostly straightforward to set up a DB Link to SQL Server from an Oracle 10 instance on 32 bit Windows 7. However I simply cannot get the link to work on 11gR2. I tried the simplistic ds4odbc interface and the more complex SQL Server gateway. Nothing works. The connection always times out. Has anyone been able to create a SQL Server DB link from 11gR2 on Windows 7? (The Oracle instance is 32 bit. The OS is 64 bit). I know Win7 is unsupported at present.
Edited by: user2190753 on Oct 14, 2010 4:51 PM

Hi,
first of all you need to check the ODBC connectivity between Oracle and SQL Server and the Data source,try to load data from oracle to Sql Server to check the ODBC connection is working properly and then create database link from sql server to oracle ,you can create stored procedures in SQL server to get data from Oracle to sql server or Oracle PL/SQL Packages to data from sql server to Oracle Database
To setup ODBC and datasource
see this link
http://www.databasejournal.com/features/oracle/article.php/3442661/Making-a-Connection-from-Oracle-to-SQL-Server.htm
and then create link server in sql server after you test connenction with oracle

How could I create a "Linked Server" link from SQL Server 2008R2 64-Bit to Oracle Database 11.2 64-Bit?

How could I create a "Linked Server" link from SQL Server 2008R2 64-Bit to Oracle Database 11.2 64-Bit?
Let's say the SQL Server and Oracle Database are in the same Company Internet Network.
I have the code, but I do not know how to use it. Such as what is System DSN Name? Where could I get it. What does it look like?
Do I need to install any Oracle Client Software in order to link from SQL Server to Oracle? Or SQL Server has the built-in drivers installed already that I can directly create a Linked Server from SQL Server to Oracle?
I need to know details. Thanks.
USE master
go
EXEC sp_addlinkedserver
     @server  = '{Linked Server Name}'
    ,@srvproduct = '{System DSN Name}'
    ,@provider  = 'MSDASQL'
    ,@datasrc  = '{System DSN Name}'
EXEC sp_addlinkedsrvlogin
     @rmtsrvname = '{Linked Server Name}'
    ,@useself  = 'False'
    ,@locallogin = NULL
    ,@rmtuser  = '{Oracle User Name}'
    ,@rmtpassword = '{Oracle User Password}'

You need an OLE DB provider for Oracle. There is one that ships with Windows, but it only supports very old versions of Oracle. Oracle has an OLE DB provider that you can use. I don't know if it's part of Oracle Client or how it is bundled.
You should not use MSDASQL or any DSN.
Erland Sommarskog, SQL Server MVP, [email protected]

Specifying Partner Failover in odbc.ini for Linux ODBC driver for SQL Server

Hi,
We are trying to specify the partner failover when making connections via Linux ODBC driver for SQL Server. Do you know a way to specify partner failover in the DSN entry in odbc.ini?
We are using Linux ODBC driver for SQL Server and unixODBC DriverManager.
Our DSN is:
[MyDSN]
Driver=ODBC Driver 11 for SQL Server
Description=MyDSN
Server=MySERVER,<port>
I also tried to use the following connection string in Python (via pyodbc) bypassing the DSN and connecting using the server name.
cnxn = pyodbc.connect("Server=server1,<port>;UID=sa;PWD=<pwd>;Driver=ODBC Driver 11 for SQL Server;Failover_Partner=Server2,<port2>;Database=MyDB")
If the standby DB is on server1 connection fails. It doesn't try server2. If the DB is principal on server1 connection succeeds.
Thank you,
Liviu
LLL

Hello,
Did you use ODBC Driver for SQL Server to connect to database that uses database mirroring?
According to
the BOL,it does not list "Failover_Partner" as ODBC Driver for Linux connection string keywords.
But ODBC driver for Linux supports
AlwaysOn Availability Groups or Failover Cluster Instance by specify MultiSubnetFailover=True when connecting to a SQL Server 2012 availability group listener or SQL Server 2012 Failover Cluster Instance.
The following case is about similar issue and it seems that ODBC Driver on Linux does not recognize Failover_Partner in connection string. (Not test myself).You can refer to:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6a8b5223-066d-4493-84a3-b5374a32e433/native-client-on-linux-does-not-recognize-failoverpartner-in-connection-string?forum=sqldataaccess
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Data sources (ODBC) config -MS SQL Server linking

OS -WS2008 R2-64
I realize that the problems I'm experiencing are not one’s everyday’s activities and are falling quite astray of the regular Oracle dba work.
There is no other place to post but here as the MS SQL Server forums were not able to provide any solution so far.
I hope somebody could have experienced similar issues and could have solutions or at least to point to the right direction.
The box has a MS SQL Server 2008 that has to be linked with an Oracle 10g database on a different box(SunOS 5.10).
The source for the ODBC drivers supposed to be Oracle Client + ODAC.
The simple scenario of linking SQL Server to Oracle got developed into an ugly battle with Oracle drivers to be recognized by the SQL Server.
Numerous installations-de-installations of the Oracle Client 10g + ODAC and Oracle Client 11 + ODAC led to nowhere.
The major points of failures are:
1. The OracleMTS Recovery Service gets broken and can not start - the installation of ODAC fails.
Following the Metalink: Recreating Oracle MTS Recovery Service [ID 836137.1]
fails even with domain admin account - "access denied".
2. In case when the Oracle Client + ODAC get a successful installation:
- no effort could make the oracle drivers to ne recognized by the SQL server.
Even with config of Data Sources (ODBC) and successful connection test against the Oracle databases -> there is no way to have the oracle OraOLEDB.Oracle listed in the SQL Server dropdown window with available drivers.
3. Data Sources (ODBC) - fail to initiate reporting bogus reasons.
As there are 32 and 64 bit of applications (ODBC Managers) and corresponding – or not – drivers------ there is a reportedly confusion over the forums which drivers are for which OS.
The bottom line is – linking fails (something I have done successfully before).
I have the feeling there is something wrong with our environments, but have no way to prove it.
I’m posting with a little hope for help.
Thx,

WS2008 is 64 bit
MS SQL Server 2008 is 64-bit
Solaris is 64-bit
Oracle is 64-bit
Oracle's OLE DB - as OraOLEDB.Oracle
or Microsoft OLE DB Provider for ODBC Drivers (MSDASQL) .
The road block is that I can not configure a Data Sources (ODBC) - System DSN with any of OraOLEDB.Oracle or MSDASQL because they are not listed on the list of available drivers!!!!
Source for OraOLEDB.Oracle has to be the Client11g - ODAC installation. - at no avail
Source for MSDASQL should be the OS by itself as the driver is built in. - at no avail
(the SQL server recognizes the MSDASQ - listed under Linked servers providers).
As per the information from Microsoft and other forums - the mess is based upon 32 - 64 bit applications and drivers; on the way the installations were done.
Even the server administrator advises for a new installation.
Thx,

How to share and Access DB (.accdb) with global tables that link to SQL Server tables without having to define ODBC connections on each client PC?

I have an Access DB with quite a few Linked Tables that point to a SQL Server backend db. Currently I am using an ODBC connection defined on my pc, but I want other users to be able to download the .accdb file from a share and run. Will I have
to define this odbc connection on each client's pc? Is there a better way to do this without having to have each client manually set this up on their PC?

I have an Access DB with quite a few Linked Tables that point to a SQL Server backend db. Currently I am using an ODBC connection defined on my pc, but I want other users to be able to download the .accdb file from a share and run. Will
I have to define this odbc connection on each client's pc? Is there a better way to do this without having to have each client manually set this up on their PC?
Hi Jason,
I think you can automate that process. In each application I use a one-record-table in the FE with a field Connected. Connected is default False.
Starting a database in the development mode ignores this flag. Starting a database in production mode starts, if Not Connected, a procedure to RefreshLink the tables to the BE, and makes Connected = TRUE, so a next startup does not
result in a new RefreshLink.
Instead of a Boolean you could also use a string containing the path, or whatever you want.
Imb.

Database link to SQL Server Init error

Hi all,
i´m tryng to create a dblink between Oracle 10.2.0 in a RHEL4 and a SQL Server.
I can connect using isql but when i try using sqlplus i obtain this error:
SQL> CREATE DATABASE LINK dbl
CONNECT TO "user"
IDENTIFIED BY "pwd"
USING 'hsodbc'; 2 3 4
Enlace con la base de datos creado.
SQL> SELECT * FROM Table_1@dbl;
SELECT * FROM Table_1@dbl
ERROR en línea 1:
ORA-28545: error diagnosticado por Net8 al conectar a un agente (error in Net8 while connecting an agent)
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: 2 lines precediendo a DBL
This is the error explanantion in Oracle Docs:
I think the problem is the ini file inithsodbc.ora.
inithsodbc.ora
# This is a sample agent init file that contains the HS parameters that are
# needed for an ODBC Agent.
# HS init parameters
# AAB - Parametros para asociar un agente ODBC al HS
HS_FDS_CONNECT_INFO = MSQLS
HS_FDS_TRACE_LEVEL = ON
HS_FDS_SHAREABLE_NAME =/usr/local/freetds/lib/libtdsodbc.so
HS_AUTOREGISTER = true
# ODBC specific environment variables
set ODBCINI=/home/oracle/.odbc.ini
listener.ora
# listener.ora Network Configuration File: /app/oracle/oracle/product/10.2.0/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = STA2)
(ORACLE_HOME = /app/oracle/oracle/product/10.2.0/db_1)
     (SID_DESC = (SID_NAME=hsodbc)
(ORACLE_HOME=/app/oracle/oracle/product/10.2.0/db_1)
(PROGRAM=hsodbc)
                         (ENVS=LD_LIBRARY_PATH=/app/oracle/oracle/product/10.2.0/db_1/lib:/usr/local/lib)
LISTENER =
     (DESCRIPTION =
     (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = nemesisgr2.hi.inet)(PORT = 1521))
tnsnames.ora
# tnsnames.ora Network Configuration File: /app/oracle/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
DEVSTA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = nemesisgr.hi.inet)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = devSTA)
STA2 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = nemesisgr2.hi.inet)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = STA2)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
STA =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = nemesisgr2.hi.inet)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = STA)
#AAB - Descripcion de servicio para conectar con SQLServer
HSODBC = (DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)
(HOST=nemesisgr2.hi.inet)
(PORT=1521)
(CONNECT_DATA = (SID=hsodbc)
(HS = OK)
ODBC Files
odbc.ini
[ODBC Data Sources]
MSQLS = Microsoft SQL Server
[MSQLS]
Driver = /usr/local/freetds/lib/libtdsodbc.so
Description = Microsoft SQL Server
Trace = No
Servername = sqlserver
Database = master
[Default]
Driver = /usr/local/freetds/lib/libtdsodbc.so
odbcinst.ini
[PostgreSQL]
Description          = ODBC for PostgreSQL
Driver          = /usr/lib/libodbcpsql.so
Setup          = /usr/lib/libodbcpsqlS.so
FileUsage          = 1
[MSQLSDRIVER]
Description          = Driver for MS SQL Server
Driver          = /usr/local/freetds/lib/libtdsodbc.so
Setup          = /usr/lib64/libtdsS.so
FileUsage          = 1
UsageCount          = 5
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
[egServer70]
     host = ntmachine.domain.com
     port = 1433
     tds version = 7.0
# Test MS SQl Server
[sqlserver]
     Database = master
     host = pruebas.hi.inet
     port = 1433
     tds version = 7.0
Any ideas??
Thanks in advance.
Alex

I have changed the inithsodbc.ora file including:
HS_FDS_SHAREABLE_NAME =/usr/lib/libodbc.so (I have ODBC installed)
Here you are the other information:
lsnrctl status
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 23-OCT-2008 09:29:52
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Bienvenido a LSNRCTL, escriba "help" para obtener información.
LSNRCTL> status
Conectándose a (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=nemesisgr2.hi.inet)(PORT=1521)))
ESTADO del LISTENER
Alias LISTENER
Versión TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Fecha de Inicio 22-OCT-2008 19:31:34
Tiempo Actividad 0 días 13 hr. 58 min. 29 seg.
Nivel de Rastreo off
Seguridad ON: Local OS Authentication
SNMP OFF
Parámetros del Listener /app/oracle/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log del Listener /app/oracle/oracle/product/10.2.0/db_1/network/log/listener.log
Recibiendo Resumen de Puntos Finales...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nemesisgr2)(PORT=1521)))
Resumen de Servicios...
El servicio "STA" tiene 1 instancia(s).
La instancia "STA", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "STA2" tiene 2 instancia(s).
La instancia "STA2", con estado UNKNOWN, tiene 1 manejador(es) para este servicio...
La instancia "STA2", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "STA2XDB" tiene 1 instancia(s).
La instancia "STA2", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "STA2_XPT" tiene 1 instancia(s).
La instancia "STA2", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "STAXDB" tiene 1 instancia(s).
La instancia "STA", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "STA_XPT" tiene 1 instancia(s).
La instancia "STA", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "hsodbc" tiene 1 instancia(s).
La instancia "hsodbc", con estado UNKNOWN, tiene 1 manejador(es) para este servicio...
El comando ha terminado correctamente
LSNRCTL>
hsodbc
There is no output executing this command.
[oracle@nemesisgr2 ~]$ /app/oracle/oracle/product/10.2.0/db_1/bin/hsodbc
[oracle@nemesisgr2 ~]$
tnsping hsodbc
[oracle@nemesisgr2 ~]$ tnsping hsodbc
TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 23-OCT-2008 09:35:58
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Archivos de parámetros utilizados:
/app/oracle/oracle/product/10.2.0/db_1/network/admin/sqlnet.ora
Adaptador TNSNAMES utilizado para resolver el alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp) (HOST=nemesisgr2.hi.inet) (PORT=1521)) (CONNECT_DATA = (SID=hsodbc)) (HS = OK))
Realizado correctamente (40 mseg)
Rgds,
Alex

Linking to SQL Server from Oracle 10g on 64bit Linux

I have this working, so I thought I would post my steps.
In versions 8 to 10 of Oracle, the software for making these connections was known as Heterogeneous Services. It was 32bit only software and the actual binary file that was executed when querying a non oracle database was $ORACLE_HOME/bin/hsodbc. When a query was made to the linked database, a process was started on the machine with the name of hsodbcXXX (where XXX is the name of the DSN).
In version 11g of Oracle this software is now referred to as Database Gateways and there is a 64bit version as well as a 32bit version. The binary file that is executed in this case is $ORACLE_HOME/bin/dg4odbc.
Fortunately the 64bit Database Gateway software can also be used with Oracle 10g databases as long as it is up to version 10.2.03 and has the odbc compatibility patch installed. (5965763).
To make use of this, we need to install the 11g ODBC Gateway into a separate ORACLE_HOME and start a listener from that environment. We can then make use of that listener from the 10g environment.
So here is what I did to get this working: (Note: DSN = MyDSN)
1.     Download and install 64bit ODBC driver with support for 64-bit ULEN from Easysoft. The file is named odbc-sqlserver-1.1.4-linux-x86-64-ul64.tar. You'll need to email Easysoft support for the URL. Create the DSN entry as part of the install. At the end of the process it can test the DSN. The query should come back with info about the SQL Server. Test the connection using isql from the /opt/easysoft/unixODBC/bin directory to verify that it works as well (/opt/easysoft/unixODBC/bin/isql –v MyDSN). Note, I installed easysoft driver under /opt rather than the /usr/local which is the default. /usr/local/easysoft is a symlink to /opt/easysoft.
2.     Install ODBC gateway via the 11g Gateways installer. You can do a custom install and deselect all but the ODBC Gateway component. (http://download.oracle.com/otn/linux/oracle11g/linux.x64_11gR1_gateways.zip)
3.     Create a /home/oracle/11g_environment.sh script that sets 11g ORACLE_HOME, PATH, and LD_LIBRARY_PATH variables. It should look something like this:
#set ORACLE ENV vars for 11g
ORACLE_HOME=/u01/app/oracle/product/11.1.0/tg_1 # (assuming that is where ODBC Gateway was installed)
PATH=/bin:/usr/bin:/u01/app/oracle/product/11.1.0/tg_1/bin:/opt/easysoft/bin:/opt/easysoft/unixODBC/bin
LD_LIBRARY_PATH=/opt/easysoft/lib:/opt/easysoft/unixODBC/lib:/u01/app/oracle/product/11.1.0/tg_1/lib
export ORACLE_HOME
export PATH
export LD_LIBRARY_PATH
4.     Create $ORACLE_HOME/hs/admin/initMyDSN.ora, $ORACLE_HOME/network/admin/listener.ora, and $ORACLE_HOME/network/admin/tnsnames.ora under 11g structure. They are as follows:
initMyDSN.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=MyDSN
HS_FDS_TRACE_LEVEL=0
HS_FDS_TRACE_FILE_NAME=MyDSN.trc
HS_FDS_SHAREABLE_NAME=/opt/easysoft/unixODBC/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
# ODBC specific environment variables
#set ODBCINI=/etc/odbc.ini
#set ODBCINSTINI=/etc/odbcinst.ini
#set LD_LIBRARY_PATH=/opt/easysoft/lib:/opt/easysoft/unixODBC/lib:/u01/app/oracle/product/11.1.0/lib
#set PATH=$PATH:/opt/easysoft/unixODBC/bin:/opt/easysoft/bin/
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
listener.ora
MyDSN =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1522))
SID_LIST_MyDSN =
(SID_LIST =
(SID_DESC=
(SID_NAME=MyDSN)
(ORACLE_HOME = /u01/app/oracle/product/11.1.0/tg_1)
(PROGRAM=dg4odbc)
(ENVS=LD_LIBRARY_PATH=/opt/easysoft/lib:/opt/easysoft/unixODBC/lib:/u01/app/oracle/product/11.1.0/tg_1/lib)
tnsnames.ora
# tnsnames.ora Network Configuration File:
# Generated by Oracle configuration tools.
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
MyDSN =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST=localhost)(PORT=1522))
(CONNECT_DATA=(SID=MyDSN))
(HS=OK)
5.     Add another entry for MyDSN in /u01/app/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora so tnsping works in 10g environment as well.
MyDSN =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST=localhost)(PORT=1522))
(CONNECT_DATA=(SID=MyDSN))
(HS=OK)
*** Notice that the MyDSN listener runs on a different port (1522) as it is a separate listener.
6.     Login to machine as user oracle and source the 11g environment script. “source ~/11g_environment.sh”. Now start the listener. “cd $ORACLE_HOME/bin”. “./lsnrctl start MyDSN”.
7.     Login to a new shell as user oracle with a 10g environment.
8.     Run sqlplus and create the database link. “CREATE PUBLIC DATABASE LINK SQLSERVER connect to “<someuser>” IDENTIFIED BY “<somepass>” USING ‘MyDSN’;”
9.     test the link. “select * from information_schema.tables@SQLSERVER;”
If it is successfull, you should see a system process named "dg4odbcMyDSN".

So what have you found out for yourself so far (considering the solution to this is easily found on the web)?
Have you looked up Heterogeneous Services?

Linking to SQL Server using DG4ODBC

Hi all,
I've configured Oracle 11g R1 for Windows 2003 Server 32-bit to connect to MS SQL Server 2005 through ODBC.
Following is the error I got when I try to access SQL Server by the db link in Oracle:
SQL> select sysdate from dual@sqls ;
select sysdate from dual@sqls
ERROR at line 1:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from SQLSThe ODBC link to the SQL Server was successfully tested.
The listener, however, returned error as shown below.
/* The file E:\Oracle\OraDb11g\hs\admin\initsqls.ora */
HS_FDS_CONNECT_INFO = sqls
HS_FDS_TRACE_LEVEL = 1
/* Listener.ora */
LISTENER =
(ADDRESS_LIST=
      (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
SID_LIST_LISTENER=
(SID_LIST=
      (SID_DESC=
         (SID_NAME=sqls)
         (ORACLE_HOME=E:\Oracle\OraDb11g)
         (PROGRAM=dg4odbc)
/* tnsnames.ora */
sqls =
(DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
    (CONNECT_DATA=(SID=sqls))
    (HS=OK)
/* sqlnet.ora */
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT, HOSTNAME)
/* testing the connection */
E:\Oracle\OraDb11g\BIN>tnsping sqls
TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 14-JUN-2
010 09:36:35
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
E:\oracle\OraDb11g\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT
=1521)) (CONNECT_DATA=(SID=sqls)) (HS=OK))
OK (20 msec)
/* code to create the db link */
CREATE PUBLIC DATABASE LINK sqls CONNECT TO
"SRV11\Administrator" IDENTIFIED BY "ospassword" using 'sqls';
/* Contents of Listener Log */
Mon Jun 14 11:25:59 2010
14-JUN-2010 11:25:59 * trc_level * 0
14-JUN-2010 11:26:06 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=Administrator))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=185599488)) * status * 0
Mon Jun 14 11:26:22 2010
14-JUN-2010 11:26:22 * (CONNECT_DATA=(SID=sqls)(CID=(PROGRAM=)(HOST=WORKGROUP\SRV10)(USER=SRV10\Administrator))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=3333)) * establish * sqls * 12505
TNS-12505: TNS:listener does not currently know of SID given in connect descriptorAny hint is appreciated.

You did create a DUAL table in the Sqlserver database?
Sybrand Bakker
Senior Oracle DBA

I can't link to an I series (IBM AS400) server from my sql server 2014 server (64 bit) -- but yes can link on sql server 2005 (32 bit)

I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big). I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64
bit). There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change? How can I get this I series server to link to my sql server 2014 server?
USE [master]
GO
/****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
GO
Rich P

Thank you for this reply. I went to the link and selected the option for DB2s and ran the install. Then I started up SSMS. I copied the same script as above, and it executed successfully. But when I try to run a query against
a table in a database on this linked sever -- I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 8
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Do I need to change the line containing -- @provider=N'MSDASQL', maybe?
this is the query I'm running:
select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
The same exact query runs fine on the sql server 2005 linked server. Is there something I need to configure?
Rich P

ORA-28545: error diagnosed by Net8 for DG4ODBC for link with SQL Server

Database: 11.2.0 Windows 32-bit (on WindowsXP SP3)
ORACLE_HOME = D:\Oracle\Product\11.2.0\dbhome
GATEWAY_HOME = D:\Oracle\Product\11.2.0\tg
odbc : sqlserver (working... i can import table's data in MS Excel) its ok...
D:\Oracle\Product\11.2.0\dbhome\hs\admin\initsqlserver.ora
# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
# HS init parameters
HS_FDS_CONNECT_INFO = sqlserver
HS_FDS_TRACE_LEVEL = 0
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
D:\Oracle\Product\11.2.0\dbhome\NETWORK\ADMIN\listener.ora
# listener.ora Network Configuration File: D:\Oracle\Product\11.2.0\dbhome\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = orcl)
(ORACLE_HOME = D:\Oracle\Product\11.2.0\dbhome)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:D:\Oracle\Product\11.2.0\dbhome\bin\oraclr11.dll")
(SID_DESC=
(SID_NAME=sqlserver)
(ORACLE_HOME = D:\Oracle\Product\11.2.0\dbhome)
(PROGRAM = dg4odbc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.20.0.32)(PORT = 1521))
ADR_BASE_LISTENER = D:\Oracle\Product\11.2.0\dbhome
Listener Status
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.20.0.32)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date 30-SEP-2011 11:13:53
Uptime 0 days 0 hr. 0 min. 24 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File D:\Oracle\Product\11.2.0\dbhome\network\admin\listener
.ora
Listener Log File d:\oracle\product\11.2.0\dbhome\diag\tnslsnr\stylo-dba
\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.20.0.32)(PORT=1521)))
Services Summary...
Service "orcl" has 1 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Service "sqlserver" has 1 instance(s).
Instance "sqlserver", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL>
D:\Oracle\Product\11.2.0\dbhome\NETWORK\ADMIN\tnsnames.ora
# tnsnames.ora Network Configuration File: D:\Oracle\Product\11.2.0\dbhome\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.20.0.32)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
sqlserver =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.20.0.32)(PORT=1521))
(CONNECT_DATA =
(SID=sqlserver))
(HS = OK)
TNS PING Restult
C:\Documents and Settings\Administrator>tnsping sqlserver
TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 30-SEP-2
011 11:15:47
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
D:\Oracle\Product\11.2.0\dbhome\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=172.20.0.32)(PO
RT=1521)) (CONNECT_DATA = (SID=sqlserver)) (HS = OK))
OK (50 msec)
C:\Documents and Settings\Administrator>
Database Link
create database link sqlserver connect to uoracle identified by uoracle using 'sqlserver';
SQL>
SQL> select from sysobjects@sqlserver*
ERROR:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from DG4ODBC
SQL>
Waiting for help. What thing im missing.....

Hi Naeem,
You have said the install setup is -
ORACLE_HOME = D:\Oracle\Product\11.2.0\dbhome
GATEWAY_HOME = D:\Oracle\Product\11.2.0\tg
but in the listener.ora you have set ORACLE_HOME for the gateway as -
(ORACLE_HOME = D:\Oracle\Product\11.2.0\dbhome)
To use DG4ODBC installed in the 'tg' ORACLE_HOME then you should configure a listener in the gateway OH -
D:\Oracle\Product\11.2.0\tg\network\admin
and start this listener. This listener will need to use a different port from the RDBMS listener in the other OH.
Change the gateway tnsnames.ora entry used by the RDBMS to reflect this port change.
One other point - SQL*Server is case sensitive so you may need to create the database link as -
create database link sqlserver connect to "uoracle" identified by "uoracle" using 'sqlserver';
if the user/password are defined in lower case in SQL*Server.
Also, the same for object names depending on the SQL*Server configuration -
select "column_name" from "owner"."table_name"@sqlserver ;
Regards,
Mike
Edited by: mkirtley on Sep 30, 2011 8:12 AM

Strange problem with an Oracle database link to SQL Server

Hi gurus,
Please help me on this problem.
We have an Oracle 10R2 database link to a SQL Server 2000 database. I can select count(*) from The_SQL_Server_Table@myOracleLink, and I can describe The_SQL_Server_Table@myOracleLink, but I cannot select Column1 from The_SQL_Server_Table@myOracleLink! I am getting the ORA-00904: "COLUMN1": invalid identifier error.
Could anyone tell me what is wrong here? By the way, the same user name can select all the columns in The_SQL_Server_Table through ODBC from the client app. But I need the DB link to work with some Oracle stored functions.
Thank you!
Ben

myora9i wrote:
Hi gurus,
Please help me on this problem.
We have an Oracle 10R2 database link to a SQL Server 2000 database. I can select count(*) from The_SQL_Server_Table@myOracleLink, and I can describe The_SQL_Server_Table@myOracleLink, but I cannot select Column1 from The_SQL_Server_Table@myOracleLink! I am getting the ORA-00904: "COLUMN1": invalid identifier error.
Could anyone tell me what is wrong here? By the way, the same user name can select all the columns in The_SQL_Server_Table through ODBC from the client app. But I need the DB link to work with some Oracle stored functions.
Thank you!
Bennotice "COLUMN1" is different from "Column1"
CaSe MaTTerS!

ODBC Drivers for SQL Server 2005 on AIX for OWB connect

Hi All -
I have a problem whereby I am trying to connect OWB with SQL Server 2005. The problem statement follows: -
Infrastructure: -
OWB Server installed on AIX
Oracle Installed on AIX
SQL Server 2005 source on Windows
OWB Client on windows XP
My problem is: -
I am trying to connect OWB with SQL Server 2005 for which I have to create heterogenous source entry in Oracle home. But AIX box does not have any ODBC drivers installed and hence I can not configure a DSN on the same. Can any one suggest where can I get these drivers and their installation steps.
Thanks in advance!
Arun
Edited by: Uni.... on Jun 2, 2009 10:50 PM

I was not able to find DG4ODBC anywhere.
Somehow I managed to get a copy of Data Drivers from Data Direct and configured ODBC.INI file as below: -
ODBC Data Sources
DB2 Wire Protocol=DataDirect 6.0 DB2 Wire Protocol
Informix Wire Protocol=DataDirect 6.0 Informix Wire Protocol
Oracle Wire Protocol=DataDirect 6.0 Oracle Wire Protocol
Sybase Wire Protocol=DataDirect 6.0 Sybase Wire Protocol
Teradata=DataDirect 6.0 Teradata
SQLServer Wire Protocol=DataDirect 6.0 SQL Server Wire Protocol
MySQL Wire Protocol=DataDirect 6.0 MySQL Wire Protocol
PostgreSQL Wire Protocol=DataDirect 6.0 PostgreSQL Wire Protocol
Greenplum Wire Protocol=DataDirect 6.0 Greenplum Wire Protocol
ODBC
IANAAppCodePage=4
InstallDir=/u01/app/ODBC
Trace=0
TraceFile=odbctrace.out
TraceDll=/u01/app/ODBC/lib/odbctrac.so
AMS
Driver=/u01/app/ODBC/lib/ddmsss24.so
Description=DataDirect 6.0 SQL Server Wire Protocol
Address=10.240.20.154,1433
Database=AMS
My TNSName.Ora file is shown below: -
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/10/db/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
DWHDEV =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = aixdevdb2)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = DWHDEV)
AMS =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.240.20.154)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = AMS)
(HS = OK)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
Listener.Ora file is as below: -
# listener.ora Network Configuration File: /u01/app/oracle/product/10/db/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/10/db)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = AMS)
(ORACLE_HOME = /u01/app/oracle/product/10/db)
(PROGRAM = hsodbc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = aixdevdb2)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
INITHSODBC file for this source is initAMS.ora is configured as: -
HS_FDS_CONNECT_INFO = AMS
HS_FDS_TRACE_LEVEL = 4
HS_FDS_TRACE_FILE_NAME = /u01/app/ODBC/log.log
HS_DB_NAME = MSSQL
HS_FDS_SHAREABLE_NAME = /u01/app/ODBC/lib/odbc.so
# ODBC specific environment variables
#set ODBCINI= /u01/app/ODBC/odbc.ini
I have tested the DSN created in ODBC.INI file using example appplication that comes by default with datadirect drivers and that is connecting to database and fetching data as per query supplied, but when I am trying to create connecting from OWB to SQL Server it is failing with following error: -
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from OWB_188
Even database link is giving same error message.
I have followed all the steps which are necessary to configure Heterogeneous connectiviyt including restarting listener, but no luck.
Any comments

ODBC Link ans SQL Server

Similar Messages

Maybe you are looking for