This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Preparing your DB2 database before you upgrade

This section describes the steps you should perform with your DB2 database before you install BMC Remedy AR System or any application in the BMC Remedy IT Service Management Suite.

Some forms have entries that exceed the default BMC Remedy AR System size limit for each record. The following steps help optimize the way DB2 determines which forms it places in larger containers. Perform these steps to provide a balanced performance standard across all the forms.

Before you begin

  • If the BMC Remedy AR System server and the IBM DB2 database are running on the same environment on a single server (not a remote DB2 database), and you are installing BMC Remedy AR System on a DB2 database, change the Local Security Policy settings before you install the BMC Remedy AR System server. Go to Start > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment > Act as part of the operating policy and add the user (administrator) who is running the BMC Remedy AR System process. Then, select Local Policies > User Rights Assignment > Log on as a service policy, and add the user (administrator) who is running the BMC Remedy AR System process.
  • Verify that the following DB2 values have been set during the installation of BMC Atrium CMDB:
    • APP_CTL_HEAP_SZ 40480 (DB2 version 9.4 or earlier)
    • APPL_MEMORY AUTOMATIC (DB2 version 9.5 or later)
    • INSTANCE_MEMORY AUTOMATIC (DB2 version 9.5 or later)
    • UTIL_HEAP_SZ 95000
    • STMTHEAP 60000
    • LOGFILSIZ 4000
  • To perform the following steps, make sure you are logged in as the DB2 instance owner. For example:
    su - db2 instance
  • If the database is not configured to extend automatically, set the BMC Remedy AR System data file size to at least 2 GB for one BMC Remedy application, or to at least 8 GB if you are also installing all BMC Remedy ITSM applications.

Note

As of version 8.1 of the BMC Remedy IT Service Management Suite, your DB2 database server must be at version 9.7 or later to upgrade the BMC Remedy ITSM Suite. If you are unable to upgrade your DB2 database server, refer to the instructions provided in the BMC Remedy ITSM documentation.

To prepare your DB2 database

  1. Install the DB2 database server.
    You can install the DB2 database server on the same computer where the AR System server is installed or on a remote server that is networked to the computer where you plan to install BMC Remedy AR System.
  2. Install DB2 clients.
    For remote installations, install the DB2 clients on the same computer as the AR System server.
  3. (Solaris only) Install the DB2 libdb2.so library.
    The AR System server is dynamically linked to the DB2 library on Solaris. If this library was not installed with the DB2 client, install the library on the same computer where you plan to install the AR System server.

    Note

    For information on the supported DB2 client library versions, see the compatibility matrix (Checking system requirements and supported configurations).

  4. Create and name a DB2 instance.
    • For local database servers, create a DB2 instance on the local computer.
    • For remote database servers, create a DB2 instance on the remote computer.

      Note

      For naming restrictions, check your database vendor documentation.

  5. Set the port configuration:
    db2 update dbm cfg using SVCENAME 60007
  6. Restart the DB2 instance:
    db2stop
    db2start
  7. Verify the port configuration:
    db2 get dbm cfg | grep SVCENAME
    Be sure to use the correct DB2 port during the installation.
  8. Make sure the TCP/IP Protocol for the database is enabled, and set a TCP/IP port for the database instance.
  9. (UNIX only) Verify or set the LANG environment variable.
  10. Make sure that your database can accept network communication with the parameters entered in the installation. (For the list of parameters, see your planning spreadsheet.)
    The network communication will use ODBC and be able to recognize your ODBC data source.
  11. If you are using DB2 9.7, grant permissions to the DBADM role:
    grant DBADM, BINDADD ,CONNECT, CREATETAB, CREATE_EXTERNAL_ROUTINE,
    CREATE_NOT_FENCED_ROUTINE, IMPLICIT_SCHEMA, QUIESCE_CONNECT, LOAD
    on database to user <userName>
    Make sure the DBADM user exists as a local Windows account, and make sure that the passwords of the local Windows account and the DB2 account are identical.
  12. Make sure that the database's local catalog name matches the database's name on the database server.
    If the names do not match, the installer will not display the Upgrade/Overwrite dialog box, and a warning will appear: Warning! You have entered an existing database login.
  13. For a Unicode DB2 installation, make sure that the DB2CODEPAGE variable is set to 1208.
    On Microsoft Windows, for example, enter the following command from the DB2 command window:
    db2set DB2CODEPAGE=1208
    

    Note

    The DB2CODEPAGE setting is part of the database client libraries. Make sure that this setting is correct on the computer where the BMC Remedy AR System is running, which might be different from the computer where the database is located.

    For more information about the syntax and usage of DB2 commands, see the IBM DB2 documentation.

