Migrating and Upgrading to IBM Data Server Driver Package

Upgrading to IBM Data Server Driver Package

1. Install a Db2 version 11.5 DSDRIVER copy.
   • If there is no existing DSDRIVER installed, then install the latest version of the DSDRIVER. The new DSDRIVER will be installed to a new copy.
   • If there is one existing copy of the DSDRIVER:
     • If there is an existing DSDRIVER and a copy name is not provided for the new install, the default behavior is to install the DSDRIVER on top of that copy and upgrade it to the current level.
     • If there is an existing DSDRIVER and a copy name is provided in the install command line or in the response file (for the silent install) the DSDRIVER will be installed to that copy, whether it is a new copy, or an existing DSDRIVER copy.
   • If there are 2 or more existing DSDRIVER copies:
     • If one of the existing DSDRIVER copies is set as the default Db2 client interface copy:
       • If no copy name is provided during install, the DSDRIVER will be installed on top of the default client interface copy.
       • If a copy name is provided during install, the DSDRIVER will be installed to that copy, whether it is an existing copy or a new one.
     • If none of the existing DSDRIVER copies is set as the default Db2 client interface copy:
       • If no copy name is provided during install, the DSDRIVER install will be stopped with message DBI20006E Installing the IBM Data Server Driver Package failed because the installer could not determine whether to install a new copy or to upgrade an existing copy because no copy name was specified.
       • If a copy name is provided during install the DSDRIVER will be installed to that copy, whether it is an existing copy or a new one.
   Note: The installer will handle the case where the release level of the existing copy is higher than the current.
2. If you want your applications to use the Db2 version 11.5 DSDRIVER copy through the default interface, set the Db2 version 11.5 DSDRIVER copy as the Db2 client interface default.

Migrating to IBM Data Server Driver Package from an instance based client

To migrate to IBM Data Server Driver Package from an instance based client, complete the following steps:

1. If you do not have an LDAP-enabled environment, skip this step. If you do have an LDAP-enabled environment and the LDAP server is used for storing database entries, refresh all the local database and node entries and add new entries from the LDAP server by issuing the following command:

   db2 refresh ldap immediate all

   Running this command ensures that any LDAP database information is now refreshed in the local catalog of the instance based client.

2. Create the DSDRIVER configuration file and populate it with the existing instance based client catalog information by issuing the following command:

   db2dsdcfgfill -i instance_name -o output_path

   where:

   • instance_name is the name of the database manager instance. To determine the name of the instance, run the db2ilist command. For more information, see db2ilist - List instances command.
   • output_path is the path where the configuration file is saved. Choose any path other than the path where the instance based client is installed. This file is used later when the IBM Data Server Driver Package is installed
   The db2dsdcfgfill command is found in one of the following paths:

   • On AIX, or Linux operating systems $HOME/sqllib/bin, where $HOME is the home directory of the instance owner.
   • On Windows operating systems DB2DIR/bin directory, where DB2DIR is the installation location of the Db2 copy.
   Starting with Db2 version 10.5 Fix Pack 5, information about the LDAP databases stored in the local catalog is also automatically populated to the db2dsdriver.cfg file when you run the db2dsdcfgfill command, as in the following example:

   <configuration>
   <dsncollection>
      <dsn alias="EC205" name="STLEC1" host="INEC005.vmec.svl.ibm.com" port="446"/>
      <dsn alias="EC206" name="STLEC1"  host="INEC006.vmec.svl.ibm.com" port="446" ldap=”1”/>
      <dsn alias="EC207" name="STLEC1"  host="INEC007.vmec.svl.ibm.com" port="446"/>
   </dsncollection>
      <databases>
      <database name="STLEC1" host="INEC005.vmec.svl.ibm.com" port="446"/>
      <database name="STLEC1" host="INEC006.vmec.svl.ibm.com" port="446"/>
      <database name="STLEC1" host="INEC007.vmec.svl.ibm.com" port="446"/>
      </databases>
   </configuration>

   Note: The dsn alias EC206 is an LDAP cataloged database on an instance based client. Therefore the entry in the example above contains ldap=”1”
3. Uninstall the Data Server client copy. For more information, see Uninstalling an IBM data server client.
4. Install a version 11.5 DSDRIVER copy. For more information, see IBM Data Server Drivers.
5. Copy the configuration file created in step 2 to the DSDRIVER configuration file location.

   To determine the DSDRIVER configuration file location, use the db2cli validate command.

   The DSDRIVER configuration file, db2dsdriver.cfg, is now created using the configuration file path you chose with the -o in the db2dsdcfgfill command from step 2 and is ready to connect.

6. Verify the connection to the LDAP directory by issuing the following command: db2cli validate -dsn dsn name -connect -user username -passwd password . For more information, see Validating IBM Data Server Driver Package.
7. If you have an LDAP-enabled environment, your db2dsdriver.cfg file contains an <ldapserver> section. To refresh the contents of the db2dsdriver.cfg file at any time, issue the following command: db2cli refreshldap.