Thank you for your response, Rex! Of course now that I have a chance to revisit this issue this week (I was out of the office last week), it appears to have resolved itself. I did not know about the Clear Workspace Cache tool, but if it crops up again, I'll try that first.
To answer your questions:
- We do a Delete/Append via python script every night on most of our FCs in Published from Production.
- Both 10.3.1 geodatabases are on the same server.
- We did try it from another PC, each running differing versions of Windows (10 and 7) and had the same issue.
- No, the attribute query did not work in Published when that SQL statement was missing -- it failed.
I'll mark your comment as answered -- maybe it was a caching issue that cleared up after some time passed -- but reopen if it acts up again.