For local installations

  1. Create an operating system user account (for example, bmcuser1) on the same computer where you installed the DB2 database and where you will install the AR System server.

    Note

    The new operating system user account must have the Log on as Service rights.

  2. For BMC Remedy AR System root installations or BMC Remedy AR System installations performed by a user who is not a database instance administrator, make the user a member of the following groups, which are created during the DB2 database installation:
    db2iadm1
    db2fadm1
    db2asgrp
  3. Give the user privileges to the following folders:
    /etc/arsystem (Write permission)
    /tmp (Write permission)
    /opt/bmc/ (Write permission)
    User-defined installation directory (Write permission)
    /usr/sbin/slibclean (Execute permission on AIX platforms)
    /tmp or /var/tmp or /usr/tmp (Write permission, depending on the operating system)
    If the IATEMPDIR variable is set during the installation, make sure that the user has permission to the appropriate file.

    Note

    Due to installer framework changes in 8.1.02, this requirement is not valid from 8.1.02 and onwards.

    1. If you are migrating the DB2 database or instance to a different computer or environment, provide privileges for the BMC Remedy AR System database user to the tablespace.
      For example:
      GRANT USE OF TABLESPACE <Tablespace> TO USER
      <DB2DatabaseUserLoginProvidedDuringARSystemInstallation>
      The installer provides tablespace privileges during installation and expects that the Syscat.tbspaceauth table has specific privileges for the grantee of the BMC Remedy AR System database user.
    2. Log in as the user (for example, bmcuser1 ), and start the installation.
      Make sure that the user provided during installation is the owner of the pre-created 32K tablespace. You can verify the owner of the tablespace using the following SQL query.
      select TBSPACE, OWNER from SYSCAT.tablespaces where datatype='A' and
      tbspace!='SYSCATSPACE' and PAGESIZE=32768
      During the installation, enter the same user name (for example, bmcuser1) in the AR Database Login field in the AR Database panel.

