Failed database requests can sometimes cause a database instance to appear twice.
Issue
A single instance of a Microsoft SQL or DB2 database is displayed as two separate database members in the Application View, once with the database name in the form of host:port/schema, and once with as a hash value.
Probable cause
Within a selected five-minute period, a Microsoft SQL or DB2 database instance receives some requests that successfully connect to the database and some requests which fail to connect to the database. When a request cannot connect to the database, the database name appears as a hash value. If the five-minute period comprises requests that successfully connect and requests that fail to connect, the database appears as two separate members.
Failed requests might be caused by a user error (such as database credentials), an offline database, or other reasons.
Resolution
Check the connection to the database:
- Confirm that requests have the required database credentials.
- Confirm that the database is online.
To show the database connection string in the Application View
The hash value is a security measure to prevent accidentally revealing sensitive information that might be displayed in the database connection string. As a troubleshooting measure, you can change the hash value to show the database connection string, which might help you find the source of the problem.
In the agent policy, change the display.db.connection.string.unrecognized.format property to true.
Related topics
Analyzing database problems with the Database tier
Modifying an App Visibility agent policy
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks