Starting from Oracle Database 12c Release 2 (12.2.0.1), you can use the SET CONTAINER statement in the following way, if you want to switch amongst pluggable databases, while continuing to use user services with full service functionality:

ALTER SESSION SET CONTAINER=<container name> SERVICE=<service name>;

JDBC Support for Binding PL/SQL BOOLEAN type

Starting from Oracle Database 12c Release 2 (12.2.0.1), Oracle JDBC drivers support binding PL/SQL BOOLEAN type, which is a true BOOLEAN type. PLSQL_BOOLEAN binds BOOLEAN type for input or output parameters when executing a PL/SQL function or procedure. With this feature, now JDBC supports the ability to bind PLSQL_BOOLEAN type into any PL/SQL block from Java.

Most of the variants of the defineColumnType method are deprecated. The supported variants are for:

LOB to LONG conversions

Configure the LOB prefetch size

See the JDBC Javadoc for more information.

CONNECTION_PROPERTY_STREAM_CHUNK_SIZE property

See the JDBC Javadoc for more information.

Oracle Update Batching

Oracle update batching was deprecated in Oracle Database 12c Release 1 (12.1). Starting in Oracle Database 12c Release 2 (12.2), Oracle update batching is a no operation code (no-op). This means that if you implement Oracle update batching in your application, using the Oracle Database 12c Release 2 (12.2) JDBC driver, then the specified batch size is not set and results in a batch size of 1. With this batch setting, your application processes one row at a time. Oracle strongly recommends that you use the standard JDBC batching if you are using the Oracle Database 12c Release 2 (12.2) JDBC driver.

Desupported Features

All Oracle JPublisher features are desupported and unavailable in Oracle Database 12c Release 2 (12.2.0.1). Oracle recommends that you use the alternatives listed here:

To continue to use Web service callouts, Oracle recommends that you use the Oracle JVM Web Services Callout utility, which is a replacement for the Web Services Callout utility.

To replace other JPublisher automation capabilities, including mapping user-defined SQL types or SQL types, wrapping PL/SQL packages and similar capabilities, Oracle recommends that developers use explicit steps, such as precompiling code with SQLJ precompiler, building Java STRUCT classes, or using other prestructured options.

See Also:

My Oracle Support Note 1937939.1 for more information about JDeveloper deprecation and desupport: