Duplicate Search Databases in SharePoint Foundation 2013 Farm

Question

I seem to have 2 seperate issues with Search within my SharePoint Foundation 2013 Farm. This is a new Farm, so I can remove the search service application and re-create if this is a way that can clear the 2 issues I am experiencing.
Issue 1:
For some reason I have 2 instances of the following search related DB's:
SearchAdminDatabase
SearchAnalyticsReportingDatabase
SearchGathererDatabase
SearchLinksDatabase
1 instance of each of the databases all report database status of "No Action Required" and the other instance of all the DB's report a database status of "Not Responding".
Issue 2:
My search service application seems to be working fine as I am able to crawl content and retrieve results, however the DB's associted with this search service application are reported with the following warning within the SharePoint Health Analyzer. I have
been unable to run the Upgrade-SPContentDatabase command against these databases as I get a message saying that the content database could not be found:
Title
Databases running in compatibility range, upgrade recommended.
Severity
2 - Warning
Category
Configuration
Explanation
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
Search_Service_Application_AnalyticsReportingStoreDB_a3c64b2f3b9b4a5d83383ec0b1ecfcf4,
Search_Service_Application_CrawlStoreDB_ffb8d716450242cc849a7f44f521bfc9,
Search_Service_Application_DB_0fe433c02db6435db85285e9fd83863e,
Search_Service_Application_LinksStoreDB_75efb2f689cf49f19c98a5a8155e47b7.
Remedy
To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases.  For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
Kevin Evans

Answer 1

At time people create search service application and delete it. SA is deleted but database were not deleted for some reason. so these might be those stale database. You can delete them if you want
http://blogs.technet.com/b/tothesharepoint/archive/2011/12/19/find-active-databases-used-by-sharepoint-server-2010.aspx
If you want a report of all of your SharePoint databases that includes the GUIDs and related property values, use the SharePoint 2010 Management Shell.
There are several Windows PowerShell cmdlets you can use to find all of the SharePoint databases and then print this report to a text file. The quickest and perhaps easiest cmdlet is “Get-SPDatabase”. Run this cmdlet in the SharePoint
2010 Management Shell to list all of the SharePoint Server databases with properties for each one. From this potentially large list you can then obtain specific information such as the database ID by using additional syntax in your cmdlet. Similarly, also
in the SharePoint 2010 Management Shell, run “Get-SPDatabase | Sort-Object
disksizerequired -desc | Format-Table Name” and you will get a simple list of the names for each database. You can then print this list to a text file by adding, “| out-file c:\db.txt” to the end of the command. 
For detailed information, see
Windows PowerShell for SharePoint Server 2010,
Database cmdlets, 
Get-SPDatabase, and
Get-SPContentDatabase.
If this helped you resolve your issue, please mark it Answered