Analytics Software

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 question, 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 DB (and SQL Server) ODBC drivers, and the other (x64) can see all the ODBC drivers except for Oracle 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 Native Oracle ODBC driver is unavailable in that context? Is there any way to get the native (Oracle in Ora10g) driver into the x64 ODBC Data Source Admin?

Thanks in advance for help.