Skip to Content
Information
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.

Collecting diagnostics

If you need to contact BMC Support to resolve an installation issue, ensure that you provide the support team with the following files:

File name and location

Description

BDSSAInstallationDirectory/logs/Install.log

Installation configuration log

BDSSAInstallationDirectory/local.properties

Installation parameters file

BDSSAInstallationDirectory/logs/blauthprovider.log

BMC Server Automation authentication provider log

BDSSAInstallationDirectory/logs/appserver.log

BMC Server Automation authentication server log

BDSSAInstallationDirectory/logs/cogstartup.xml

Cognos configuration file

BDSSAInstallationDirectory/logs/cogserver.log

Cognos execution log

BDSSAInstallationDirectory/logs/blrptadmin.log

Report Administration Utility log

BDSSAInstallationDirectory/logs/ETL/timeStamp/site_siteID_timeStamp_run_etl.log

You need this log file if the ETL script fails.

ETL log

BDSSAInstallationDirectory/logs/etl/etl_performance_YYYYMMDDhhmmss_info.log

ETL performance log
To generate this log file, use the following command from the BDSSAInstallationDirectory\etl\bin directory:

nsh get_etl_performance_info.nsh -d <n>

The d option generates the detailed log for last n days.

BDSSAInstallationDirectory/logs/etl/etl_debug.log

ETL debugging log

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Decision Support for Server Automation 8.3