This page has frequently asked questions to aid in troubleshooting and collecting the necessary data for support.
Frequently asked questions
Database Agent connection status displays in the Databases dashboard, which shows all named database agents for the server. Make sure to select the Status description column to display if it does not initially display.
And as with other Agents, database status also displays in the Agents Overview dashlet. Make sure to check if it is connected and its license status.
In case of issue, make sure to check the status of the Collector hosting the Agent as well the connection to the database. (Settings menu > Dynatrace Server > Databases).
The permissions needed for the Database Agent and the respective SQL statements are listed in Database Agent Configuration > Permissions.
After configuring the Agent, click Test Connection. The following error appears if the configured user doesn't have the needed permissions:
Databases monitoring data are mapped into System Profiles dynamically if a database tier is detected in a PurePath and a DB Agent is connected to that same database.
The dynamically mapping can be checked in the Agent Overview of a specific system profile:
It is disabled if:
- No Database Agent has been configured for that particular database or it is currently not connected.
- The Database Agent has not been automatically detected for that System Profile - see below How does the mapping with the System Profile work?.
- The database call is a stored procedure, which is currently not supported.
They are stored with the log files of the Collector on which the Database Agent has been configured. Search for DBAgent.
No, not currently.
There is currently limited support for RAC. You can either connect each of the RAC nodes separately to have a real visibility into the cluster OR connect the cluster as one single DB instance. However in that case the Database Agent only monitors the connected node.
Oracle/MS SQL Server: a license is consumed for each DB instance, per 8 CPU cores.
MySQL: a single license is consumed by each DB agent, irrelevant of the CPU count. DB2: a license is consumed by each DB agent, per 8 CPU cores.
See also Licensing Details.
Retrieve the CPU cores for Oracle by querying the v$parameter view:
SELECT value FROM v$parameter WHERE name LIKE 'cpu_count'
Retrieve the CPU cores for SQL Server by querying the system view dm_os_sys_info:
SELECT cpu_count FROM sys.dm_os_sys_info
MySQL: a license is consumed for each DB instance - no limitation on the number of CPU cores.
Aurora: a license is consumed for each DB instance - no limitation on the number of CPU cores.
Yes, the Database Agent doesn't require any specific edition. All Database Agent features are available with all editions.
Yes, since AppMon 6.5.
Invoke the following to create explain tables in the SYSTOOLS schema:
CALL SYSPROC.SYSINSTALLOBJECTS('EXPLAIN', 'C', CAST (NULL AS VARCHAR(128)), CAST (NULL AS VARCHAR(128)))
DB2 explain facility works by populating explain tables. These are not created by default. IBM documentation
Alternatively the database agent DB2 user may not have all required permissions:
grant all on SYSTOOLS.EXPLAIN_ACTUALS to <dtagent> grant all on SYSTOOLS.EXPLAIN_ARGUMENT to <dtagent> grant all on SYSTOOLS.EXPLAIN_DIAGNOSTIC to <dtagent> grant all on SYSTOOLS.EXPLAIN_DIAGNOSTIC_DATA to <dtagent> grant all on SYSTOOLS.EXPLAIN_INSTANCE to <dtagent> grant all on SYSTOOLS.EXPLAIN_OBJECT to <dtagent> grant all on SYSTOOLS.EXPLAIN_OPERATOR to <dtagent> grant all on SYSTOOLS.EXPLAIN_PREDICATE to <dtagent> grant all on SYSTOOLS.EXPLAIN_STATEMENT to <dtagent> grant all on SYSTOOLS.EXPLAIN_STREAM to <dtagent>
For performance reasons SQL gathered by agents is truncated to 512 characters. This can be modified by editing agent sensor properties for database category sensors such as JDBC, ADO.NET, and PHP.
See SQL execution plan limitations section for more information.
If you need further assistance, go to our support page and make sure to provide a session export and a support archive.