(DI-2205) Release Notes

New features

• ASM-878: Added a new default monitoring area for the DB6 database

• ASM-923: New Collector for SAP Lock entries (SM12) monitoring (more details)

Improvements

• ASM-855: Possibility to generate Oracle-specific KPIs from central or remote SAP system (more details)

• ASM-857: Documentation updates for standalone Oracle database monitoring (more details)

• ASM-870: Enhanced Collector for Oracle sessions monitoring (more details)

  • New KPIs ORA_SESS_ENQWAIT and ORA_SESS_COMMIT

  • Added new fields ORASID and BLOCKING_SESSION in detail table Oracle active sessions

• ASM-871: Percentage thresholds in Collector for Number ranges are processed as decimals instead of an integer value (more details)

• ASM-877: Possibility to collect details through SQL statement from a remote SAP system

• ASM-879: Improved error handling for SQL collector to store more details about occurred SQL failures (more details)

  • Details for the occurred messages are displayed through the new pop-up window (logs format)

• ASM-882: When default monitoring is started for SAP system with primary HANA or Oracle database, additional collector jobs for HANA or Oracle DB monitoring are automatically started (more details)

• ASM-906: Documentation updates for remote SAP system monitoring (more details)

• ASM-907: Documentation updates for standalone HANA database monitoring (more details)

• ASM-911: Enhanced logic for standalone Oracle database monitoring to support various scenarios for Oracle database monitoring through remote SAP system (more details)

• ASM-912: Enhanced logic for standalone HANA database monitoring to support various scenarios for HANA database monitoring through remote SAP system (more details)

• ASM-920: Added new field CLIENT_CODE into the following detail tables:

  • ABAP Runtime Errors

  • Application logs

  • Monitored BG jobs / Monitored BTC jobs

  • Workload statistics transaction jobs / Workload statistics RFC

  • Queue specific statistics

  • System log info

• ASM-922: Changed descriptions of CPU Load average KPIs (more details)

Resolved issues

• ASM-856: Corrected handling of collector jobs that are in the suspended state

• ASM-859: Incorrect percentage values displayed for Oracle specific KPIs

• ASM-872: Special character '#' stored into Input table for SQL statements when horizontal tab character used in provided SQL statement

• ASM-888: Incorrect calculation of KPIs for total and free size for DB tablespaces

• ASM-894: Messages raised in Collector jobs have been stored in the database table in the incorrect sequence of their occurrence

• ASM-895: KPI Creation wizard didn’t contain the same checks for SQL execution as used in SQL Collector

• ASM-896: Possibility to overwrite the description of an existing default KPI group through the KPI Creation wizard

• ASM-899: Incorrect success message displayed in KPI Creation wizard when already existing detail table name provided

• ASM-901: When the long description of custom KPI changed in the KPI Creation wizard, the changes were not discarded when the user canceled the action

• ASM-903: Content of Input tables was displayed in invalid sort order on higher SAP releases

• ASM-919: Possibility to generate default monitoring profile through KPI Creation wizard

• ASM-921: Lower/Upper limit values were not copied correctly when copying the existing KPI definition

• ASM-925: IDOC Detail collector didn’t use the existing index when selecting data for processing

• ASM-939: Runtime error occurred when displaying any server with negative CPU or RAM values in System settings