Released: Mar 20, 2026

Aggiornamenti in 26.1.031

Funzionalità

• Enhanced SQL Performance module with additional diagnostic graphs:
  • The SQL Performance module for Microsoft SQL Server has been enhanced with additional graphs to improve cross-comparison of performance metrics and simplify troubleshooting.
  • New graphs have been added for Waits, Worker Time, and CPU usage.
  • These graphs allow users to visually correlate different performance indicators and narrow down specific time periods where performance issues occur. Previously, the module primarily relied on Logical Reads and Physical Reads statistics.
  • Users can now better distinguish between CPU-bound workloads, resource waits, and I/O-related activity.
  • The new graphs allow users to select and focus on specific time ranges, enabling more precise analysis and easier navigation between different performance indicators.
• Two new dbWatch properties for Oracle, MS SQL Server, Sybase, PostgreSQL, MySQL, and MariaDB to expose the database server's local time difference relative to UTC. utc_diff_h: UTC offset expressed in hours utc_diff_s: UTC offset expressed in seconds.
• A new dbWatch job to monitor the open_mode status of Pluggable Databases (PDBs) within an Oracle Container Database (CDB) environment. The job query relevant Oracle system views (v$pdbs) to retrieve the current open_mode for each PDB.
• A new dbWatch job that monitors SQL Server authentication logins for lockout events. The job detect locked logins, record relevant metadata in a historical table, and track when the login is unlocked. Optional automatic unlock functionality is supported and controlled by a configurable parameter.
• Developed new Farm Views for the Blocking Event Collector job based on SQL Server Extended Events (XE):
  • The views should provide a clear and centralized overview of where the job is deployed across the farm, including key execution details such as status, runtime behavior, and volume of collected data.
  • This task also includes defining the required properties to support configuration, monitoring, and reporting of the job.
• Improved the network layout view and removed beta tagging.
• Created Query plan viewer.
• Blocking event collector:
  • This job collects SQL Server blocking information using the built-in Blocked Process Report event via Extended Events.
  • It captures both the blocked and the blocking sessions whenever a blocking situation exceeds the configured threshold.
  • The data collected by the Blocking Event Collector job is then visualized in the Management section of dbWatch Monitor.
• Dedicated Audit Server (beta):
  • Audit logs should be stored on a dedicated Audit Server, not on the individual Server that the auditable action occurred.
