Known issues and workarounds

QM001669485

In a Microsoft Windows Server 2003 computer, when you install BMC TrueSight Report Engine, on the Time Zone Selection page, the time zone that is selected by default depends on the time zone of the computer on which you are installing BMC TrueSight Report Engine. If many cities share a particular time zone, by default, the first entry in the list is selected. If you do not change the default time zone, you may set an incorrect time zone for the BMC TrueSight Report Engine.

Workaround: Manually change the time zone of the BMC TrueSight Report Engine.

QM001730634

The following database error is displayed when you use the Performance Interval Size object in query filters.

Workaround: Do not use this object as a filter. Instead, use a condition object.

QM001732682

For both Oracle and Sybase databases on Linux, report engine does not encrypt the BMC TrueSight Infrastructure Management Server password in the BPPM_SERVER_CONFIG table after registration.

Workaround: Do not access the internal report engine tables through the database.

QM001732926

Rows pertaining to PATROL Agent in DEVICE_CNTL, ITEM_CFG and PARAM_CNTL config tables do not match after config job due to frequent updates of the TIMEDISCOVERED column in DEVICE_CNTL.

Workaround: Wait for the next data transfer cycle.

QM001743732

For performance reporting, if objects from the aggregation level class or measure class are selected, then reporting start and end dates are not required because the date prompts for performance objects are mandatory. If you select the start and end dates, then the prompt for the dates is displayed twice.

QM001748631

While installing the Report Engine on Red Hat Enterprise Linux version 6.2, the following error message is displayed:

You can ignore this error message.

QM001747808

If a difference of time zones between the BMC TrueSight Infrastructure Management Server and the BMC TrueSight Report Engine exists and the difference has an offset of 30 minutes, the rate data will have a range of 1 hour with 30 minutes offset in it. For example, 00:30 to 01:30, 01:30 to 2:30, and so on.

QM001764805

The Escalated Incidents report does not display escalated incident data.

Workaround: See Knowledge Article KA377809 for the workaround.

QM001766038

If STATS data is not available after drill down from daily to time stamp, BusinessObjects displays an error if you click Drill Up to Hour to go back to view hourly data.

Workaround: SAP will fix this in patch 4.6.

QM001774212

The Business Intelligence launch pad Home page does not show images for recently viewed documents and the other three panes, when SAP BusinessObjects is installed on UNIX.

QM001795220

If you upgrade the Report Engine during the time the VW_CONFIGDATA view is being refreshed, certain SQL scripts may fail.

Workaround: Wait until the VW_CONFIGDATA view is completely refreshed and rerun the SQL scripts after the upgrade. For more information, see Knowledge Article KA401278.

QM001798284

The Response Time by Priority and Operator - Details report and Response Time by Severity and Operator - Details report do not work in SAP BusinessObjects Enterprise version 4.0 Service Pack 4.