After upgrading your DB2 Connect™ servers, you should perform several post-upgrade tasks
to ensure that your DB2 Connect servers
perform as expected and run at their optimum level.
Perform the following post-upgrade tasks for DB2® servers that also apply to DB2 Connect servers:
- If you set the diaglevel database manager configuration
parameter to 4 as recommended in the pre-upgrade tasks for DB2 Connect servers, reset
this parameter to the value set before the upgrade.
- Manage changes in DB2 server behavior .
There are new registry variables, new configuration parameters, and
new default values for registry variables and configuration parameters
introduced in latest version or release of DB2 products that can impact the behavior of DB2 server. There are also changes
in physical design characteristics of databases and changes to security
that also have an impact.
- If you obtained customized code page conversion tables from the DB2 support service for previous
versions or releases, copy all of the files for those tables from
the DB2OLD/conv to DB2DIR/conv,
where DB2OLD is the location of your previous supported version of DB2 Connect copy and DB2DIR
is the location of your new DB2
Connect copy. You do not need to copy standard code page conversion
tables.
If you upgraded your existing, supported DB2 Connect copy on Windows operating systems, you can restore
the customized code page conversion tables that you backed up as part
of the pre-upgrade tasks for DB2
Connect servers to the DB2PATH\conv directory,
where DB2PATH is the location of your new DB2 Connect copy.
If you are connecting to a DB2 for z/OS® server
or a IBM® DB2 for IBM i server
where euro support is required, set the DB2CONNECT_ENABLE_EURO_CODEPAGE registry
variable to YES on all DB2 Connect clients and servers so that
the current application code page is mapped to the equivalent coded
character set ID (CCSID) that explicitly indicates support for the
euro sign.
- Optional: If you upgraded any databases in your DB2 Connect server and changed the log
space setting as recommended in the pre-upgrade tasks for DB2 Connect servers, adjust the log space size .
Ensure that the amount of log space that you allocate is adequate
for your DB2 Connect server.
- Optional: Back up your databases after
the upgrade is complete.
- Optional: If you have DB2
Connect federated databases, review configuring federated systems after
migration to determine
if you need to perform any tasks after you upgrade your federated
databases.
- Verify that your DB2
Connect server upgrade was successful. Test connections to all
your cataloged databases. The following example shows how to test
a connection from the Command Line Processor (CLP):
db2 CONNECT TO DATABASE sample user mickey using mouse
You
need to specify a user and password when connecting to a remote database.
Ensure all connections are successful.Also, test your applications
and tools to ensure that the DB2
Connect server is working as expected.
At this point, you should resume all of your maintenance
activities. You should also remove any previously supported versions
or releases of DB2 Connect copies
that you no longer need.