Timer Jobs Not Running After Database Migration

I recently migrated a Content database from one SQL Seerver to another, but I did not migrate the other databases (Config, etc). I don't know whether this was a bad decision, but in my understanding the Content database should be able to live anywhere.

After the migration, everything appeared to work correctly, until I noticed that Timer Jobs do not run (those that relate to the Web Application that contained the content database that had been migrated). To do the migration, I backed up the site collection in question, dropped the original content database, created a new content database on the new server, and then restored the site collection to the new content database.

I need to know what to invertigate or check. 

The first solution that others discuss is the clearing of the cache for running of timer jobs. This can be done by clearing the .xml files from the C:\ProgramData\Microsoft\SharePoint\Config\<some GUID> folder. These get re-created.

This did not help. The next suggestion was that the GUID in the <some GUID> folder referred to above (this being the Farm GUID) was not correct for the Farm, and one simply needed to create a folder that did reflect the farm GUID.  My folder name was correct, so it does not apply to me.

So, if no Timer Jobs are running against the relevant web application, what could have been done wrong, or what must I check?