Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for Microsoft Windows > Preupgrade Tasks > Verifying Database Server Configuration >
DB2 Universal Database Server Configuration
This section provides guidelines for obtaining optimum performance from a DB2 Universal Database.
Before upgrading a DB2 database, verify that your development database server meets or exceeds the following OLTP parameters:
- You have at least 25 primary and 100 secondary logs of at least 32-MB log size.
- Locklist parameters are set to at least 5,000, and preferably 15,000.
- Maxlocks should be set to 20.
- DMS tablespace has at least 25% of free pages. If it does not, you must increase tablespace size by adding containers.
- The file system has sufficient space to allow your DMS tablespace to grow.
In addition, verify that the tablespaces are not near their capacity. This can be done by connecting to the database and issuing the following command:
db2 list tablespaces show detail
Upgrade Instance
After upgrading your RBDMS software (for DB2 UDB, follow the instructions provided by IBM), upgrade your DB2 UDB instance.
- Run the following command on the database server to upgrade to the current version of your RDBMS software:
Verifying DB2 Permissions on AIX and Solaris
If you are running DB2 UDB on the AIX or Solaris platform, perform the following steps before executing the Siebel database upgrade:
- Navigate to the instance home directory.
- Use the following command to verify that the directory
sqllib/function/routine/sqlproc
has write permission for the group:- To authorize group write permission, enter the following command:
Verifying Instance Owner Permissions on DB2 UDB for AIX and Solaris
If you are running DB2 UDB on the AIX or Solaris platforms, verify that the Siebel Database instance owner belongs to the primary group of the fenced user. If the instance owner is not part of this group, errors will occur during the Siebel Database upgrade.
Increasing the Number of ODBC Statement Handles
DB2 UDB can quickly run out of ODBC statement handles, depending on the number of business objects your enterprise uses. Because it is difficult to know how many business objects your users actually use, you should increase this number automatically each time you upgrade the DB2 UDB client, or when rebinding database utilities.
Siebel Systems recommends that you increase the number of CLI packages to six by rebinding the CLI packages, using the special DB2
CLIPKG
bind option.
- Navigate to the following subdirectory from a DB2 Command window:
- Connect to the DB2 UDB database.
- Enter the following command:
For more information about the DB2 bind command and the
CLIPKG
option, refer to IBM DB2 documentation.Upgrade-Specific Parameters
The default settings of the parameters in this section should be adjusted for upgrading to Release 7.5. The values recommended in the following pages are guidelines only, and your environment may require adjustments to these values.
After your upgrade has been completed, and prior to running Release 7.5 in a production environment, you must adjust the DB2 parameters described in this section to those values recommended in Siebel Server Installation Guide for the operating system you are using. Otherwise, your Siebel Database Server may not provide optimal performance.
See your IBM DB2 technical documentation for additional information on DB2 parameters.
DB2 Database Manager Configuration Parameters
You can set the database configuration parameters using the
update database manager configuration
command of the DB2 Command Line Processor or using the DB2 Control Center.NOTE: Refer to your IBM DB2 UDB documentation for more information on modifying the database configuration parameters.
Table 11 provides guidelines for setting DB2 Database Manager configuration parameters specifically for an optimal upgrade of your Siebel Database. Set these parameters for each DB2 instance. Use the configuration information below for the listed parameters. For parameters not listed in this table, accept the default settings.
Table 11. DB2 Database Manager Configuration Parameters db2set Parameters
Use the
db2set
command to set the parameters (for example,db2set DB2_RR_TO_RS = YES
) referenced in Table 12. (Under Windows, you would access this through the DB2 Command Window, accessible from the DB2 for Windows 2000 client.)NOTE: After changing any of these settings, perform a
db2stop/db2start
to implement the changes in your DB2 database.DB2 Database Configuration Parameters
The database configuration parameters can be set using the
update database configuration
command of the DB2 Command Line Processor or using the DB2 Control Center. See the IBM DB2 technical documentation for more information on modifying the database configuration parameters.Set the parameters in Table 13 for each database within an instance on which you run your Siebel eBusiness Applications. For other parameters of the same type, accept the default settings.
Table 13. DB2 Database Configuration Parameters Installing the Stored Procedures and User-Defined Functions
NOTE: If you are performing an upgrade from Release 7.x to Release 7.5, skip this procedure. You already completed this step during your upgrade to Release 7.x.
If you are upgrading from Release 6.x and your RDBMS is DB2 UDB, you must install the stored procedures and user-defined functions (UDFs) on the database server. To do this, you must first transfer them to the database server, and have installed the database server components. (For information on installing database server components, refer to the chapter on installing the Siebel Database Server for DB2 Universal Database in Siebel Server Installation Guide for the operating system you are using.)
If you use a different RDBMS platform, skip to Preparing Application Data for Upgrade.
The user-defined functions (UDFs) and stored procedures must be transferred to and installed on the database server to support the Siebel product. Any method that transfers the necessary files to the correct location on the database server is acceptable.
NOTE: Compiling stored procedures in DB2 creates .dll files. You must copy these files to the database server machine's
sqllib\function
directory.To copy and install the stored procedure code, follow the procedure appropriate to your operating system. You first must delete the old store procedures. Then you must install the Siebel stored procedure library on the DB2 database server host.
Before you perform this procedure, determine whether your DB2 database software requires upgrading. You might also be required to apply a DB2 fix pack. See Siebel System Requirements and Supported Platforms for more information about required versions.
To delete the old stored procedures
To copy and install the stored procedure code
- Install the Siebel stored procedure library on the DB2 database server host.
- Log onto the Siebel source installation machine, and navigate to the source installation subdirectory that contains the Siebel Database installation objects.
The directory that contains the file to install (
siebproc
) is
DBSRVR_ROOT
\DB2UDB\SIEBPROC\
DBSRVR_OS
DBSRVR_OS
= the operating system your database server runs on; for example,aix
.
- Put the
siebproc
file (on Windows this is calledsiebproc.dll)
into theFUNCTION
subdirectory within the DB2 UDB instance directory (where DB2 UDB is installed) on the Siebel Database Server.For example, on Windows, this location might be
C:\SQLLIB\FUNCTION.
Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for Microsoft Windows Published: 20 October 2003 |