Discontinued functionality in Db2 12.1

Discontinued functionality has been removed from Db2 in version 12.1 and is no longer available. Users need to make changes if they have been using that functionality in previous releases.

Attention: The Db2 12.1 release is currently available for the following Db2 products:
The following Db2 functionality is discontinued in version 12.1:
Table 1. Summary of discontinued functionality in Db2 12.1
Discontinued capability Details Resolution
Support for db2top on newer SUSE Linux Enterprise Server (SLES) releases. With the release of Db2 12.1, the deprecated db2top monitoring utility is not supported on SUSE Linux Enterprise Server (SLES) 15.6 and later. Use the dmctop utility.
Running a LOAD ‘CLIENT’ operation on a remote client host, with a remote storage alias specified. When run against a remote client host rather than the database server host, the ability to run a LOAD operation that has the CLIENT option and a remote storage object specified, is discontinued. Consider running the LOAD operation with a remote storage alias directly on the database server host, or by using the LOAD command with the ADMIN_CMD procedure.
Running an INGEST operation with a remote storage alias specified. An INGEST operation with a remote storage alias specified is discontinued. When data is to be read from remote storage, consider accessing the data from an EXTERNAL TABLE, or by using the LOAD command to populate an existing table.
db2pd -ha option. The high availability (-ha) option of the db2pd utility is discontinued on Linux platforms. Use the Db2 cluster manager (db2cm) -list or -status options instead.
db2haicu utility on Linux. The db2haicu utility is discontinued on Linux. Going forward, Linux users should use db2cm instead of db2haicu.
TSA as the integrated cluster manager on Linux for Db2 TSA for Linux was deprecated in Db2 11.5.8 and is now discontinued. TSA is being replaced by Pacemaker as the integrated cluster manager for Db2 on Linux. Going forward, Linux users setting up an integrated high availability (HA) environment for Db2, whether it be Mutual Failover, HADR, DPF or pureScale need to use Pacemaker as the integrated cluster manager for HA.
db2pdcfg -flushbp The -flushbp parameter of the db2pdcfg command is discontinued. Use the FLUSH BUFFERPOOLS command to achieve equivalent functionality. The FLUSH BUFFERPOOLS statement writes dirty pages from all local buffer pools for a particular database synchronously to disk.
db2tapemgr command. The db2tapemgr command for managing the storage and retrieval of Db2 log files to and from tape storage is discontinued. Db2 no longer supports moving log files to and from tape storage. Use other supported storage methods and manage log archiving through the logarchmeth1 and logarchmeth2 configuration parameters. You can also use an alternative storage vendor.
db2mtrk - Memory tracker command. The db2mtrk command, which reported on memory status for instances, databases, agents, and applications is discontinued. Use the MON_GET_MEMORY_POOL table function, the MON_GET_MEMORY_SET table function, or the db2pd command with the -mempools or -memsets options instead.
Stepwise redistribution routines. The following stepwise redistribution routines are now discontinued:
  • The ANALYZE_LOG_SPACE procedure
  • The GENERATE_DISTFILE procedure
  • The GET_SWRD_SETTINGS procedure
  • The SET_SWRD_SETTINGS procedure
  • The STEPWISE_REDISTRIBUTE_DBPG procedure
 Use the REDISTRIBUTE DATABASE PARTITION GROUP command to achieve equivalent functionality.
