This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Server Automation
TrueSight User Experience
BSA/TSSA All Versions
I am experiencing slower than expected performance from my BladeLogic Server Automation (BSA/TSSA) console. This might be confined to specific operations or may be a more general performance issue across many actions and operations. What information should be gathered to help troubleshoot the issue and determine the root cause?
A) Useful High-Level questions to answer to help BMC Customer Support understand the problematic behavior
3) Health and Value Dashboard results zip file: The BSA Health and Value dashboard stores its results in the <File Server Storage>\dashboards\reports\latest directory. See below example. Please zip up the most-recent directory and provide the resultant zip file:
a) Console Logs - perform the following steps on the BSA Console workstation:
b) Configuration Apperver Logs - perform the following steps on the BSA Application Server which the console is connecting to:
1. Backup the following file: "<TSSA_INSTALL_DIR>/NSH/br/deployments/<deployments>/lob4j.properties
2. Edit the following line:
You don’t have to restart the application server. After 30 to 40 seconds it will start logging debug entries.
c) Reproduce the issue and carefully note the timeframe during which the issue was reproduced.
Undo the lob4j.properties change from "b" above after reproducing the issue
d) Generate Support Data: Run the “Generate Support Data” with the below options checked/selected for each Application Server in the environment. Note that the tool can be run once with all application server selected.This video discusses how to run the “Generate Support Data” utility.
e) Database Reports - Oracle
AWR, ADDM and ASH report for the hour duringwhich issue was reproduced.
Also, short AWR report for example 10 mins by following below link and steps
f) Database Reports - SQL Server
Run the actions that are slow in that GUI, note what actions are slow, then stop the DB trace and send the trace and the actions/times.
2. Database maintenance job history. Please follow below steps.
a. Go to SQLServer Management Console
b. Login using sysdba user
c. Under Object Explorer, expand to ‘SQL Server Agent’
d. Right click on ‘Jobs’ and click ‘View History’
e. Select all history for last 60 days and export to excel.
3. While the issue is being reproduced please capture the output of these queries. These may need to be run by the DBA as the sys users.
SELECT r.start_time [Start Time],session_ID [SPID],
SELECT TOP 50
WHEN -1 THEN DATALENGTH(eqt.TEXT)
END - eqs.statement_start_offset)/2)+1)
,eqs.total_elapsed_time/1000000 AS Total_elapsed_time_Secs
,eqs.last_elapsed_time/1000000 AS Last_elapsed_time_Secs
FROM sys.dm_exec_query_stats eqs
CROSS APPLY sys.dm_exec_sql_text(eqs.sql_handle) eqt
CROSS APPLY sys.dm_exec_query_plan(eqs.plan_handle) eqp
ORDER BY eqs.total_worker_time DESC;
SELECT TOP 10
FROM sys.[dm_os_wait_stats] AS [ws]
ORDER BY [wait_time_ms] DESC;