Creating and initializing DB2 on Windows
Before you begin
- The database server software must be installed and configured.
- You must have created a database, database user, and schema for the exclusive use of the TrueSight Middleware and Transaction Monitor product.
- if you plan to use Transaction Management features of TrueSight Middleware and Transaction Monitor, use the largest data block/page size allowed by the DBMS, preferably 32K. Consult your DBMS vendor documentation on how to create a database or database objects with a larger page size.
- The Services server must be in close physical proximity to the database server with a network latency of less than 5ms between them (100 Mb LAN). BMC recommends a gigabit LAN.
- Database clients must be appropriate to the installation of the core components and to the database server. TrueSight Middleware and Transaction Monitor services are 64-bit applications on Windows and Linux (SLES, RHEL). BMC recommends that the database client version matches the database server version.
To create and initialize DB2 on Windows
- Install the database client software on the services server.
- Run db2.create.sql and db2.init.sql scripts from within a DB2 interactive session.
See Running-the-scripts-to-create-and-initialize-the-database.
db2 o -stf db2.create.sql -l db2.create.log
db2 o -stf db2.init.sql -l db2.init.log - Ensure that the schema for use by the TrueSight Middleware and Transaction Monitor user has full authority granted to all the objects within it.
Use of aliases is supported, provided the database user has full authority over the base database objects through the aliases. - When the scripts are complete, ensure that your entire database network is functioning and all of the clients can access and write to the server.
Where to go from here
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*