TLS1.0/1.1 for client-server communication. TLS1.0/1.1 for client-server communication is now discontinued. TLSv1 is an invalid value for the SSL_VERSIONS parameter. By default, TLS 1.2 and TLS 1.3 are enabled. This change means that down-level clients are not able to connect to V12 servers using TLS1.0/1.1. Use TLS1.2 or TLS 1.3 by running db2 update dbm cfg using SSL_VERSIONS TLSV12, db2 update dbm cfg using SSL_VERSIONS TLSV13, or db2 update dbm cfg using SSL_VERSIONS NULL.
TLS 1.0/1.1 for LDAP authentication plug-ins. TLS 1.0 and 1.1 for communication between the LDAP authentication plug-ins and an LDAP server is discontinued. By default, TLS 1.2 and 1.3 are enabled. Ensure TLS 1.2 and/or TLS 1.3 are enabled in the LDAP server. No changes to the IBMLDAPSecurity.ini configuration file are needed. Instances with SECURITY_PROTOCOL set to ALL will use TLS 1.2 and 1.3.
SHA1 and 3DES cipher suites for TLS.

The following cipher suites are now discontinued for the SSL_CIPHERSPECS DBM configuration parameter:

  • TLS_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 Use one of the other more secure cipher suites: db2 update dbm cfg using SSL_CIPHERSPECS <comma separated values>, or set the parameter to NULL: db2 update dbm cfg using SSL_CIPHERSPECS NULL.
SHA1 certificates for TLS. The usage of certificates with a SHA1 signature algorithm with all versions of TLS is now discontinued. This includes client-server communications, communications between HADR primary and standby instances, and communication between an LDAP authentication plug-in and LDAP server.
Note: Communication to a KMIP key manager is unaffected by this change, as it already requires certificates with a SHA256 or better signature algorithm.
 Regenerate certificates using a SHA1 signature algorithm and choose a SHA256, SHA384, or SHA512 signature algorithm.
3DES for Native Encryption.

The following operations in native encryption are being discontinued when using the 3DES cipher:

  • Creating an encrypted database using the 3DES cipher: db2 "CREATE DATABASE TESTDB ENCRYPT CIPHER 3DES".
  • Restoring into a new encrypted database using the 3DES cipher: db2 "RESTORE DATABASE TESTDB ENCRYPT CIPHER 3DES".
  • Creating an encrypted backup by specifying the Cipher=3DES option in the backup command: 
    db2 "BACKUP DATABASE TESTDB ENCRYPT ENCROPTS
    'Cipher=3DES'"
  • Creating an encrypted backup when ENCRLIB and ENCROPTS DB config parameters are set. In this case, ENCROPTS option cannot be specified in the backup command and this information is instead acquired from the DB config parameters: db2 "BACKUP DATABASE TESTDB".
Note:
  • Existing 3DES encrypted databases can still be used as before.
  • Existing 3DES encrypted databases can still be backed up using the AES cipher.
  • Existing 3DES encrypted backups can still be restored with the AES cipher or as unencrypted.
 Use AES instead, which is a more secure algorithm.
