Unsupported content

 

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.

Prerequisite for using BMC Decision Support for Server Automation 8.9.00 with BMC Server Automation


This topic describes a hotfix that can be installed on BMC Decision Support for Server Automation 8.9.

Important

BMC Decision Support for Server Automation version 8.9.00 is not compatible with BMC Server Automation 8.9.01, 8.9.01.001, 8.9.02 or TrueSight Server Automation 8.9.03, 8.9.03.001, 8.9.04, or 8.9.04.001. To use BMC Server Automation 8.9.01, 8.9.01.001, 8.9.01.002, 8.9.02 or TrueSight Server Automation 8.9.03, 8.9.03.001, 8.9.04, or 8.9.04.001 with BMC Decision Support for Server Automation, you must apply a hotfix on BMC Decision Support for Server Automation 8.9.00.

Updates

The fix for BMC Decision Support for Server Automation version 8.9.00 includes the fixes for the following product issues:

Defect or RFE IDDescriptionAffected versions of BMC Decision Support for Server Automation

QM002363748

Build Date property for AIX (Filesets and Service Packs) was missing.

A new property Build Date has been added in AIX  for the Filesets and Service Packs. You can view this property in the following locations:

  • Extended Properties tab of the Filesets and Properties tab of the Filesets
  • AIX Container Properties tab of the Service Packs

For more information, see Examining patch properties for AIX.

8.9.00
QM002207666

BMC Decision Support for Server Automation is not compatible with BMC Server Automation 8.9.01.

8.9.00
QM002207010BMC Decision Support for Server Automation does not display SCAP rule severity attribute in reports.8.7.00,
8.8.00,
8.9.00
QM002165911

(Applicable only for Microsoft SQL Server database) Archival fails on Microsoft SQL Server 2012 and later versions with the following error message:

[Microsoft][ODBC Driver 11 for SQL Server]Warning: BCP import with a format file will convert empty strings in delimited columns to NULL.

8.7.00,
8.8.00,
8.9.00
QM002289075(Applicable only for Microsoft SQL Server database) ETL operation fails for inventory domain while loading incremental data.8.9.00

The following table lists the open issue in BMC Decision Support for Server Automation.

Defect or RFE IDDescriptionAffected versions of BMC Decision Support for Server Automation
DRBSP-14716

Cognos - Query Studio report displays data for a BMC Server Automation or TrueSight Server Automation site even if there is no AIX Fileset data in the database for that site.

8.9.00 + BSA_89SP4_Enablement.zip


Downloading the files

Download the zip package corresponding to the version of BMC Server Automation or TrueSight Server Automation in your environment from the following ftp location and extract its contents to a temporary location on the BMC Decision Support for Server Automation server.

Applying the hotfix for BMC Server Automation or TrueSight Server Automation

The following section mentions the steps to install the hotfix.

Before you begin

Ensure that you have applied BDSSA89_LICENSE_HOTFIX.zip. For information about how to apply the license hotfix, see Downloading and applying the licensing hotfix .

For existing BMC Decision Support for Server Automation 8.9.00 environments

Perform the following steps to install the fix to allow BMC Decision Support for Server Automation 8.9.00 to work with BMC Server Automation or TrueSight Server Automation.

Step 1: Installing the files

