@Watch Teller Strange... as the code is only being called upon by tracking and shouldn't even be included if tracking is disabled. Hmm.. will have a look, but that's another issue altogether.
For now, let's just bite our time till the next release which should fix the issue. In the mean, if you like, you can change the line I changed in the pull request in your install. That should definitely get rid of the error.
@ebuzztoday glad to hear it's gone, but a server reboot should not be able to fix this. Or are you not using database table prefixes ?