DB2_SERVER_ENCALG registry variabl.e DB2_SERVER_ENCALG registry variable has been removed. This is an old registry variable that used to specify the encryption algorithm when using SERVER_ENCRYPT authentication type. This registry variable has been replaced by ALTERNATE_AUTH_ENC DBM CFG parameter in V9.7.
Change password plug-ins for Linux. IBMOSchgpwdclient and IBMOSchgpwdserver plug-ins are discontinued and are no longer shipped with Db2. Consequently, setting them is no longer possible. The existing IBMOSauthserver and IBMOSauthclient plug-ins provide the same functionality and they should be used instead.
FED_NOAUTH database management configuration parameter. The parameter can no longer be set to yes. As a result, bypassing federated authentication at the instance is no longer possible as it is insecure. There is no alternative.
Infiniband adapters for Db2 pureScale® connections. Db2 pureScale support for Infiniband adapters is discontinued. Migrate to RoCE adapters before upgrading to Db2 12.1.
db2cluster -cm -list -configuration option. The db2cluster -cm -list -configuration option is discontinued. Run db2cluster -cm -list <options> to retrieve the appropriate cluster information.
RoCE adapters without IP support on AIX. Db2 pureScale support for RoCE adapters that do not have IP support on AIX systems is discontinued. Migrate to a supported RoCE adapter before upgrading to Db2 12.1.
DATA_ENCRYPT authentication type. DATA_ENCRYPT and DATA_ENCRYPT_CMP authentication types provide the ability to encrypt both user credentials and user data when sent between the client and the server. DATA_ENCRYPT is removed from the server, and Db2 Connect. It is not removed from the client so connections to down-level server continue to work. These authentication types are being discontinued since they use DES encryption algorithm which is no longer considered secure. Using TLS instead is recommended. For more information, see Encryption of data in transit.
LOAD RESTART command parameter. The RESTART parameter of the LOAD command is discontinued. Restart a LOAD operation by running a LOAD TERMINATE statement, followed by the original LOAD statement.
Health Monitor. Health Monitor functionality is now discontinued, with the exception of the HEALTH_MON database manager configuration parameter, the GET HEALTH SNAPSHOT command and the HADR health indicators (db.hadr_op_status and db.hadr_delay), which remain deprecated. The IBM Data Studio or IBM Db2 Data Management Console products can be used to monitor the health of Db2 databases.
End of support for Microsoft .NET Framework versions. Support for versions 2.0, 3.0, and 3.5 of the .NET Framework is now discontinued by the IBM® Data Server Provider for .NET. NA
End of support for Microsoft .NET CLR routines. Support for .Net CLR routines is now discontinued. If you have a dependency on a .NET CLR routine, rewrite the routine logic in a supported language and recreate the routine.
Client Authentication. CLIENT authentication is now discontinued. You cannot set AUTHENTICATION or SRVCON_AUTH DBM CFG to CLIENT. Use one of the other secure authentication types for server. To continue using CLIENT authentication on the server, you must set the DB2AUTH registry variable to ENABLE_CLIENT_AUTHN.
DB2 administration server (DAS). The Db2 administration server (DAS) and all associated functionality is discontinued. The IBM Data Studio or IBM Db2 Data Management Console products can be used to administer Db2 databases.
The governor utility. The governor utility is now discontinued. Use the Db2 workload manager capability. For more information, see Migrating from Db2 Governor to Db2 workload manager.
End of support for applications that use Visual Studio 2008. The use of IBM data server products with Microsoft Visual Studio 2008 is discontinued. If you have a dependency on Visual Studio, rewrite the routine logic for a supported Visual Studio version and recreate the routine.
Db2 supports the following Visual Studio versions:
  • Versions deprecated in Db2 12.1:
    • Visual Studio 2015
    • Visual Studio 2013
    • Visual Studio 2012
    • Visual Studio 2010
  • Versions not deprecated in Db2 12.1:
    • Visual Studio 2022
    • Visual Studio 2019
    • Visual Studio 2017
Deprecated table functions now discontinued. The following Snapshot monitor table functions are now discontinued:
  • SNAP_GET_APPL_INFO_V95
  • SNAP_GET_APPL_V95
  • SNAP_GET_BP_V95
  • SNAP_GET_CONTAINER_V91
  • SNAP_GET_DBM_V95
  • SNAP_GET_DB_V97
  • SNAP_GET_DETAILLOG_V91
  • SNAP_GET_DYN_SQL_V95
  • SNAP_GET_STORAGE_PATHS_V97
  • SNAP_GET_TAB_V91
  • SNAP_GET_TBSP_PART_V97
  • SNAP_GET_TBSP_V91
Also, the following workload management table functions are now discontinued:
  • WLM_GET_SERVICE_CLASS_AGENTS_V97
  • WLM_GET_SERVICE_CLASS_WORKLOAD_OCCURRENCES_V97
  • WLM_GET_SERVICE_SUBCLASS_STATS_V97
  • WLM_GET_WORKLOAD_OCCURRENCE_ACTIVITIES_V97
  • WLM_GET_WORKLOAD_STATS_V97
  • WLM_GET_ACTIVITY_DETAILS
 Use an alternate procedure or function. For more information see Monitor procedures and functions and Workload management routines.