• Audit log format. Audit logs must be JSON (or similar structured format) that meets ISO27001 (and other relevant) requirements.
• Audit Configuration GUI (beta). Audit settings must be available through a GUI.
• Add, edit and remove user through CCC.
• Updated MS SQL Server Patch Status with Microsoft patches through March 12, 2026. A new version of MS SQL Server Patch Status has been prepared and updated to include Microsoft patch information released through March 12, 2026. This update ensures that patch status checks reflect the latest available SQL Server patch levels and improves the accuracy of version and patch compliance reporting.
• Improved robustness and exception handling in Oracle “Table Fragmentation” maintenance job. The job now handles unexpected conditions more gracefully, reducing the risk of failures during execution.
• Improved robustness of Auto Growth Event Collector when trace file path is unavailable. The Auto Growth Event Collector job has been enhanced to handle scenarios where the default trace file path and name are not available (i.e., when the query returns NULL). Previously, the job could fail with an exception when attempting to access trace information in such cases. The implementation has been updated to gracefully handle missing trace data, preventing unnecessary failures and improving overall stability.
• dbWatch CC Management failure for Oracle when not using SYS account. Some Oracle queries in Management refers to V_$DATAFILE instead of using the public synonym V$DATAFILE. This cause failure in queries using Management user different from SYS, even when the appropriate privileges has been granted.
• Device selection not possible in Sybase Add Instance Wizard. The device selection dropdown is empty.
• Improved SQL Statistics job to detect and visualize execution plan changes. Enhance the SQL Statistics job and the Query Plans visualization to correctly detect and present execution plan changes for SQL statements. The procedure shall capture plan change events reliably (e.g., based on query_plan_hash over time) and store the required metadata so that plan changes are clearly visualized in the Management section of dbWatch Monitor.
• Updated and Cleanup Database Uptime Job and Property Definitions. Implement updates and cleanup improvements to the Database Uptime (for Oracle) job to ensure correct data handling and consistency in historical records. The update includes adjustments to the job logic as well as cleanup of duplicate or inconsistent data entries in the history table. In addition, the associated property definitions for the Database Uptime job must be revised to align with the updated job behavior and ensure correct data retrieval and presentation.
• Updated Template Definitions. Update the predefined template configurations to reflect recent job additions and framework changes. For the Sybase Default template, include the Framework job and the Temp Cache Statistics job as part of the standard template definition. For the MS SQL Server Security and Compliance template, include the new Login Lockout Monitor job.
• Sybase: dbw_registerTask does not update job version during upgrade. On the Sybase platform, the framework procedure dbw_registerTask does not correctly update the job version number during job upgrades. As a result, the job version remains unchanged even after a successful upgrade deployment. The issue is resolved by installing the Framework job version 1.1, which reinstalls the dbw_registerTask procedure and restores correct version handling.
• Sybase: Monitor GUI does not apply job parameter changes. On the Sybase platform, updating dbWatch job parameter values via the Monitor GUI does not work because the stored procedure dbw_setParameter is not being called. As a result, users cannot change parameter values from the GUI. Direct execution of the procedure works as expected, e.g.: exec dbw_setParameter 1, ‘ignore databases’, ‘model, master’.
• Enhanced table statistics check logic and reporting. Improved the table statistics check by refining the evaluation of outdated statistics based on last analyzed age and DML activity percentage. Tables with old statistics but low DML activity are now ignored, and reporting has been updated to clearly reflect this logic in execution results and detail views.
• Improved network log when certificate signing fails. Certificate signing now fails with an error code. Add a more readably error message.
• The missing indexes view has now been extended with a new column user_seeks, making it easier to assess how frequently the suggested indexes are being used and helping prioritize further investigation.
• Auto-configure XEvent output path. Update XEvent-based jobs to automatically use the SQL Server ERRORLOG directory as the default output location during installation, while keeping the path parameter for optional customization. This avoids the need to know instance-specific log paths and prevents issues when an empty path is intended.
• Management based local report for no engine jobs. The management specification based local report do not work for no engine jobs. Add support for this.
• Improved Owner Mapping Parameters. Update the stored procedure parameter naming to improve clarity and readability. In addition, introduce a new parameter “prefer existing owner login” to allow dbo to be mapped to a previously registered server login when an owner-to-login mapping is missing, instead of always using the default owner login.
• Resizable Description Window. Add support for resizing the description window, allowing users to adjust its size for better readability and usability when viewing longer descriptions.
• Missing description. For TABLE-type presentations, neither the description icon (percent icon) nor the text tags are displayed. This functionality works correctly for local reports of the new admin type.
• Not active menu. In CODE-type presentations, the menu actions such as Refresh and Detach are currently inactive/disabled.
• Popup when unselecting “Local database schema” in the add instance wizard. When unselecting “Local database schema” in the add instance wizard, a popup needs to tell the user about the impact of their choices. No history, 80-90% less monitoring jobs available, a lot less reporting etc.
• Dataguard Archivelog Gap. The Dataguard archivelog gap job has been improved to correctly check archivelog gaps across all threads on the primary RAC nodes and compare them against the standby node(s). In addition, the job feedback and reporting have been enhanced to provide clearer and more accurate results.
• Audit all actions. Make sure all actions are audited.
• Logarithmic scale on chart y axis.

Correzioni