Perform the following steps on the BMC Decision Support for Server Automation server:

  1. Ensure that you have downloaded the BSA_89SP4_Enablement.zip file from the FTP location as mentioned in the Downloading the files section.

  2. Copy and extract the BSA_89SP4_Enablement.zip zip package to a temporary directory on the reports server. For example,

    WindowsC:\temp
    Linux/tmp
  3. Navigate to the following paths in the temporary directory and open a cmd or shell terminal:

    WindowsOpen a command prompt from ..\temp\BSA_<Version>_Enablement
    LinuxOpen shell terminal from ../tmp/BSA_<Version>_Enablement
  4. Execute the bdssaHotfixInstaller.nsh script. Use the following command in the cmd or shell terminal:

    Windowsnsh bdssaHotfixInstaller_windows.nsh
    Linuxnsh bdssaHotfixInstaller_linux.nsh

    Note

    The OdiDeleteScan Oracle ODI command might take a long time depending on the a amount of history. For more information, see the knowledge article 000025342 (https://communities.bmc.com/docs/DOC-101231).

Step 2: Configuring after installation

Perform the following steps only after you have installed the patch on the reports server:

Depending on whether you are using a Microsoft SQL Server or an Oracle database server, select the appropriate tab below and perform the steps on your database.

    1. Navigate to the \postinstall\ORACLE directory and copy all the scripts to a temporary directory.
    2. Depending on whether you have a char setup or nchar setup, navigate to the \ORACLE\char or \ORACLE\nchar directory. You can use the following query to check whether the warehouse schema is CHAR or NCHAR:

      Select DATA_TYPE from USER_TAB_COLUMNS where TABLE_NAME = 'D_BLUSER' and COLUMN_NAME = 'NAME';

      If the schema is CHAR type, VARCHAR2 is returned as the output. If the schema is NCHAR type, NVARCHAR2 is returned as the output.

    3. Log on to the BMC Decision Support for Server Automation warehouse database.
    4. Connect to SQL *Plus by using the following command:
      sqlplus <username>/<password>@tnsentryforbdssadwdb

      For example, sqlplus BDSSA_DW/<password>@tnsentryforbdssadwdb
    5. Run the following scripts:
      sqlplus> start upgrade_ddl_statements.sql
      sqlplus> start upgrade_dml_system_property.sql
      sqlplus> start ovaldi_fix.sql

    1. Navigate to the \postinstall\SQLSERVER directory and copy all the scripts to a temporary directory.
    2. Depending on whether you have a char setup or nchar setup, navigate to the \SQLSERVER\char or \SQLSERVER\nchar directory. You can use the following query to check whether the warehouse schema is CHAR or NCHAR:

      select t.name as data_type from sys.columns c join sys.types t on c.user_type_id = t.user_type_id where OBJECT_NAME(object_id) = 'D_BLUSER' and c.name = 'NAME';
    3. Copy and execute the entire script in your SQL Integrated Development Environment (IDE), such as, Query Analyzer or use the sqlcmd utility to execute the following scripts:

      sqlcmd -S <bdssaDWDbServer> -U <bdssaDwDbUser> -P <bdssaDwuserpassword> -d <BDSSADWdatabase> -i upgrade_ddl_statements.sql -o upgrade_ddl_statements.log
      sqlcmd -S <bdssaDWDbServer> -U <bdssaDwDbUser> -P <bdssaDwuserpassword> -d <BDSSADWdatabase> -i upgrade_dml_system_property.sql -o upgrade_dml_system_property.log
      sqlcmd -S <bdssaDWDbServer> -U <bdssaDwDbUser> -P <bdssaDwuserpassword> -d <BDSSADWdatabase> -i ovaldi_fix.sql -o ovaldi_fix.log
      sqlcmd -S <bdssaDWDbServer> -U <bdssaDwDbUser> -P <bdssaDwuserpassword> -d <BDSSADWdatabase> -i SP_TBL_BCP_REMOVE_DATA.sql -o SP_TBL_BCP_REMOVE_DATA.log

      Replace the variables with the values described in the following table:

      Variable Value
      <bdssaDWDbServer> Name of the SQL server with the BMC Decision Support for Server Automation warehouse database
      <BDSSADWdatabase> Name of the BMC Decision Support for Server Automation warehouse database
      <bdssaDwDbUser> Database owner of the BMC Decision Support for Server Automation warehouse database.  For a list of user accounts that are created and used by BMC Decision Support for Server Automation, see User accounts.
      <bdssaDwuserpassword> Password of the database owner
    4. Check the output logs for any error messages.

    Step 3: Publishing latest Cognos model

    You run extract, transform, and load (ETL) for publishing latest Cognos model or you can perform the following steps:

    1. Go to the <BDS_HOME>/shared/odi/bin directory.
    2. Execute the update_cognos_model_properties.nsh script by using the following command in cmd or shell terminal:
      nsh update_cognos_model_properties.nsh -f
    3. Go to Query Studio after the script has been executed successfully.
    4. Verify that the new Build Date attribute have been added at the following locations:

      BSA_89SP4_Enablement.zip

      Patch>Patch Overview>Patch Details>AIX Container>
      Patch>Patch Overview>Patch Details>AIX Fileset>

    Step 4: (Optional) Adding new TrueSight Server Automation site in BMC Decision Support for Server Automation

    To add a new BMC Server Automation 8.9.01, 8.9.01.001, 8.9.02 or TrueSight Server Automation 8.9.03, 8.9.03.001, or 8.9.04 site to BMC Decision Support for Server Automation after applying the hotfix, perform the following steps:

    1. Log on to BMC Decision Support for Server Automation reports server.
    2. Navigate to the <BDS_HOME>/shared directory.
    3. Back up the version.properties file.
    4. Open the version.properties file with a text editor and change the value of the version.maint parameter.

      BSA_89SP4_Enablement.zip

      version.maint=04.
    5. Save the file.
    6. Launch the BMC Decision Support for Server Automation Console.
    7. Add the Server Automation site. For more information, see Adding sites.
    8. Run the extract, transfer, and load (ETL) process.

    For new BMC Decision Support for Server Automation environment

    To install BMC Decision Support for Server Automation 8.9.00 and apply the hotfix to work with TrueSight Server Automation, perform the following steps:

    1. Install BMC Decision Support for Server Automation 8.9.00.
    2. Navigate to the <BDS_HOME>/shared directory.
    3. Back up the version.properties file.
    4. Open the version.properties file with a text editor and change the value of the version.maint parameter.

      BSA_89SP4_Enablement.zipversion.maint=04.
    5. Save the file.
    6. Configure BMC Decision Support for Server Automation 8.9.00 by using the console. For more information, see Configuring the product by using the console.
    7. Once the configuration is completed, reset the version.properties file to the default value.
    8. Install the appropriate hotfix as mentioned in the Downloading the files section.
    9. Run the extract, transfer, and load (ETL) process for the primary site.
    10. Go to Query Studio after the script has been executed successfully.
    11. Verify that the new Build Date attribute have been added at the following locations:

      BSA_89SP4_Enablement.zip

      Patch>Patch Overview>Patch Details>AIX Container>
      Patch>Patch Overview>Patch Details>AIX Fileset>

    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