PostgreSQL Security & Compliance checks for logging and auditing configuration. Created a set of Security & Compliance (S&C) checks for PostgreSQL related to logging, security, and auditing configuration. The purpose is to validate whether PostgreSQL instances are configured according to recommended security and audit logging practices.
PostgreSQL job for validating log_destination configuration. Introduced a new job for the PostgreSQL platform within the Security and Compliance area to validate logging configuration. The job checks whether the log_destination parameter is properly configured to ensure that server messages are captured. PostgreSQL supports multiple logging destinations such as stderr, csvlog, syslog, and jsonlog (and eventlog on Windows).
PostgreSQL Security & Compliance checks for Access Control. Implemented new PostgreSQL Security & Compliance checks focused on Access Control. The checks should verify relevant PostgreSQL user, role, privilege, and authentication settings to help identify insecure access configurations and support compliance reporting.
PostgresSQL Security & Compliance report. Implemented a PostgreSQL Security & Compliance Report that aggregates and presents the results from PostgreSQL Security & Compliance jobs.
PostgreSQL Security and Compliance job templates. Created two new job templates for the PostgreSQL platform, equivalent to the existing Security and Compliance (MS SQL Server) – weekly and Security and Compliance (MS SQL Server) – weekly NO alerts templates.
PostgreSQL job for validating log_filename configuration. Implemented a new PostgreSQL Security & Compliance job for validating the `log_filename` configuration parameter against CIS PostgreSQL Benchmark recommendations. The job verifies that the configured log file naming pattern complies with organizational logging policies and supports proper log rotation and audit log management. The implementation includes configuration validation, historical tracking, reporting, and graphical presentation of collected parameter values over time.
PostgreSQL job for validating log_directory configuration. Implemented a new PostgreSQL Security & Compliance job for validating the `log_directory` configuration parameter against CIS PostgreSQL Benchmark recommendations. The job verifies that the configured log destination directory complies with organizational logging policies and ensures that PostgreSQL server logs are written to an appropriate and accessible location. The implementation includes configuration validation, historical tracking, reporting, and graphical presentation of collected parameter values over time.
Added PostgreSQL Support for Security and Compliance Farm Views. Extend the existing Security and Compliance Farm Views framework to support PostgreSQL environments.
Support for full CRON schedule in monitoring pause/ alerting pause.
Added a configurable “deep” network logging. When a server has a heavy load of incoming messages there is no way of knowing what the messages are and what the source is. This provides a toggleable way of increasing logging.
Added 'replacenone' function to replace NoValue with something in FDL. It will sometimes be useful to have the possibility to replace NoValue with something.
Introduced new FDL properties for AG performance monitoring. Implemented a series of new FDL properties related to AG (Availability Group) performance monitoring. The update includes additional metrics and properties intended to improve visibility into AG performance behavior and provide extended monitoring capabilities for SQL Server Availability Groups within dbWatch Monitor.
Differential Backup Monitoring Job for Microsoft SQL Server. Introduced a new monitoring job in dbWatch for Microsoft SQL Server that verifies the existence and freshness of differential backups (backup type I).
Restrict access to autodiscovery. A user that is not allows to add instances, should not have access to the autodiscovery features.
Improved graph documentation for MS SQL Server Performance Module. Updated and improved the documentation text (titles and descriptions) for graphs in the MS SQL Server Performance Module to ensure clearer explanations of what each graph shows and how to interpret the metrics.
Saving instance config checks file write access. Saving an instance configuration with missing file write privileges will fail silently. This provides user feedback informing that the write failed.
Async loading of job compatibilities.
Oracle job “Table statistics check”: exclude temporary tables. Enhancements have been made to the Oracle job “Table statistics check”. The job has been updated to exclude temporary tables from the statistics evaluation, as these should not be part of regular statistics checks. In addition, the code has been improved to handle NULL values more robustly, ensuring that NULL values are no longer displayed in the details column.
Defined is_multitenant property for Oracle 11 and earlier. In the Management > Storage section, the `is_multitenant` property is required to correctly display information about tablespaces and datafiles. For Oracle 11 and earlier versions, multitenant architecture is not supported. Therefore, this property should be explicitly defined with a static value of `0`. Currently, this property is not set for these versions, which results in missing or incomplete information in the Storage view (tablespaces and datafiles not being displayed).
Metadata transferred correctly. In a Data Guard scenario, when a switchover occurs and job specification)is moved from the original primary to the new primary instance, engine jobs that rely on property-code (Java code executed before the procedure) no longer execute this code. The metadata related to property-code is not properly registered on the new primary instance. As a result, the job does not function as expected unless it is reinstalled. When switching back to the original primary instance, the job works as expected again. This affects jobs such as “PDB state monitor”, which rely on this functionality.
Feedback on license overuse. It is possible to overuse a license when adding instances through ccc.
Improved and standardized graph/table descriptions and layout (Oracle Performance). Enhanced and standardized descriptions and layout for graphs and tables in the Performance section of dbWatch Monitor for Oracle. The update includes improved descriptions, better consistency in terminology, and minor UI/layout adjustments to improve readability and usability. New graphs for SGA memory statistics, UGA / PGA (User memory statistics) and CPU load.
Improved license summary in domain config.
Enhanced PostgreSQL engine script to support procedure-based job execution. Improved the engine script for the PostgreSQL platform by introducing support for executing jobs implemented as stored procedures. A new execution procedure has been added to handle jobs written as PL/pgSQL procedures. At the same time, backward compatibility is maintained by continuing to support jobs implemented as functions. This ensures a more flexible and future-proof execution model while preserving compatibility with existing implementations.
Corrected PostgreSQL job metadata for functions registered as procedures. Updated PostgreSQL platform job definitions where functions were incorrectly registered as procedures in job metadata.
Increased authentication tag length from 96 to 128 in GCM setup.
Improved CertID computation to reduce likelihood of collision.
Improved Audit Configuration. Map audit policies to security groups for better usability. Currently audit policies are applied to specific servers/instances. This means new instances are not audited until it is explicitly added to the policy. By using security groups, there is less chance of “forgetting” to add auditing to an instance.
Visual marking of content already added in AddContent dialogs. When configuring Service Group, Security Groups, Audit Policies it is difficult to tell what content is already added because it is still available in the add dialog.
Improved exception handling in Blocking Statistics. If an error occurs in the final cleanup block, the same CATCH block may attempt to close/deallocate a cursor that does not exist or is already closed, potentially generating additional exceptions and masking the original error. Updated the procedure to verify that the cursor exists before attempting to CLOSE/DEALLOCATE it.
New file size FDL Properties for MS SQL Server. Introduced new properties in FDL for Microsoft SQL Server that expose the size of database data files and transaction log files. These properties make it possible to visualize size of databases within dbWatch Web Server.
Job Template view added mark when parameter override is in use.
Refactored SQL Server Database Backup Check to Monitor Full Backups Only. Reviewed and simplified the existing SQL Server “Database backup” monitoring job so that it only validates Full Database Backups (backup type D).
Changed default dbWatch database name from dbwatch to dbwatch_cc in remaining jobs. Updated remaining dbWatch jobs and related definitions that still use dbwatch as the default dbWatch database name, and change them to dbwatch_cc. This is a cleanup and consistency fix to align older job definitions with the current default database naming standard.
Updated Wait Statistics job to remove history records with period value 0. Created a new version of the Wait Statistics job to clean up old history records where the period value is 0, as these can cause report generation errors such as division by zero. The procedure is also updated to prevent new records with period value 0 from being created.
Improved Blocking Statistics job for MS SQL Server to avoid timeout. Updated the Blocking Statistics job for MS SQL Server to prevent timeout when there are several hundred blocked sessions. Instead of continuing to analyze all sessions, the job should stop after analyzing 50 sessions or after 20 seconds, whichever comes first.
Flush instances with missing version or platform_info. Sometimes an instance is missing some fdl properties, typically platform_info and version. Detect if this happens, and flush the instance.
Enhanced Database Disk Capacity job with default threshold percentages and automatic configuration of new disks. Update the SQL Server Database Disk Capacity job to add two new parameters: default warning percentage and default alarm percentage. These parameters should be used to automatically configure the existing threshold parameters warning threshold (percent), warning threshold (MB), alarm threshold (percent), and alarm threshold (MB). The job should also be improved to detect disks that are added after the job has been installed and automatically configure threshold values for those disks based on the new default percentage parameters, removing the need for manual updates to the existing per-disk threshold parameters.
Reduced the number of in-memory events. The number of in-memory events can grow rather large, cap them at f.ex 1000 pr instance.
Improved debug info in Connectivity dialog.
Added a new internal graph for dbWatch Server memory usage. Create a new internal graph that shows memory usage for dbWatch Servers, making it easier to monitor server resource consumption over time.
Added highlighting in charts when selecting a category. If a line chart has a lot of categories, they are almost impossible to tell apart. Added highlighting of the selected category.
Job template editor should not allow editing of bundled templates. Today the editor allows you to change a bundled template, and then fails when trying to save (with a general save failed message).
The reported memory usage gives a jigsaw pattern of memory increases and then down again after garbage collection.
Configurable idle thread timeout. Currently there is a hardcoded 60 second threshold for when idle threads are killed. This is now configurable.
Monitoring Gap detection properties. Introduced new properties that identify and expose monitoring gaps in historical data collection. The purpose is to detect periods where no monitoring data has been collected for an extended period of time, indicating potential issues with job execution.
Update commons-lang3. Detected vulnerabilities CVE-2025-48924 in org.apache.commons:commons-lang3:3.17.0.
Updated log4j to 2.25.3 or later.
Upgraded jgit to version newer than 7.2.0×.
修复
Fixed SQL Server default database check job logic. Corrected “Logins default database check” job so the installed procedure now matches the documented behavior. The job now performs two separate checks: it verifies that only sysadmin logins are required to use master as default database, and it validates that login default databases both exist and are ONLINE. The fix also activates the return status for default db parameter and keeps the upgrade procedure in sync with the create procedure.
Fixed missing Tablespaces and Datafiles in Management. In dbWatch Monitor, in the Management section, Oracle instances version 11 and earlier (including 10 and 9) did not display information under “Storage” for Tablespaces and Datafiles.
SQL Performance (Oracle): Scroll bar overlap. In the SQL Performance package (Oracle), when opening “Show statistics”, the SQL statement statistics information is partially obscured by a scroll bar. This affects visibility of the content for all SQL statements and reduces usability of the view.
Connecting to mongodb with forced tls. Mongodb connections with forced tls does not work.
PostgreSQL instance setup: Login name resets when changing group selection. When adding a new PostgreSQL instance in dbWatch, after a successful connection, the user is prompted to select a database and create a new login. The GUI suggests a login name in the format `dbwatch_cc`, or `dbwatch_ccX` if the default already exists. However, if the user changes the group selection (top-level dropdown in the GUI), the suggested login name is reset to `dbwatch_cc`, regardless of the previously suggested or entered value. If the user does not notice this change and proceeds, and a `dbwatch_cc` login already exists, the installation will fail. Change to Test group … Database and Login values change.
Report Editor: Custom logo/icons not shown in preview. In dbWatch Report Editor, logos/icons used in the report are no longer displayed in the preview window. The selected logo/image is still included in the generated report, but only when using PDF format. When HTML format is selected, the default dbWatch logo is used instead, even if a different logo has been configured. This behavior has never worked correctly in Control Center as far as we can recall, but it did work in dbWatch 12.
NamedValues.remove( does not always work, causing a recursive loop when doing a reanchor when the reanchor types all ready exist in the NamedValues.
Fixed bug in OrderedResult.compare method.
h0 appears as a category in live multiserver fdl graphs.
Missing audit trail for set worksheet/management authentication. There is no audit entry if a user changes his/her authentication in management or worksheet.
Opening a Chat with no entries is stuck at “Loading”. When clicking on a chat with no entries the dialog view is stuck at “Loading”.
Missing domain info in Monitor title. Sometimes the domain information is missing from the Monitor title.
Uploading a new license gives incorrect warning. When uploading a new license, we sometimes see a incorrect warning claiming that the new license is not compatible with the current license usage.
Server host resolves to 127.0.0.1. The fdl server/host (sometimes) resolves to 127.0.0.1.
Adding a user with backslash breaks the users.json file. Adding usernames with json special characters (and perhaps xml) breaks the config files.
Corrupted domain/<domain>/nodes.json after setting Server Display name using json escape characters.
Getting task metadata through fdl never ends. Task metadata resolving never sends a ChannelEnd.
Resetting password by editing config files does not rehash password. When changing the password by editing the authentication.xml file the password is not rehashed.
Find default JDBC driver does not work. The “Find default” button under JDBC driver in instance configuration does not work.
Using nested properties from an sql query is not robust.
Bug in resolving of task maxversion. Maxversion of tasks always uses the task in local (if any).
Resolved issues with metadata / metadata dictionary. Creating new entries in the metadata dictionary and then applying that metadata to instances is buggy. Values are not always applied.
Audit Analyzer view has problems with multiserver mixed old/new audit. Audit Search never completes when mixed old and new audit.
Missing refresh when changing template selection in Manage Jobs.
dbWatch Control Center 26.1.031主版本2026年3月20日
功能
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.
修复
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.