Deprecated functionality in Db2 11.5
Functionality gets marked as deprecated when a specific function or feature is supported in the current release but might be removed in a future release. In some cases, it might be advisable to plan to discontinue the use of deprecated functionality.
For example, a registry variable might be deprecated in this release because the behavior that is triggered by the registry variable has been enabled by default in this release. The obsolete registry variable will be removed in a future release.
Review the details for each deprecation and plan how to manage future changes. Review also Discontinued functionality in Db2 11.5 that might affect your databases and existing applications.
Db2 functionality
The following Db2 functionality is deprecated in version 11.5:| Deprecated capability | Details | Resolution |
|---|---|---|
| TLS 1.0 and 1.1 | The use of versions 1.0 and 1.1 of the Transport Layer Security (TLS) protocol has been deprecated. | TLS is the Secure Socket Layer (SSL) protocol used by Db2 to provide secure, encrypted transmission of data. We recommend using TLS version 1.2. |
| Infiniband network in a GDPC on AIX | Support for using the Infiniband network as a private network between members and CF in a geographically dispersed pureScale cluster (GDPC) on AIX has been deprecated. It will be discontinued in a future release. | New instances should use the RoCE network with a four switch configuration. It functions as a private network between members and CFs that provides full redundancy at an adapter and switch level. |
| Unicode Collation Algorithm of the Unicode Standard version 5.0.0 have been deprecated | When you create Unicode databases, you can specify locale-sensitive collations based on the Unicode Collation Algorithm (UCA) with the COLLATE USING parameter in the CREATE DATABASE command. These collations provide similar functionality and better performance | For new Unicode databases, create them using any of the supported locale-sensitive UCA-based collations. For more information, see Unicode Collation Algorithm based collations. For existing Unicode databases, you can convert to a supported locale-sensitive UCA-based collation by recreating your databases following a similar procedure as Converting non-Unicode databases to Unicode. |
APIs, Commands, command parameters, monitor elements, and statements
The following APIs, Commands, command parameters, monitor elements, and statements are deprecated
in version 11.5:
| Deprecated capability | Details | Resolution |
|---|---|---|
| db2ReadLogNoConn, db2ReadLogNoConnInit, db2ReadLogNoConnTerm | The db2ReadLogNoConn, db2ReadLogNoConnInit,db2ReadLogNoConnTerm APIs have been deprecated. | For log reading capability, see db2ReadLog API. |
| The DATA_ENCRYPT authentication type | The DATA_ENCRYPT authentication type has been deprecated. | DATA_ENCRYPT is an authentication option that also causes some data to be encrypted in transmission. To continue to encrypt data during transmission, we recommend that you use the Db2 database system support of Secure Sockets Layer (SSL) |
| The 3DES encryption option | The 3DES native encryption option has been deprecated. | The Triple Data Encryption Standard (3DES) is an algorithm used by Db2 for native encryption. We recommend that users now use the Advanced Encryption Standard (AES) native encryption option. |
| DB2INSTDEF | Support for the DB2INSTDEF registry variable on UNIX has been deprecated. | The environment variable DB2INSTANCE must always be set on UNIX platforms. |