After converting your environment to Db2
pureScale, you must
perform several post-conversion tasks to help ensure that your Db2 servers perform at
their optimum level.
Procedure
To help ensure that your Db2 servers perform at
their optimum level:
- If you set the diaglevel database
manager configuration parameter to 3 or higher as
part of the pre-conversion tasks for a Db2
pureScale environment,
reset this parameter to the value that was set before the conversion.
-
Adjust your database configuration settings to meet new requirements
in a Db2
pureScale environment.
-
Ensure that the libraries for your external routines remain in the location where they were
before the conversion.
- Start your database and all necessary database services.
- If you created local or global file or pipe event monitors in a prior
release and the directory or named pipe that you specified is not on a shared file system, drop and
re-create them indicating that the directory or named pipe is on a shared file system.
- To use the new high availability function in your global
event monitors and the default DB2DETAILDEADLOCK event monitor, drop
them and re-create them.
- Back up your databases.
- Verify that your environment conversion is successful by
connecting to the
databases and issuing a small query, as shown in the following example:
db2 connect to sample
Database Connection Information
Database server = DB2/AIX64 10.1.0
SQL authorization ID = TESTDB2
Local database alias = SAMPLE
db2 select * from syscat.dbauth