For remote installations

  1. On the remote computer, complete the following steps:
    1. Create an operating system user account with the same user name that was used in step a (for example, bmcuser1) on the same computer where you will install the AR System server.

      Important

      This DB2 user must have database creation privileges. Database access privileges are not sufficient.

    2. For BMC Remedy AR System root installations or BMC Remedy AR System installations performed by a user who is not a database instance administrator, make the user a member of the following groups, which were created during the DB2 database installation:
      db2iadm1
      db2fadm1
      db2asgrp
    3. If you are migrating the DB2 database or instance to a different computer or environment, provide privileges for the BMC Remedy AR System database user to the tablespace.
      For example:
      GRANT USE OF TABLESPACE <Tablespace> TO USER <DB2DatabaseUserLoginProvidedDuringARSystemInstallation>
      The installer provides tablespace privileges during installation and expects that the Syscat.tbspaceauth table has specific privileges for the grantee of the BMC Remedy AR System database user.
    4. Catalog the database from the DB2 client using a command-line processor.
      The catalog command syntax is:
      db2 catalog tcpip node  <instanceNameAlias> remote <hostName> server <tcpPort>
      For example:
      db2 catalog tcpip node arsdbname remote servername.abc.com server 50000
      
      For more information, see your DB2 documentation.
    5. Confirm that the remote DB2 connections are correct.
      After the remote connection is configured, create a DB2 database on the remote database server and from the client computer DB2 prompt. Then, enter:
      db2 connect to <databaseName>
      <databaseName> is the name of the underlying database (for example, arsystem).
    6. Log in as the user (for example, bmcuser1) on the remote computer, and start the installation.
      During the installation, enter the same user name (for example, bmcuser1 in the AR Database Login field in the AR Database panel.

Creation of a 32 KB tablespace

On a DB2 database, a 32 KB tablespace is created as a System Managed Storage (SMS) on new and overwrite installations of the BMC Remedy AR System server.

The 32 KB tablespace is added during a BMC Remedy AR System installation as follows:

  • During a new installation, a 32 KB tablespace is created in the background with the name given for the regular tablespace but concatenated with _32kb.
    For example, if the tablespace name is ARSystem for the BMC Remedy AR System server, an additional tablespace with a 32 KB page size is created and named ARSystem_32KB.
  • During an overwrite installation, the underlying database is dropped and a new database and tablespace are created as they are for a new installation.
  • During an upgrade from version 7.1.00 to 8.1, the installer checks for the Form: AP:Rule Definition form entry and, on the underlying database, validates the availability of the 32 KB tablespace that is listed in the clause. If the 32 KB tablespace is present, the upgrade continues successfully. If it is not present, the installer creates a 32 KB tablespace similar to the one described for a new installation and continues the installation.

Note

When you create a DMS tablespace, 1 SMS tablespace and 1 SMS temporary tablespace with 32K pagesize are automatically created as they are required by the installer.

If you select to install the Approval Server, the installer adds the Approval Server Form: AP:Rule Definition form entry and its clause with the newly created 32 KB tablespace to the ardb.cfg (ardb.conf) file. (The existence of this file is validated, and if it is not present when you install the Approval Server, the file is created. The Form: AP:Rule Definition form entry is also validated to make sure that the clause contains the correct 32 KB page size tablespace name.)

Pre-creating a database

If you do not have DBA privileges, your database administrator must create an empty database so that you are not asked for database information during the installation.

Note

You must pre-create the database with the same Database Login ID that is used as a value for the BMC Remedy AR System Server DB Login ID installation parameter during the database installation. (For example, ARAdmin).

To pre-create a DB2 database:

  1. Create a database.
    • Create a Unicode database:
      DB2 CREATE DATABASE ARSYSTEM USING CODESET UTF-8 TERRITORY US
    • Create a non-Unicode database:
      DB2 CREATE DATABASE ARSYSTEM
  2. Connect to the created database, for example:
    CONNECT TO ARSYSTEM
  3. Drop the default tablespace.
    drop tablespaces userspace1
  4. Create two bufferpools: one with a 16K pagesize and another with a 32K pagesize.
    Bufferpool names are user-defined (for example: arbp1, arbp2).
    create bufferpool arbp1 size 1000 pagesize 16k
    create bufferpool arbp2 size 1000 pagesize 32k
    
  5. Create one of the following tablespaces:
    • Create Database Managed Storage (DMS) tablespaces using the 16K pagesize bufferpool created in step 4.
      For example:
      CREATE TEMPORARY TABLESPACE ARTMP_PT01 pagesize 16k MANAGED BY DATABASE USING (FILE '/data1/ardata/artmp' 250M) extentsize 32 overhead 24.1 prefetchsize 32 transferrate 0.9 bufferpool arbp1
      CREATE REGULAR TABLESPACE ARSystem pagesize 16k MANAGED BY DATABASE USING (FILE '/data1/ardata/ARSys' 1024M) extentsize 32 overhead 24.1 prefetchsize 32 transferrate 0.9 bufferpool arbp1
      
    • Create System Managed Storage (SMS) tablespaces using the 16K pagesize bufferpool created in step 4.
      For example:
      CREATE TEMPORARY TABLESPACE ARTMP_PT01 pagesize 16k MANAGED BY SYSTEM USING ('artmp') extentsize 32 [overhead 24.1] prefetchsize 32 [transferrate 0.9] bufferpool arbp1
      CREATE REGULAR TABLESPACE ARSystem pagesize 16k MANAGED BY SYSTEM USING ('ardata') extentsize 32 overhead 24.1 prefetchsize 32 transferrate 0.9 bufferpool arbp1
      [dropped table recovery off]
      
      The container (artmp or ardata) can be an absolute or relative directory name.
  6. Create SMS tablespaces using the 32K pagesize bufferpool created in step 4.
    For example:
    CREATE TEMPORARY TABLESPACE ARTMP_PT01_32KB pagesize 32k MANAGED BY SYSTEM USING ('artmp_32KB') extentsize 64 overhead 24.1 prefetchsize 32 transferrate 0.9 bufferpool arbp2
    CREATE REGULAR TABLESPACE ARSystem_32KB pagesize 32k MANAGED BY SYSTEM USING ('ARSys_32KB') extentsize 64 overhead 24.1 prefetchsize 32 transferrate 0.9 bufferpool arbp2
    

    Note

    When you create a DMS tablespace, 1 SMS tablespace and 1 SMS temporary tablespace with 32K pagesize need to be created as they are required by the installer.

    Optional parameters are enclosed in square brackets, for example:
    [ dropped table recovery off]

    Note

    The Dropped Table Recovery Off option can improve performance but it means that you cannot recover a table if it is accidentally dropped.

  7. Grant the created tablespaces permissions for the database user.
    For example:
    GRANT USE OF TABLESPACE
     ARSystem TO USER  <DB2DatabaseUserLoginProvidedDuringARSystemInstallation>
     with grant option
    GRANT USE OF TABLESPACE
     ARSystem_32KB TO USER  <DB2DatabaseUserLoginProvidedDuringARSystemInstallation>
     WITH GRANT OPTION
    
  8. (For UNIX) Start the DB2 instance as the <DB2DatabaseUserLoginProvidedDuringARSystemInstallation>.
    • If you are using the default database user and password:
      db2 connect to ARSystem user aradmin using AR#Admin#
    • If you are using a different database user and password:
      db2 connect to ARSystem user <DB2DatabaseUserLoginProvidedDuringARSystemInstallation> using <DB2DatabaseUserPasswordProvidedDuringARSystemInstallation>
      Alternatively, you can also use the su command to change the owner of the DB2 instance.
      For example:
      su - <DB2DatabaseUserLoginProvidedDuringARSystemInstallation> and then starting the DB2 instance
      
  9. If the following values for the following commands are not already set during the installation of BMC Atrium CMDB, run the following commands:
    DB2=> UPDATE DB CFG for databaseName using APP_CTL_HEAP_SZ 40480 (version 9.4 or earlier)
    DB2=> UPDATE DB CFG for databaseName using APPL_MEMORY AUTOMATIC (version 9.5 or later)
    DB2=> UPDATE DB CFG using INSTANCE_MEMORY AUTOMATIC (version 9.5 or later)
    DB2=> UPDATE DB CFG for databaseName using UTIL_HEAP_SZ 95000
    DB2=> UPDATE DB CFG for databaseName using STMTHEAP 60000
    DB2=> UPDATE DB CFG for databaseName using LOGFILSIZ 4000

    Note

    The default database name is ARSYSTEM.

  10. If the database is on a remote computer, grant the tablespace permission to the ARAdmin user by running the following command:
    DB2=> grant use of tablespace tablespaceName to user aradminUser with grant option;
    
  11. When you finish, perform the following steps:
    1. Enable the database you created.
    2. Set the transactional logs.
      BMC recommends the following settings:

      Log file size (4KB) (LOGFILSIZ)

      20000

      Number of primary log files (LOGPRIMARY)

      8

      Number of secondary log files (LOGSECOND)

      10

      Log retain for recovery enabled (LOGRETAIN)

      OFF

      User exit for logging enabled (USEREXIT)

      OFF

    3. Check that the options are consistent with HADR mode.

AR System database components created for DB2 databases

For IBM DB2 databases, the installer creates the following BMC Remedy AR System database components:

Database components created for DB2

Component

Description

BMC Remedy AR System Database

Database tables that the BMC Remedy AR System installer creates on the DB2 server. The tables store all the data related to the BMC Remedy AR System database.

Tablespaces

Logical layer between the database and the database objects that are stored in the database. The installer creates the following tablespaces:

  • User (USER-DEFINED-TABLESPACE, for example, ARSystem) — Stores user-defined tables. The user tablespace is where the BMC Remedy AR System tables will reside.
  • Temporary (USER-DEFINED-TEMP-TABLESPACE, for example, ARTMPSPC) — Stores temporary tables that are used for short-term activities, such as sorting and displaying search results.
  • Catalog (SYSCATSPACE) — Stores system metatables.

SMS tablespaces

In system-managed tablespaces:

  • The DB2 system manages the container space when the user specifies the container location.
  • The system increases the tablespace size dynamically when the number of records increases.
  • Data is stored in a directory container.

DMS tablespaces

In database-managed spaces:

  • The database administrator (DBA) manages the container size.
  • Data is stored in a file container.
  • Space is allocated when the tablespace is created. You can also increase the size manually, as needed.
    If the DMS space is not sufficient when you want to upgrade the BMC Remedy AR System server, double the pages of the syscatspace.

    Note


    BMC recommends that you use SMS instead of DMS.

Containers

Store physical data and tables corresponding to BMC Remedy AR System. There are three types of containers: file, directory, and disk.

Information added to AR System database configuration file (ardb.cfg or ardb.conf)

  • The AR System installer adds the following lines to the BMC Remedy AR System database configuration file (ardb.cfg or ardb.conf):
    Form: NTE:SYS-NT Process Control
    Clause: IN tablespaceName
    Form: NTE:SYS-NTUnProcessedRecords
    Clause: IN tablespaceName
    Form: SRM:Request
    Clause: IN tablespaceName
    Form: NTE:SYS-Individual NT Control
    Clause: IN tablespaceName
    Form: NTE:SYS-Group NT Control
    Clause: IN tablespaceName

    In the preceding clause, tablespacename is the name of the table space created in step 3.
  • The BMC Remedy ITSM installer adds the following lines to the BMC Remedy AR System database configuration file if you are installing BMC Asset Management.
    Form: AST:PurchaseRequisition-Detail-Signature
    Clause: IN tablespacename
    
    In the preceding clause, tablespacename is the name of the table space created in step 3.
  • The BMC Remedy ITSM installer adds the following lines to the BMC Remedy AR System database configuration file if you are installing BMC Change Management.
    Form: CHG:Infrastructure Change
    Clause: IN tablespacename
    
    In the preceding clause, tablespacename is the name of the table space created in step 3.
  • The BMC Remedy ITSM installer adds the following lines to the BMC Remedy AR System database configuration file if you are installing BMC Service Desk: Incident Management.
    Form: HPD:Help Desk
    Clause: IN tablespacename
    Form: HPD:Search-Assignment Logs
    Clause: IN tablespacename
    Form: HPD:Search-Worklog
    Clause: IN tablespacename
    Form: HPD:IncidentInterface_Create
    Clause: IN tablespacename
    
    In the preceding clause, tablespacename is the name of the tablespace you created earlier.

Minimum DB2 database transaction log size (for upgrades only)

When you upgrade a BMC Remedy AR System 8.1 server that uses a DB2 database in an environment supporting BMC Remedy ITSM applications, BMC recommends a minimum database transaction log file size of 1.3 GB.

Before starting the upgrade, adjust the following DB2 Universal Database configuration parameters to ensure that logfilesize >= 1.3 GB:

  • LOGFILSIZ
  • LOGPRIMARY
  • LOGSECOND

For example:

Log file size (4KB)

(LOGFILSIZ) = 20000

Number of primary log files

(LOGPRIMARY) = 8

Number of secondary log files

(LOGSECOND) = 10

Log retain for recovery enabled

(LOGRETAIN) = OFF

User exit for logging enabled

(USEREXIT) = OFF

Warning

This example is from a test environment and represents a minimum transaction log file size. To determine the log file requirements for your environment, consult your database administrator before beginning the upgrade.

For more information about determining your transaction log file size, go to http://publib.boulder.ibm.com/tividd/td/tec/SC32-1233-00/en_US/HTML/ecoimst65.htm.

Upgrading DB2 (for Service Level Management)

If you are using any version of BMC Service Level Management prior to version 7.6.04 and you want to upgrade to version 8.1, then you must upgrade your BMC SLM DB2 database by running the DB2 database script.

Note

If you are performing a new installation of BMC Service Level Management 8.1, you do not need to complete these steps.

  1. Do one of the following tasks:
    1. During the installation, if the ardb.cfg (ardb.conf) file is not detected, you receive an error message that you must first create the ardb.conf file.
    2. During the installation, if the ardb.cfg (ardb.conf) file exists but there is no SLM:ServiceTarget form entry with clause of 32KB tablespace, you receive an error message that you must execute the rundb2upgrade.sh script.
  2. Run either of the following:
    1. (AIX) Run ./rundb2upgrade.sh.
    2. (Windows) Run rundb2upgrade.bat.
  3. At the User Name prompt, type the AR administrator user name.
  4. At the Password prompt, type the AR administrator user password.
  5. At the AR Server Port prompt, type the AR port number.
  6. Do either of the following tasks:
    1. (AIX) At the AR Database Name prompt, type the AR table space name (case sensitive).
    2. (Windows) at the DB2 Table Space name prompt, type the AR 32KB table space name.
  7. At the AR Installation Directory prompt, type the AR installation path.

    Note

    For Windows, the AR installation path must be in 8.3 format.

  8. At the SLM Installation Directory prompt, type the SLM installation path.
  9. At the Export Target Directory prompt, type the path for the exported data.
  10. After running the script, re-install BMC Service Level Management 8.1.

    Note

    The script file is in the utility directory of DISK 1.

Related topics

Where to go from here

Completing the planning spreadsheet for an upgrade

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments