Writer instructions | |
---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines |
Creating and initializing DB2 on Linux
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 MainView Middleware Monitor product.
- if you plan to use Transaction Management features of MainView Middleware 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. MainView Middleware Monitor services are 64-bit applications on Windows and Linux. BMC recommends that the database client version matches the database server version.
To create and initialize DB2 on Linux
- Install the database client software on any computer that needs access to the database.
- Run the scripts db2.create.sql and db2.init.sql 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 MVMM user has full authority granted to all the objects within it.
Use of aliases is supported, provided the MVMM database user has full authority over the base database objects through the aliases. - Add the following to the .profile file of the local user used to run services.
Adding these paths to your profile ensures that the services can locate and use required third-party software on your system.- Replace db_details with the path to any MVMM database specific shared objects that are needed to run database applications.
If necessary, work with your system or database administrator or your database documentation to determine the appropriate information to add to the path.
Typically, this task involves sourcing the db2profile. If you do not plan to use a dedicated user account to run services, follow your company's policies for setting local environment variables to add this information.64-bit DB2
export/add to .profile filei
Linuxii
LD_LIBRARY_PATH=db_details:$LD_LIBRARY_PATH
This allows the services to connect to a 64-bit DB2 database using the 64-bit client libraries (libdb2.so, etc.).
- The colon is a separator character and must appear between each path.
- The LD_LIBRARY_PATH must be set on all Linux systems with the MVMM Application Service.
- 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
Run scripts to create and initialize the database.