下表列出了各版本jdbc驱动与Oracle Sever的兼容关系:
For the correct information always check the JDBC Developer’s Guide and Reference for the JDBC version you are using. In the JDBC Developers Guide and Reference 11g Release 1 (11.1), it is stated:
Backward Compatibility
The JDBC drivers are certified to work with the currently supported versions of Oracle
Database. For example, the JDBC Thin drivers in Oracle Database 11g Release 1 (11.1)
are certified to work with the 10.2.x, 10.1.x, 9.2.x, and 9.0.1.x Oracle Database releases.
However, they are not certified to work with older, unsupported database releases,
such as 8.0.x and 7.x.Forward Compatibility
Existing and supported JDBC drivers are certified to work with Oracle Database 11g
Release 1 (11.1).
Although the main features will work it can happen that new features of a database version
cannot be used by older drivers. Therefore, it is recommended to use at least the same version
for the JDBC Driver as the version of the database
Here is a table giving which JDBC drivers can access which Oracle database :
| JDBC drivers | Oracle database |
| 11.2.0 | 11.2.0 11.1.0 10.2.0 10.1.0 9.2.0 |
| 11.1.0 | 11.2.0 11.1.0 10.2.0 10.1.0 9.2.0 |
| 10.2.0 | 11.2.0 11.1.0 10.2.0 10.1.0 9.2.0 |
| 10.1 | 11.2.0 11.1.0 10.2.0 10.1.0 9.2.0 |
| 9.2.0 | 11.2.0 11.1.0 10.2.0 10.1.0 9.2.0 |
* Database versions desupported.
转帖请注明源地址: http://www.youyus.com
* #1 – See Note 207319.1
* #2 – An ORA-3134 error is incorrectly reported if a 10g client tries to connect to an 8.1.7.3 or lower server. See Note 3437884.8 .
* #3 – An ORA-3134 error is correctly reported when attempting to connect to this version.
* #4 – There are problems connecting from a 10g client to 8i/9i where one is EBCDIC based. See Note 3564573.8
* #5 – For connections between 10.2 (or higher) and 9.2 the 9.2 end MUST be at 9.2.0.4 or higher. Connections between 10.2 (or higher) and 9.2.0.1, 9.2.0.2 or 9.2.0.3 are not supported.
* #6 – For connections between 11.1 (or higher) and 10.1 / 10.2 the 10g end MUST be at 10.1.0.5 / 10.2.0.2 (or higher) respectively in order to use PLSQL between those versions. See Note 4511371.8 for more details.
General Notes:
1. For database links between different Oracle versions connections must be supported in BOTH directions in the matrix above.
eg: As 9.2 -> 7.3.4 is not supported then database links between these version are not supported in either direction.
If you need to use a database link between an unsupported combination it may be possible to use an intermediate database.
eg: 10.2 -> 8.1.7 -> 8.0.6
2. Unsupported combinations may appear to work but can encounter errors for particular operations. The fact that they appear to work should not be relied upon – issues on unsupported combinations will not be investigated.
3. Since new database servers are compatible with a limited set of older OCI clients, it may not be necessary to upgrade the client software when upgrading the database. However, some new features may not work without upgrading the client software. So, for example, an Oracle 7.3.4 client is able to connect to an Oracle8i database, but is not able to take advantage of newer features such as Transparent Application Failover (introduced in v8).
4. Oracle Applications , or other Oracle products, may have supported configurations not listed in the matrix above.
5. The matrix above also applies between different platforms and between 32/64 bit releases of Oracle client / server except where any Oracle platform desupport notice indicates otherwise .
6. Unix BEQUEATH (BEQ) connections are NOT supported between different releases. eg: Client 9.2.0 is not supported to make an Oracle Net connection to a 10.1.0 server using the BEQ protocol adapter regardless of the interoperability support listed above. See Note 364252.1 for more details.
© 2009, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.
相关文章 | Related posts:
- SQL*Net PERFORMANCE TUNING UTILIZING UNDERLYING NETWORK PROTOCOL
- Troubleshooting JVM Performance Problems
- Automatic PGA Memory Management
- TECH: Database Block Checking Features
- Extracting Data from a Corrupt Table using DBMS_REPAIR or Event 10231
- RMAN 11G : Data Recovery Advisor – RMAN command line example
- gc lost blocks diagnostics
- Script to Collect RAC Diagnostic Information (racdiag.sql)
- 11g: Scheduler Maintenance Tasks or Autotasks
- How to Perform a Health Check on the Database [ID 122669.1]




最新评论