This section lists the issues that you might encounter during TrueSight Server Automation - Data Warehouse configuration.

Configuration fails if passwords contain special characters

The configuration fails if the TrueSight Server Automation database password or the reports data warehouse password contain the following special characters:

• Ampersand (&)
• Double quotes (" ")
• Pipe (|)
• Less than sign (<)
• Greater than sign (>)
• Single quotes (' ')
• Forward slash (/)
• Semicolon (;)
• Percent (%)

Workaround: Avoid using special characters in passwords.

Changing the password fails by using change_password.nsh script

If you have installed TrueSight Server Automation - Data Warehouse on Microsoft Windows 2016 operating system, you cannot change the password of the DWAdmin user by using the change_password.nsh script and the following error is displayed:

change_password.nsh:46: no matches found: *.jar Error=2 (no such file or directory)
Error: Could not find or load main class com.bmc.bbds.util.PasswordManager

This issue occurs because the NSH is not upgraded to version 8.9.04.

Workaround:

Do one of the following:

• Upgrade the NSH to version 8.9.04.
• Do the following:
  1. Open the change_password.nsh script and comment the cd "$REPORTS_HOME/shared/ConfigurationManagement/libs" line as shown below:
     #cd "$REPORTS_HOME/shared/ConfigurationManagement/libs"
  2. Change the directory location to <TSSA-DWInstallationDirectory>\shared\ConfigurationManagement\libs. For example:
     cd "C:\Program Files\BMC Software\TSSA-DW\shared\ConfigurationManagement\libs"
  3. Run the change_password.nsh script as shown below:
     nsh ..\change_password.nsh

Context creation fails on Oracle

On Oracle, configuration fails because the context could not be created for a site.

Context creation fails for the following reasons:

• The tnsnames.ora file on the reports data warehouse database server does not contain the TNS entry for the TrueSight Server Automation database or the TNS Name does not match with the SID.
• The tnsnames.ora file on the TrueSight Server Automation database server does not contain the TNS entry for the reports data warehouse or the TNS Name does not match with the SID.

Solution: Complete the following steps:

1. Ensure that the following requirements are met:
   • The tnsnames.ora file on the reports data warehouse database server contains the TNS entry for the TrueSight Server Automation database and the TNS Name matches with the SID.
   • The tnsnames.ora file on the TrueSight Server Automation database server contains the TNS entry for the reports data warehouse and the TNS Name matches with the SID.
2. Perform the post-installation configurations again. For more information, see Configuring TrueSight Server Automation - Data Warehouse by using the console.

Database Link Connection Test Error

On Microsoft SQL Server, the configuration process can fail with the following error message:

Database Link Connection Test Error: User does not have permission to perform this action. Please create linked server with name: BSA_<SiteID>_<buildNo>.

The configuration process uses the credentials of the reports data warehouse user to create the linked server between a TrueSight Server Automation database (site) and the reports data warehouse. This user must be assigned to the sysadmin role. If this user is not assigned the sysadmin role, the configuration process fails. 

When the error occurs, the post-installation configuration screen prompts you to create a linked server in the following format: BSA_<SiteID>_<buildNo>. 

Solution: Create a linked server between the TrueSight Server Automation database and the reports data warehouse: 

1. If you have not already done so, copy the installation scripts from the TSSA-DW<version>external-files.zip file into a directory. 

   If you extract the entire contents of TSSA-DW<version>external-files.zip, the scripts are copied into the /Sqlserver directory below the directory that you specify.

2. From the reports data warehouse location, log on to SQL Server Management Studio as sa.
3. Navigate to the directory in which you extracted the installation scripts.

4. Locate the create_linked_server_for_om.sql file and open it. 
   The script file contains variables related to the TrueSight Server Automation database, such as user name or database name.

5. Open New Query.
6. Copy the contents of the script file and paste the contents into the query window.

7. For each parameter in the file, provide the appropriate value for the TrueSight Server Automation database.

   • @om_sqlsvr_instance is the name of the SQL Server instance on which the TrueSight Server Automation database resides.

     • If this is a default instance on a computer, use the computer name (for example, Computer1).

     • If this is a named instance, use the computer name and instance, with the format as in the following example: Computer1\Instance1.

   • @om_db_name is the name of the TrueSight Server Automation database.

   • @om_sqlsvr_login is the SQL Server logon ID for connecting to the TrueSight Server Automation database.

   • @om_sqlsvr_pwd is the clear text password for the previous logon ID. 
     The following example shows how to include these parameters in the new file:

     set @om_sqlsvr_instance=N'Computer1\Instance1' 
set @om_db_name=N'bladelogic' 
set @om_sqlsvr_login=N'sa' 
set @om_sqlsvr_pwd=N'sa'

8. Replace all the instances of  'DB_SITE1_LINK ' with 'BSA_<SiteID>_<buildNo>'.

   For a specific TrueSight Server Automation - Data Warehouse version, use the corresponding build number in the link name. For example, if the build number is 8.9.04.86, the link name for the primary site is BSA_SITE1_86. 

9. Save the changes to a new file.

   Warning about saving the file

   Do not save your changes to the original script file. You might need that file later.

10. Run the newly created script.
11. In the left pane of SQL Server Management Studio, navigate to Server Object/Linked Server and verify that the new linked server was added.

12. In a SQL Server Management Studio query window, test the linked server by executing the following statement:

    Select * from BSA_<SiteID>_<buildNo>.<blDatabase>.dbo.agent_state

    <blDatabase> is the same database name that you used when you replaced the <Database name for OM> variable in step 7. 
    If the linked server was successfully added, a table is displayed with a description of values that indicate possible agent states. The table contents vary based on the version of TrueSight Server Automation used for the database.

13. Exit SQL Server Management Studio. 
14. Perform the post-installation configurations again. For more information, see Configuring TrueSight Server Automation - Data Warehouse by using the console.