September 26, 2011 at 9:56 am
Was hoping that I might get some advice on a problem I'm having setting up connectivity between Oracle and SQL Server. Briefly my company operates both Oracle and a SQL Server environments. I'm DBA for the latter.
The plan is to push data from Oracle to SQL Server via a sqljdbc driver. This works fine in a SQL Server 2005 32-bit test environment however fails in the SQL Server 2005 64-bit production environment - 'Could not load the DLL sqljdbc.dll, or one of the DLLs it references'.
Having, as far as I can see, carried out correctly all the instructions for deploying the sqljdbc driver, I thought maybe a 64-bit version might be required but can't seem to get my hands on one. Is one available and will this solve the problem or am I barking up the wrong tree?
YaHozna.
September 26, 2011 at 11:13 am
You'll need a 64-bit driver. Searching for "64 bit jdbc driver" in Bing gave some results. Not sure if they can be trusted or not, but should be easy enough for you to research them.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
September 27, 2011 at 1:58 am
Thanks for the response gSquared. I have located an MS 64-bit driver - sqljdbc_xa.dll. Unfortunately my 'colleagues' on the Oracle side aren't prepared to alter their processes to accomodate calls to that driver. I'll keep looking for an Oracle (IBM/Weblogic?) version.
Regards,
YaHozna.
September 28, 2011 at 7:09 am
Seem to have solved this one myself and, to save anyone else going through the same unnecessary pain of researching on Google, asking question in Forums such as this and generally tearing one's hair out, the solution is as follows, and is irritatingly simple: make sure the location of sqljdbc.dll has been added to the PATH environment variable.
It would appear that installing SQL Server 2005 (AND 2008) in a 64-bit environment results in paths beginning with C:\Program Files (x86) - the '32-bit path' for want of a better description - being added to the PATH environment variable. Those beginning with C:\Program Files - the '64-bit path' - however are not. Furthermore deployment instructions for sqljdbc.dll are to place it in the Binn subfolder of the instance's installation folder - e.g. C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn. This is where SQL Server is actually 'installed' in a 64-bit environment - i.e. where sqlservr.exe and other executables reside. However calls to the driver fail because the DLL can't be found. Unfortunately the advice in virtually every example of this happening I've come across is to acquire a 64-bit driver. Valid advice I'm sure in some cases but a bit of a red herring here.
Anyway, to summarise, I guess technically you could place the driver anywhere as long as you add its location to the PATH variable.
YaHozna.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply