Oracle Dsn Drivers For Mac
Posted By admin On 21.02.20'I recently learned that: 1) 64-bit Windows has two ODBC Data Source admin utilities - a) the default is found in the Windows system32 folder b) the other (same named of.exe) is found in the Windows SysWOW64 folder; c) these two utilities manage distinct sets of DSNs and ODBC drivers - one cannot see those that the other sees. (They use different registry sections.) 2) The OBIEE BI Admin Tool uses the ODBC DSNs that are managed by the second (1b) above. 3) Installing the Oracle 10g Client (either 32-bit or 64-bit) on a Windows x64 server creates an ODBC driver that is seen by the first (1a) above but not the second. This should lead to an obvious problem, which should have been well-covered by now - how can OBIEE installed on an x64 box access the Oracle ODBC client driver and create DSNs for Oracle DB instances?
Since I cannot find many references and no clear answer on OTN or via Google search, I suspect something above is incorrect - perhaps (3)? Can anyone suggest a resolution, please? On my x64 Windows server, I have two ODBC Data Source programs - one (x86) can see the Oracle 10g DB (and SQL Server) ODBC drivers, and the other (x64) can see all the ODBC drivers except for Oracle 10g DB (including BI Server, MS Access, another SQL Server driver, and the default DSN for AnalyticsWeb).
The latter does have the MS driver for Oracle - should I use that, since the Oracle ODBC driver is unavailable in that context? Is there any way to get the Oracle (Oracle in Ora10g) driver into the x64 ODBC Data Source Admin? Of course, I want to use this in order to import tables for new connection pools. When I try to use the native Oracle (OCI) 10g driver instead of the (inaccessible) ODBC system DSNs to import tables in the BI Admin tool on this x64 box, I get an nQSError 46029: Failed to load the DLL D: Apps OracleBI server Bin nqsdbgatewayoci10g.dll. Check if 'Oracle OCI 10G' database client is installed.
This DLL file is actually present in the specified path, and I can connect to the database from this server via SQL Plus, which demonstrates that the 10g DB client is installed and working. What does it mean when a DLL is physically present but inaccessible to a program?
I suspect it's a problem registering the DLL with windows, although I don't know much about Windows. Thanks in advance for help.' I don't know this for sure, but doesn't it make sense that you'd have to run the 32 bit Oracle client instead of 64? In an effort to keep the whole stack the same bitdepth? I had trouble getting the install working for a long time on Vista 64, until I switched to the 32-bit JDK instead of 64 bit. Also, the Analytics Web shows up in the 32bit admin but not 64 bit. From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Monday, March 09, 2009 11:26 AM To: Jeff McQuigg Subject: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows I recently learned that: 1) 64-bit Windows has two ODBC Data Source admin utilities - a) the default is found in the Windows system32 folder b) the other (same named of.exe) is found in the Windows SysWOW64 folder; c) these two utilities manage distinct sets of DSNs and ODBC drivers - one cannot see those that the other sees.
(They use different registry sections.) 2) The OBIEE BI Admin Tool uses the ODBC DSNs that are managed by the second (1b) above. 3) Installing the Oracle 10g Client (either 32-bit or 64-bit) on a Windows x64 server creates an ODBC driver that is seen by the first (1a) above but not the second. This should lead to an obvious problem, which should have been well-covered by now - how can OBIEE installed on an x64 box access the Oracle ODBC client driver and create DSNs for Oracle DB instances? Since I cannot find many references and no clear answer on OTN or via Google search, I suspect something above is incorrect - perhaps (3)? Can anyone suggest a resolution, please? On my x64 Windows server, I have two ODBC Data Source programs - one (x86) can see the Oracle 10g DB (and SQL Server) ODBC drivers, and the other (x64) can see all the ODBC drivers except for Oracle 10g DB (including BI Server, MS Access, another SQL Server driver, and the default DSN for AnalyticsWeb). The latter does have the MS driver for Oracle - should I use that, since the Oracle ODBC driver is unavailable in that context?
Is there any way to get the Oracle (Oracle in Ora10g) driver into the x64 ODBC Data Source Admin? Of course, I want to use this in order to import tables for new connection pools. When I try to use the native Oracle (OCI) 10g driver instead of the (inaccessible) ODBC system DSNs to import tables in the BI Admin tool on this x64 box, I get an nQSError 46029: Failed to load the DLL D: Apps OracleBI server Bin nqsdbgatewayoci10g.dll.
Check if 'Oracle OCI 10G' database client is installed. This DLL file is actually present in the specified path, and I can connect to the database from this server via SQL Plus, which demonstrates that the 10g DB client is installed and working. What does it mean when a DLL is physically present but inaccessible to a program? I suspect it's a problem registering the DLL with windows, although I don't know much about Windows.
Thanks in advance for help. Toolbox siebel-analytics-lBut it is in the 64-bit, isn't it? Anyway, it's visible through Windows SysWOW64 odbcad32.exe, not Windows system32 odbcad32.exe. (I keep trying to push that in front of Windows gurus, in hopes that they will make clear what that means, but to no avail.) Anyway, I have asked a DBA to install the 32-bit Oracle client (not sure if that's what we had the first time), to see if that helps.
Kind regards, Michael Krantz mikek@ethos.net 214-803-8122 - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Tuesday, 10 March 2009 19:17 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows I don't know this for sure, but doesn't it make sense that you'd have to run the 32 bit Oracle client instead of 64? In an effort to keep the whole stack the same bitdepth? I had trouble getting the install working for a long time on Vista 64, until I switched to the 32-bit JDK instead of 64 bit.
Odbc Dsn Oracle
Also, the Analytics Web shows up in the 32bit admin but not 64 bit. From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Monday, March 09, 2009 11:26 AM To: Jeff McQuigg Subject: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows I recently learned that: 1) 64-bit Windows has two ODBC Data Source admin utilities - a) the default is found in the Windows system32 folder b) the other (same named of.exe) is found in the Windows SysWOW64 folder; c) these two utilities manage distinct sets of DSNs and ODBC drivers - one cannot see those that the other sees. (They use different registry sections.) 2) The OBIEE BI Admin Tool uses the ODBC DSNs that are managed by the second (1b) above. 3) Installing the Oracle 10g Client (either 32-bit or 64-bit) on a Windows x64 server creates an ODBC driver that is seen by the first (1a) above but not the second. This should lead to an obvious problem, which should have been well-covered by now - how can OBIEE installed on an x64 box access the Oracle ODBC client driver and create DSNs for Oracle DB instances? Since I cannot find many references and no clear answer on OTN or via Google search, I suspect something above is incorrect - perhaps (3)? Can anyone suggest a resolution, please?
On my x64 Windows server, I have two ODBC Data Source programs - one (x86) can see the Oracle 10g DB (and SQL Server) ODBC drivers, and the other (x64) can see all the ODBC drivers except for Oracle 10g DB (including BI Server, MS Access, another SQL Server driver, and the default DSN for AnalyticsWeb). The latter does have the MS driver for Oracle - should I use that, since the Oracle ODBC driver is unavailable in that context? Is there any way to get the Oracle (Oracle in Ora10g) driver into the x64 ODBC Data Source Admin? Of course, I want to use this in order to import tables for new connection pools. When I try to use the native Oracle (OCI) 10g driver instead of the (inaccessible) ODBC system DSNs to import tables in the BI Admin tool on this x64 box, I get an nQSError 46029: Failed to load the DLL D: Apps OracleBI server Bin nqsdbgatewayoci10g.dll. Check if 'Oracle OCI 10G' database client is installed. This DLL file is actually present in the specified path, and I can connect to the database from this server via SQL Plus, which demonstrates that the 10g DB client is installed and working.
What does it mean when a DLL is physically present but inaccessible to a program? I suspect it's a problem registering the DLL with windows, although I don't know much about Windows.
Thanks in advance for help. Well I hope that works - let us know the results Jeff From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Tuesday, March 10, 2009 6:28 PM To: Jeff McQuigg Subject: Re: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Toolbox siebel-analytics-lBut it is in the 64-bit, isn't it? Anyway, it's visible through Windows SysWOW64 odbcad32.exe, not Windows system32 odbcad32.exe.
(I keep trying to push that in front of Windows gurus, in hopes that they will make clear what that means, but to no avail.) Anyway, I have asked a DBA to install the 32-bit Oracle client (not sure if that's what we had the first time), to see if that helps. Kind regards, Michael Krantz mikek@ethos.net 214-803-8122 - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Tuesday, 10 March 2009 19:17 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows I don't know this for sure, but doesn't it make sense that you'd have to run the 32 bit Oracle client instead of 64? In an effort to keep the whole stack the same bitdepth? I had trouble getting the install working for a long time on Vista 64, until I switched to the 32-bit JDK instead of 64 bit. Also, the Analytics Web shows up in the 32bit admin but not 64 bit.
From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Monday, March 09, 2009 11:26 AM To: Jeff McQuigg Subject: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows I recently learned that: 1) 64-bit Windows has two ODBC Data Source admin utilities - a) the default is found in the Windows system32 folder b) the other (same named of.exe) is found in the Windows SysWOW64 folder; c) these two utilities manage distinct sets of DSNs and ODBC drivers - one cannot see those that the other sees. (They use different registry sections.) 2) The OBIEE BI Admin Tool uses the ODBC DSNs that are managed by the second (1b) above. 3) Installing the Oracle 10g Client (either 32-bit or 64-bit) on a Windows x64 server creates an ODBC driver that is seen by the first (1a) above but not the second.
This should lead to an obvious problem, which should have been well-covered by now - how can OBIEE installed on an x64 box access the Oracle ODBC client driver and create DSNs for Oracle DB instances? Since I cannot find many references and no clear answer on OTN or via Google search, I suspect something above is incorrect - perhaps (3)?
Can anyone suggest a resolution, please? On my x64 Windows server, I have two ODBC Data Source programs - one (x86) can see the Oracle 10g DB (and SQL Server) ODBC drivers, and the other (x64) can see all the ODBC drivers except for Oracle 10g DB (including BI Server, MS Access, another SQL Server driver, and the default DSN for AnalyticsWeb). The latter does have the MS driver for Oracle - should I use that, since the Oracle ODBC driver is unavailable in that context?
Is there any way to get the Oracle (Oracle in Ora10g) driver into the x64 ODBC Data Source Admin? Of course, I want to use this in order to import tables for new connection pools. When I try to use the native Oracle (OCI) 10g driver instead of the (inaccessible) ODBC system DSNs to import tables in the BI Admin tool on this x64 box, I get an nQSError 46029: Failed to load the DLL D: Apps OracleBI server Bin nqsdbgatewayoci10g.dll. Check if 'Oracle OCI 10G' database client is installed. This DLL file is actually present in the specified path, and I can connect to the database from this server via SQL Plus, which demonstrates that the 10g DB client is installed and working.
What does it mean when a DLL is physically present but inaccessible to a program? I suspect it's a problem registering the DLL with windows, although I don't know much about Windows. Thanks in advance for help.
I'm trying to do this right now as well and running into similar problems simply using MS Access - my 64bit Oracle client ODBC driver doesn't even show up in 32-bit MS-Access. Yet another Microsoft failure.
Toolbox siebel-analytics-l Sorry; the work on this particular server is low priority for us, so neither the DBA nor I will get to it soon. If you don't mind me asking, which of the two ODBC Data Source admin programs shows the Oracle client driver?
Perhaps the one in system32? And the one in SysWOW64 shows the MS Access driver? (Probably also means that MS Access will see the same drivers and DSNs as the latter.) If this is adding up the way I think it is for x64 boxes, then 64-bit (native) stuff shows up in the default ODBC DS admin in system32 and 32-bit stuff (compatibility mode, like OBIEE) shows up in the other ODBC admin program in SysWOW64. That would suggest that you should use the 32-bit Oracle client (what you suggested to me, neh?) or install 64-bit MS Access if available. Does MS provide 64-bit native software for their x64 OS? To their credit (i.e., anything they don't totally botch), I have seen SQL Server drivers show up in both ODBC admins on the same x64 box.
Perhaps this can be resolved by simply moving or copying the ODBC entries from the one registry area to the other? I fear any manual editing of the Windows registry, and this is probably an uncommon/untested/not-recommended operation, but it could work. If you try it, be sure to first save a copy of the registry and set a system restore checkpoint. Set another checkpoint after, if you don't restore to the first. Michael K - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Thursday, 12 March 2009 18:20 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Any luck?
I'm trying to do this right now as well and running into similar problems simply using MS Access - my 64bit Oracle client ODBC driver doesn't even show up in 32-bit MS-Access. Yet another Microsoft failure. I also tried copying the registry entries for the ODBC definition - FAIL. You probably read the same post I did. I have 64bit Oracle on a machine, and tried to get the 32 bit client running on the same box.
When I did that, I had an Oracle ODBC driver in both, although each had a different ORAHOME. But even before that, I can't get the 32bit client to connect to the 64-but Listener.
I think that If I can get that to work, then everything else would work. If that doesn't work, then I'll wipe out 64bit Oracle with 32bit, and I'll do 100% 32bit stack from DB, Client, ODBC, Office, and OBI. So, before I did 32bit client, the Oracle driver was in the system32 ODBC (the 64bit one), but Access reads the WOW64 one (32 bit), which is where Analytics Web is as they are both 32bit apps. I wonder if I should install 32bit client into the same Ora home as 64bit - I'm afraid to do that.
I think the trick has to be the listener - that's where the 32 can synch with the 64 bit, just as it does when I connect a different 32bit client to my 64 bit listener over the network. I don't know how to make it work tho, but will play around with it a bit more before I give up and put 32 bit oracle on the box. Mine is only a dev box, so what do I even need a 64 bit DB for? This 64 bit stuff is such a CF. Jeff From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Friday, March 13, 2009 12:36 AM To: Jeff McQuigg Subject: Re: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Toolbox siebel-analytics-l Sorry; the work on this particular server is low priority for us, so neither the DBA nor I will get to it soon. If you don't mind me asking, which of the two ODBC Data Source admin programs shows the Oracle client driver? Perhaps the one in system32?
And the one in SysWOW64 shows the MS Access driver? (Probably also means that MS Access will see the same drivers and DSNs as the latter.) If this is adding up the way I think it is for x64 boxes, then 64-bit (native) stuff shows up in the default ODBC DS admin in system32 and 32-bit stuff (compatibility mode, like OBIEE) shows up in the other ODBC admin program in SysWOW64. That would suggest that you should use the 32-bit Oracle client (what you suggested to me, neh?) or install 64-bit MS Access if available. Does MS provide 64-bit native software for their x64 OS? To their credit (i.e., anything they don't totally botch), I have seen SQL Server drivers show up in both ODBC admins on the same x64 box. Perhaps this can be resolved by simply moving or copying the ODBC entries from the one registry area to the other?
I fear any manual editing of the Windows registry, and this is probably an uncommon/untested/not-recommended operation, but it could work. If you try it, be sure to first save a copy of the registry and set a system restore checkpoint. Set another checkpoint after, if you don't restore to the first. Michael K - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Thursday, 12 March 2009 18:20 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Any luck? I'm trying to do this right now as well and running into similar problems simply using MS Access - my 64bit Oracle client ODBC driver doesn't even show up in 32-bit MS-Access.
Yet another Microsoft failure. Toolbox siebel-analytics-l Nope. I never saw any suggestion that I should copy registry entries - it just seemed to be a reasonable next step. Thanks for saving me the trouble. Thanks for clarifying system32 is for 64-bit; the names are confusing, but I suppose system32 has always been system home and the new thing is for compatibility. I don't have to deal with a 64-bit DB on this project, nor a DB on the same box as the client.
It shouldn't matter, but why not see if a 32-bit client running on a different box can connect to your 64-bit listener? - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Friday, 13 March 2009 13:57 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows I also tried copying the registry entries for the ODBC definition - FAIL. You probably read the same post I did. I have 64bit Oracle on a machine, and tried to get the 32 bit client running on the same box. When I did that, I had an Oracle ODBC driver in both, although each had a different ORAHOME.
But even before that, I can't get the 32bit client to connect to the 64-but Listener. I think that If I can get that to work, then everything else would work. If that doesn't work, then I'll wipe out 64bit Oracle with 32bit, and I'll do 100% 32bit stack from DB, Client, ODBC, Office, and OBI. So, before I did 32bit client, the Oracle driver was in the system32 ODBC (the 64bit one), but Access reads the WOW64 one (32 bit), which is where Analytics Web is as they are both 32bit apps. I wonder if I should install 32bit client into the same Ora home as 64bit - I'm afraid to do that. I think the trick has to be the listener - that's where the 32 can synch with the 64 bit, just as it does when I connect a different 32bit client to my 64 bit listener over the network. I don't know how to make it work tho, but will play around with it a bit more before I give up and put 32 bit oracle on the box.
Mine is only a dev box, so what do I even need a 64 bit DB for? This 64 bit stuff is such a CF. Jeff From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Friday, March 13, 2009 12:36 AM To: Jeff McQuigg Subject: Re: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Toolbox siebel-analytics-l Sorry; the work on this particular server is low priority for us, so neither the DBA nor I will get to it soon. If you don't mind me asking, which of the two ODBC Data Source admin programs shows the Oracle client driver? Perhaps the one in system32?
And the one in SysWOW64 shows the MS Access driver? (Probably also means that MS Access will see the same drivers and DSNs as the latter.) If this is adding up the way I think it is for x64 boxes, then 64-bit (native) stuff shows up in the default ODBC DS admin in system32 and 32-bit stuff (compatibility mode, like OBIEE) shows up in the other ODBC admin program in SysWOW64.
That would suggest that you should use the 32-bit Oracle client (what you suggested to me, neh?) or install 64-bit MS Access if available. Does MS provide 64-bit native software for their x64 OS?
To their credit (i.e., anything they don't totally botch), I have seen SQL Server drivers show up in both ODBC admins on the same x64 box. Perhaps this can be resolved by simply moving or copying the ODBC entries from the one registry area to the other? I fear any manual editing of the Windows registry, and this is probably an uncommon/untested/not-recommended operation, but it could work. If you try it, be sure to first save a copy of the registry and set a system restore checkpoint. Set another checkpoint after, if you don't restore to the first.
Michael K - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Thursday, 12 March 2009 18:20 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Any luck? I'm trying to do this right now as well and running into similar problems simply using MS Access - my 64bit Oracle client ODBC driver doesn't even show up in 32-bit MS-Access.
Yet another Microsoft failure. Well, it looks like everything is working on it now - not really sure what changed from Friday to today aside from a reboot. I was able to get the 32bit Oracle Client to connect to the 64bit listener, and the 32 bit ODBC driver works just fine from both MS Access and also OBI. So, all is well now. From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Saturday, March 14, 2009 6:59 AM To: Jeff McQuigg Subject: Re: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Toolbox siebel-analytics-l Nope.
I never saw any suggestion that I should copy registry entries - it just seemed to be a reasonable next step. Thanks for saving me the trouble. Thanks for clarifying system32 is for 64-bit; the names are confusing, but I suppose system32 has always been system home and the new thing is for compatibility. I don't have to deal with a 64-bit DB on this project, nor a DB on the same box as the client.
It shouldn't matter, but why not see if a 32-bit client running on a different box can connect to your 64-bit listener? - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Friday, 13 March 2009 13:57 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows I also tried copying the registry entries for the ODBC definition - FAIL. You probably read the same post I did. I have 64bit Oracle on a machine, and tried to get the 32 bit client running on the same box.
When I did that, I had an Oracle ODBC driver in both, although each had a different ORAHOME. But even before that, I can't get the 32bit client to connect to the 64-but Listener.
I think that If I can get that to work, then everything else would work. If that doesn't work, then I'll wipe out 64bit Oracle with 32bit, and I'll do 100% 32bit stack from DB, Client, ODBC, Office, and OBI. So, before I did 32bit client, the Oracle driver was in the system32 ODBC (the 64bit one), but Access reads the WOW64 one (32 bit), which is where Analytics Web is as they are both 32bit apps. I wonder if I should install 32bit client into the same Ora home as 64bit - I'm afraid to do that. I think the trick has to be the listener - that's where the 32 can synch with the 64 bit, just as it does when I connect a different 32bit client to my 64 bit listener over the network.
I don't know how to make it work tho, but will play around with it a bit more before I give up and put 32 bit oracle on the box. Mine is only a dev box, so what do I even need a 64 bit DB for? This 64 bit stuff is such a CF. Jeff From: michaelKr via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Friday, March 13, 2009 12:36 AM To: Jeff McQuigg Subject: Re: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Toolbox siebel-analytics-l Sorry; the work on this particular server is low priority for us, so neither the DBA nor I will get to it soon. If you don't mind me asking, which of the two ODBC Data Source admin programs shows the Oracle client driver?
Perhaps the one in system32? And the one in SysWOW64 shows the MS Access driver? (Probably also means that MS Access will see the same drivers and DSNs as the latter.) If this is adding up the way I think it is for x64 boxes, then 64-bit (native) stuff shows up in the default ODBC DS admin in system32 and 32-bit stuff (compatibility mode, like OBIEE) shows up in the other ODBC admin program in SysWOW64. That would suggest that you should use the 32-bit Oracle client (what you suggested to me, neh?) or install 64-bit MS Access if available. Does MS provide 64-bit native software for their x64 OS?
To their credit (i.e., anything they don't totally botch), I have seen SQL Server drivers show up in both ODBC admins on the same x64 box. Perhaps this can be resolved by simply moving or copying the ODBC entries from the one registry area to the other? I fear any manual editing of the Windows registry, and this is probably an uncommon/untested/not-recommended operation, but it could work. If you try it, be sure to first save a copy of the registry and set a system restore checkpoint. Set another checkpoint after, if you don't restore to the first. Michael K - Original Message - From: Jeff McQuigg via siebel-analytics-l Sent: Thursday, 12 March 2009 18:20 Subject: RE: siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Any luck? I'm trying to do this right now as well and running into similar problems simply using MS Access - my 64bit Oracle client ODBC driver doesn't even show up in 32-bit MS-Access.
Yet another Microsoft failure. I was able to get it to work. Take a look at the details here: -70-29882 Jeff M.
From: azuniga via siebel-analytics-l mailto:siebel-analytics-l@Groups.ITtoolbox.com Sent: Monday, September 21, 2009 8:09 AM To: Jeff McQuigg Subject: RE:siebel-analytics-l Oracle DB ODBC driver and DSN for OBIEE on 64-bit Windows Posted by azuniga (Programmer) on Sep 21 at 11:12 AM Mark this reply as helpfulMark as helpful I have same issue.Oracle10g 64-bit database and 32-bit client on same machine, different Oracle Home. In my path variable I have the 32-bit first then the 64-bit. I have my ORACLEHOME set to 32-bit client.
Any other setting that I would need to make this work? Thanks in advance. Looking for a OBIEE Expert for a long term project in TX. Here are the details OBIEE Senior Expert Glimpse of Responsibilities and Abilities ' Work directly with Business to gather and understand data model, reporting and data requirements. ' Based on requirements, create high level and technical design documentation. ' Lead and coordinate the development and unit testing process ' Support system and user acceptance testing activities, including issue management and resolution Preferences ' Relevant certification from Teredata ' Previous DA experience Requirements ' Relevant certification from Oracle Corp. ' Knowledge of Teradata ' Data modeling for data mart using Erwin or any other data modeling tool ' Strong technical knowledge of OBIEE admin/metadata tools, security, user interface designs, development and deployment of dashboards, analytics and performance management reports ' Experience in designing and implementing reports and analytics in OBIEE with experience in at least 2 OBIEE implementations ' Good working knowledge and experience with ETL/Data integration Sincerely, Arjun 678 370 9917 email@removed.
Configuring a DSN-less Connection Configuring a DSN-less Connection To connect to your data store through a DSN-less connection, you need to define the driver in the odbcinst.ini file and then provide a DSN-less connection string in your application. If your machine is already configured to use an existing odbcinst.ini file, then update that file by adding the settings described below.
Otherwise, copy the odbcinst.ini file from the Setup subfolder in the driver installation directory to the home directory, and then update the file as described below. To define a driver:.
Oracle Dsn Example
In a text editor, open the odbcinst.ini configuration file. ODBC Drivers Simba Oracle ODBC Driver=Installed Simba Oracle ODBC Driver Description= Simba Oracle ODBC Driver Driver=/Library/ simba/ oracleodbc/lib/lib oracleodbcsbu.dylib You can now connect to your data store by providing your application with a connection string where the Driver property is set to the driver name specified in the odbcinst.ini file, and all the other necessary connection properties are also set. For more information, see 'DSN-less Connection String Examples' in. For instructions about configuring SSL connections, see.
Odbc System Dsn Drivers
For detailed information about all the connection properties that the driver supports, see. Related topics.