Splunk AppDynamics can sometimes reveal unexpected connections from an application to a database on the flow map. If this occurs for you, try the following to determine why this database appears:

• From the left navigation menu, select Applications > <application-name> > Database Calls. Then, view a call and select the Slowest Database Calls tab, and drill down into the snapshots to see the code that is calling the database. See To troubleshoot slow database and remote service calls.
• Run a diagnostic session to capture some transaction snapshots and look for calls to the database. See Diagnostic Sessions and Transaction Snapshots. If you have integrated Splunk AppDynamics for Databases, you can select a transaction snapshot that involves running SQL on an Oracle database and from the Transaction Flow Map you can link to AppDynamics for Database to see all queries executed in the SQL session that are associated with that transaction snapshot.
• Are any exceptions thrown when the database is seen? If so, look for error snapshots that point to the exception trace.