ODBC Oracle driver in Windows Home Basic Premium - oracle10g

I am using the operating system Windows Home Basic Premium. I installed Oracle 10g Express Edition also 11g, it installed correctly but when I would go for adding driver from ODBC I didn't find any Express driver.
That's why I can't run any Java database project; it shows me driver not loaded. This is first I face problem using any software.

First off, in general, you should not be using ODBC if you are developing a Java application. Java applications generally use the JDBC driver to connect to the database. It is possible to use a JDBC to ODBC bridge driver but that was really only appropriate years ago when not every database had a JDBC driver. There would be no reason to use a JDBC to ODBC bridge driver to connect to an Oracle database in an application built today.
That being said, are you using a 32-bit version of Windows or a 64-bit version of Windows? Did you install 32-bit versions of Oracle or 64-bit versions of Oracle? If you are using a 64-bit version of Windows, the default ODBC Driver Administrator will only display the 64-bit ODBC drivers that are installed. If you installed 32-bit versions of Oracle, you'll need to open the 32-bit ODBC Driver Administrator at C:\Windows\SysWOW64\odbcad32.exe in order to access the 32-bit ODBC drivers.

Related

DB2 ADO.NET connectors only installs 32-bit connectors

I am running the latest DB2 connectors installer at https://www.ibm.com/support/pages/download-initial-version-115-clients-and-drivers and downloading & installing "IBM Data Server Driver Package (DS Driver)"
It installs the 32-bit ADO.NET connectors and puts them in the 32-bit machine.config.
But it puts no entries in the 64-bit machine.config (I have 64-bit Windows 10).
How can I get the 64-bit connectors installed?
Just make sure you have selected the correct driver.
There are different download options for 32 and/or 64bit on that page.
And if that is the case, no worries.. who never did something like that!

How to create connection on SQL Developer?

i installed SQL Developer on my MacBook
when i tried to run the sql code it says must create new connection
it required username/password
so how can i solve this
before i was using oracle database XE 12 on windows 10
but now i am using macOS and i see i cant use this software anymore (oracle database XE 12)
so i tried to install SQL Developer
Oracle SQL Developer is a tool that lets you connect to an (Oracle) database. But - you have to have the database as well (apparently, there's none on your Mac).
Express Edition database you previously used on Windows 10 was (probably) 11g (not 12; it doesn't exist), but it woks on Windows an Linux - not macOS.
Moreover, none of the modern Oracle databases can be installed on Mac; the last one was, I think, 10g (but - as it is out of support, you can't even download it any more).
Therefore, you could install a virtual machine on Mac, put Windows OS onto it, download and install 11gXE along with SQL Developer and use it.
But, why bother? Install VirtualBox and then download one of Pre-Built Developer VMs (for Oracle VM VirtualBox).

Actuate 10 Information Object Designer with postgresql

I cannot figure out how add a new Data Connection Definition in Actuate 10 Information Object Designer. The odbc is postgresql but when I input a Data Connection Definition Type, postgresql is not an option.
is this becuase Actuate 10 is too outdated? It is hard to find any infomration on this since most Actuate users use BIRT now.
Any information on the Actuate 10 Information Object Designer, or materials I could read would be helpful.
Most likely you need to install the PostgreSQL ODBC driver.
One wrinkle there is that you might have a 64-bit system, and have installed the 64-bit PostgreSQL ODBC driver. If Actuate is a 32-bit executable it won't see the 64-bit driver. You will need to install the 32-bit PostgreSQL ODBC driver as well.
(The reverse is also true btw - 64-bit programs can't use the 32-bit driver either).

32bit and 64bit Versions of PostgreSQL 9.1 ODBC are Mixed Up

I've installed both the 32bit and 64bit versions of psqlODBC 9.1. When I configure both a 32bit and a 64bit System DSN they get written to the ODBC.ini file incorrectly:
[ODBC 32 bit Data Sources]
pg_crdb_latest=PostgreSQL Unicode (32 bit)
pg_crdb_latest_32=PostgreSQL Unicode(x64) (32 bit)
[pg_crdb_latest]
Driver32=C:\Program Files (x86)\psqlODBC\0901\bin\psqlodbc35w.dll
[pg_crdb_latest_32]
Driver32=C:\Program Files\psqlODBC\0901\bin\psqlodbc35w.dll
The pg_crdb_latest DSN was added using the 64bit ODBC Data Source Administrator. The pg_crdb_latest_32 DSN was added with the 32bit one.
FYI - I installed the 32bit version first, then the 64bit version.
The outcome is I get this error when trying to connect to PostgreSQL 9.1 64bit in SAS 9.2 64bit:
ERROR: CLI error trying to establish connection: [Microsoft][ODBC
Driver Manager] The specified DSN contains an architecture mismatch
between the Driver and Application
Any ideas how to set this right? I'm running Windows 7 Pro 64bit.
This link explains it all
http://www.easysoft.com/developer/interfaces/odbc/64-bit.html#odbc-windows
So two things:
Windows has very poor file and directory naming conventions regarding ODBC - hence the confusion
64bit PostgreSQL ODBC is currently very slow (10x slower than SAS to SQL 64bit via OLEDB) - I'll investigate this further

PostgreSQL ODBC Drivers on Windows 7 not showing up

I'm running win7 64bit so I installed the (psqlodbc_09_00_0300-x64.zip) msi 64bit drivers for postgres odbc.
i also tried launching the odbc manager from the following location "%systemdrive%\Windows\SysWoW64\odbcad32.exe"
But i still don't see any postgres drivers i can use.
Anyone know how to make them show up?
To setup DSN for 32-bit application you must use: %WINDIR%\SysWOW64\odbcad32.exe
and for 64-bit application you must use: %WINDIR%\System32\odbcad32.exe
see http://psqlodbc.projects.pgfoundry.org/faq.html#6.8
Typically in a case like this you want to install both the 64-bit drivers (for 64-bit programs) and the 32-bit drivers (for 32-bit programs). If this doesn't work you have two options:
Uninstall and reinstall. On reinstall disable antivirus software, etc. and anything else that may interfere with writing to the registry.
Run regsvr32 on on the 32-bit version and regsvr64 on the 64-bit version