• Fixed issue in Health Check Report graph “Performance statistics history (avg)” for MS SQL Server. The issue caused incorrect or inconsistent presentation of performance statistics. The fix ensures that the graph now correctly reflects the underlying data and provides accurate average performance metrics over time.
• Job pre execution hangs for 30 ish seconds.
• Tables with missing column header text are misaligned. When a table column has no text, the filter is misaligned and the column header looks strange.
• Sorting a table of integers when a value is null fails.
• Missing privilege check for node info request. It is possible to ask for node information (ip, hostname, domain aso) without having an authorized user by sending a DbwNodeCommand message with command type DbwNodeCommand.COMMAND_INFO. This can be seen in the Network Layout view, where the hostname for a node can be seen if the node is in another domain.
• Bug in ThreadPoolUtils.scheduler for one time tasks. Calling ThreadPoolUtils.scheduler.apply(() => {.. }, ×, TimeUnit) will add an object to taskList that is never removed. Causing a memory leak and high cpu load after a while.
• Oracle Pluggable DB marking. Pluggable databases with instance_class 'PDB Primary' are not marked as PDB.
• Postgres engine install wrong schema. Something has happened in devel, causing Postgres engine install to fail.
• Bug in handling of timezones in range controlled charts.
• Rename instance gives save changes popup. After renaming an instance, the user is immediately shown an annoying “save changes” popup.
• Item active resolving in farm is buggy. Item active is not resolving correctly in farm for ‘Blocking events’ and ‘Database copy’.
• Plaintext password in output log. Password appears in plaintext in the output.log when testing AD.
• Zoom with “category-line-chart” is buggy. When using a category-line-chart as a range controller in management, the zooming does not work correctly.
• Username collision when creating user. It is possible to accidentally “overwrite” an existing dbwatch user when creating a new user with a username that already exists.
• Web is unstable. Sometimes there is an issue after server upgrade, where the webserver gives no data. Deleting crypto seems to fix the problem.
• Fixed compatibility tag for Oracle SQL Statistics job to allow installation on Oracle 11. Updated the compatibility tag for the SQL Statistics job on the Oracle platform to ensure that the job can be installed and executed on Oracle 11 database versions. Previously, the compatibility definition prevented installation of the job on Oracle 11 environments even though the job logic is compatible with these versions.
• Fixed column text wrapping issue in Global Security and Compliance Report (MS SQL Server). A recent change in font size within the Global Security and Compliance report for MS SQL Server caused layout issues in certain table columns. As a result, some column values were improperly split or wrapped, affecting readability and report presentation. The report layout has now been adjusted to ensure that column values display correctly without unintended word splitting.
• Fixed empty database platform views in SQL Statistics Farm view. In multi-domain environments, the SQL Statistics Farm database platform views were displayed as empty. This issue has now been corrected, and the views are properly populated across domains.
• Fixed duplicate database rows in space usage query. Previously, on Sybase instances the space usage query returned duplicate rows when a database spanned multiple device fragments. The query has now been corrected to aggregate usage per database, ensuring each database appears only once.
• Fixed ORA-0042 errors in properties querying X$ performance views. Implement fixes for two Oracle properties that generate ORA-0042: table or view does not exist errors when executed. The affected properties attempt to retrieve information from the internal performance views x$dbgalertext and x$ksppsv. In environments where the executing user does not have sufficient privileges to access these internal X$ views, the properties fail with ORA-0042 errors.
• Fixed division-by-zero in Data Cache Statistics and Temp Cache Statistics jobs. Implement improvements to the Data Cache Statistics and Temp Cache Statistics jobs on the Sybase platform to prevent division-by-zero errors when calculating performance metrics. Both jobs have been updated to correctly handle edge cases in the calculation of cache hit ratio and logical reads per second, ensuring that division by zero does not occur when underlying counter values are zero.
• Incorrect First/Last Execution Dates Outside Selected Time Range. In the SQL Performance module (MS SQL Server platform), the table showing resource-intensive SQL statements could display First execution and Last execution timestamps that fell outside the selected time range. This behavior was misleading and did not reflect the active filtering period. The issue has now been fixed, and execution timestamps are correctly constrained to the selected time window.
• Arithmetic overflow in “Data file size check”. The “Data file size check” job for MS SQL Server could raise an Arithmetic overflow error when data files are very large (several TB). The calculation logic has been corrected and the issue is now fixed.
• Improved time based x-axis in charts. Time based x axises in charts should “snap” the labels to nicer timestamps for better readability. Also consider marking the charts with time bounderies like minutes/hours/days.
• Delete CCC node. It is not possible to delete a ccc node through the domain configuration GUI.