In this release, Oracle JDBC
implements the JDBC 4.0 specification (but SQLXML) on top of Java SE 6
(i.e., JDK 1.6). The drivers may be used with Java SE 5 (i.e., JDK 1.5)
but will not have access to JDBC 4.0 capabilities. Other enhancements
include security, perfomance, manageability, etc. To learn more, read
the Java
Developer's Perspective on Oracle Database 11g
white paper.
Non Intrusive JDBC Tracing
Run java -jar jnettrace.jar <server name> <server port> <local listening port> eg: java -jar jnettrace.jar stade08 9221 8090 then modify the Jdbc program (i.e., URL) to use the same port and host name as above. This will create a client_<hex number>.trc in the local directory which is the client side sqlnet trace.
The initial motivation for
desupporting SQLJ was its low adoption by the J2EE commnity however, we
found out that it has been largely adopted by database developers.
Following numerous complaints, and listening to his customers, Oracle
has reverted the SQLJ Desupport decision; we have cancelled the
Metalink Desupport Notice. Starting with Oracle Database 10g
10.1.0.4 patch set release, the SQLJ translator has been re-enabled.
Customers have also full access to SQLJ
functionalities using -sqlj option of the JPublisher utility
(releace 10g and onwards).
Bookmark
