In this article...
Why are no queries found in the 'DB Queries' tab under the BT Dashboard?
Check to see if all these requirements are met:
- Do you have a license to monitor databases? See Database Visibility for details.
- Does the business transaction contain at least one relational database backend, that can be monitored with AppDynamics Database Visibility? See the list of supported database environments in Database Visibility Supported Environments.
- Is at least one backend in the business transaction linked to a monitored database collector? You can find information on how to link a backend with a database collector in Monitor Databases.
- Is at least one of the nodes making calls to the relational database backend Java, PHP, or .NET?
- For correlating queries executed by PHP or .NET, the controller version needs to be 4.5.4+. However, for Java, the controller version needs to be 4.5+.
- Is the database agent monitoring the database collector (linked to the backend in the business transaction) version 4.5+?
- Do you have permissions to view at least the database collectors linked to the backends in the business transaction?
Back to Contents
Further troubleshooting the DB Queries tab
Are you still unable to see queries under the ‘DB Queries’ tab after confirming the above requirements? Check these possible reasons:
ISSUE
|
CAUSE / SCENARIO
|
Query texts aren’t sampled by the (Java, PHP, or .NET) app agent
|
Fast-running queries
|
Query texts aren’t sampled by the DB agent
|
Fast-running queries
|
The query text given by the database doesn’t match the query text executed by the (Java, PHP, or .NET) app agent
|
Special cases, like stored procedure calls
|
Back to Contents
In what order are queries in the ‘Transaction Snapshot Viewer’ fetched?
The order in which queries in the ‘Transaction Snapshot Viewer’ are fetched depends on the type of database—Oracle, or other.
'Transaction Snapshot Viewer' query order with Oracle databases
In Oracle databases with both 'Oracle-specific correlation' and 'Generic Snapshot Correlation' enabled, you may see the following, consecutively:
- Oracle specific snapshot correlation (Pre-4.5 Java → Oracle correlation) - No bottom message in the UI.
If fetching by this method (#1) returns an empty list, then the next fallback is:
- Generic snapshot correlation - Bottom message: "For security reasons, app agents capture only the query groups. Therefore, some of the queries listed are not executed by this snapshot."
If fetching by this method (#2) returns an empty list, then the next/final fallback is:
- Time-based correlation - Bottom message: "Database agent couldn't capture any data related to this snapshot. You are now seeing data captured a minute before and after the snapshot was captured."
Back to Contents
'Transaction Snapshot Viewer' query order with non-Oracle databases?
For other relational database types, including Oracle databases with the Oracle-specific correlation disabled, you may see:
- Generic snapshot correlation - Bottom message: "For security reasons, app agents capture only the query groups. Therefore, some of the queries listed are not executed by this snapshot."
If fetching by method #1 (above) returns an empty list, then the fallback is:
- Time-based correlation - Bottom message: "Database agent couldn't capture any data related to this snapshot. You are now seeing data captured a minute before and after the snapshot was captured."
Back to Contents