I got this DBALException on a quiet harmless query. Tracking this down a bit, lead me to a bad implementation with a poorly implemented workaround.
The issue is most probalby caused by a count query with 2 order statements, follwed by a select query (without count) and only 1 order statement.
In short, the problem is, that the sortClauseConverter is singleton and not properly rested between different queries. In the SortClauseConverter class there is a hint, where the bug comes from and a workaround, reseting the converter, after calling applyOrderBy(). But in count this method is never called and the SortClauseConverter is never reseted.
I suggest implementing a reset() method on the SortClauseConverter and call it from DoctrineDatabase before each Operation.