All geek questions in one place

10.2 to 11.2 g and Microsoft ODBC problems for Oracle

My team is trying to switch from ORACLE 10g to 11g. These are our system specifications:

Our current production server:

ORACLE 10.2g ORACLE Application Express(3.0) Apache Red Hat 64 bit

Our new server (not yet released):

 ORACLE 11.2g ORACLE Application Express (4.1.1) ORACLE HTTP Server Red Hat 64 bit

We were able to install 11g, install APEX 4.1 and apply a recent set of patches. The only bit that delays us with our migration is that our business users have access to Crystal Reports XI, MS Access / Excel 2003, which they use to connect to our database. A typical user has the operating system Windows XP SP 3 (32 bit). At the moment, we are using the Microsoft ODBC driver for Oracle (version 2.575.1132.00) to connect to our 10-gram database and did not have any problems. However, when we try to connect to 11g, we continue to receive ORA-03113: end of file on communication channel errors. In ORACLE SQL Developer, we can connect to our 11g instance using a "basic" connection. I also used TNS records and it works well.

I think business users got the Microsoft ODBC driver for Oracle by installing ORACLE Discover 3.1.3.6, which is used for another Oracle database. They also have Oracle Client 7.3.3, which I can see Oracle73 (2.00.03.01) mentioned in the ODBM data source admin window.

We tried to googling, and after various tests, we came to the conclusion that this is an ODBC driver problem. As far as we know, ORACLE SQL Developer uses a different JAVA driver to connect, so it does not use the Microsoft version.

Can someone confirm that our understanding is correct in that there are compatibility issues with the Microsoft ODBC driver for Oracle (version 2.575.1132.00) and 11.2g? If so, what would you recommend a compatible driver for use with Crystal and Access / excel for data extraction?

I think business users got the Microsoft ODBC driver for Oracle by installing ORACLE Discover 3.1.3.6, which is used for another Oracle database. They also have Oracle Client 7.3.3, which I can see Oracle73 (2.00.03.01) mentioned in the ODBM data source admin window.

+4
source share
1 answer

The Microsoft ODBC driver for Oracle is written using the ancient version of the OCI (Oracle Call Interface) API, which was deprecated when Oracle 8 was released (this was over a decade and 11 major releases ago). Microsoft decided to abandon this driver, and not port it to the new version of the OCI API. Oracle 7 clients can connect to Oracle 10.2 databases, but Oracle does not support connections between Oracle 7 clients and Oracle 11.2 databases.

You will need to update the version of the Oracle client installed on the machines of business users, and you will want to use the latest version of the Oracle ODBC driver suitable for this version of the Oracle client. Assuming you are installing the Oracle 11.2 client version (the only reason not to upgrade all the way to client 11.2 would be if users still needed to connect to older databases that do not support connections from client 11.2), you'd want Use the latest Oracle ODBC driver from 11.2.0.x. Installing an Oracle client should also have the ability to install the Oracle ODBC driver version — this should also be sufficient.

+3
source

Source: https://habr.com/ru/post/1399254/

More articles:


All Articles