Required roles and permissions for installation

The MainView Middleware Monitor (MVMM ) installation requires that user accounts be set up on the database, services, and agent servers. These user credentials are used throughout the installation process and should be created before you start the installation itself.

Note that agent server user accounts need not be set up until you are ready to distribute and install the agent and extensions. 

• • Required permissions on the MVMM  database
  • Changes to apply to the MVMM database
  • Database user accounts

Required permissions on the MVMM  database

MVMM  requires the following permissions to be granted to the MVMM  database:

• Db2 LUW
• Oracle
• MS SQL

Db2 LUW

• SYSMAINT instance level authority to allow:
  • SELECT ON sysibmadm.bp_hitratio
  • SELECT ON sysibmadm.applications
  • SELECT ON sysibmadm.dbcfg
  • SELECT ON syscat.tables
  • REORG
  • RUNSTATS
• Authority to execute (on all tables within the MVMM  schema)
  • TRUNCATE TABLE IMMEDIATE
  • ALTER TABLE

ALTER TABLE authority is only required in MODE3 high resolution to low resolution data compression. For more detail on MODE3 compression see [History_Service].

• In addition, functions and procedures for reporting are created in the schema by the create script which must be executable by the MVMM  database user.
• If history table partitioning is required, authority to manage partitions is necessary:
  • ALTER TABLE ATTACH PARTITION
  • ALTER TABLE ADD PARTITON
  • ALTER TABLE DETACH PARTITION
  • SET INTEGRITY
  • DROP TABLE

Oracle

• Role 'select_catalog_role'
• SELECT ANY DICTIONARY

MS SQL

• VIEW SERVER STATE
• VIEW DATABASE STATE

Consult your DBA to grant these authorities. Contact BMC Support for a Db2 authority verification script if you require authority verification before installing the product.

Changes to apply to the MVMM database

The following changes need to be made to the MVMM  database. This applies to Db2 for LUW users only. The requirements are:

• Both system and user temporary tablespaces with a page size of 16K or greater must exist. This requires buffer pools of the same page size to support the tablespaces.
  
  • Command examples:
    • CREATE BUFFERPOOL QPTEMP32BP PAGESIZE 32K;
      
    • CREATE SYSTEM TEMPORARY TABLESPACE QPTEMP32 PAGESIZE 32K BUFFERPOOL QPTEMP32BP;
      
    • ALTER BUFFERPOOL QPTEMP32BP IMMEDIATE SIZE 1000;
      
    • CREATE BUFFERPOOL B2 PAGESIZE 32K;
      
    • CREATE USER TEMPORARY TABLESPACE UT PAGESIZE 32K MANAGED BY SYSTEM USING ('DB2_USER_TEMP') BUFFERPOOL B2;
      
    • ALTER  BUFFERPOOL B2 IMMEDIATE SIZE 1000;
      
• The Database configuration parameter "currently committed" (cur_commit) must be set to DISABLED/OFF.
  • Command example: db2 update db cfg for <db_alias> using cur_commit off immediate
  • The status of curr_commit can be known by issuing a "db2 get db cfg" command when connected to the database.

Consult your DBA to ensure these requirements are met; contact BMC Support with any concerns.

Database user accounts