Thank you for the reply, Kristian. Dan also replied to my email with an
explanation of what was happening to cause this error (thanks, Dan!)--maybe he
answered your questions in the process?
In my case, the failing statement was a trigger. My guess is that the
trigger was compiled against the old code (happened to be 10.2, but
could be anything before r496645 I think), and when it is "retrieved"
and executed the constructor it is calling no longer exist (signature
has changed).
Based on Dan's description of the problem I would think that a 10.2 trigger
should still succeed with the latest trunk (because there is a version
difference and thus the trigger's SPS should get recompiled)--unless I'm
misunderstanding something there? Are you sure the trigger that is failing was
a 10.2 trigger and not a 10.3 (pre svn #496645) one?
And, does the "describe" command also use a trigger/SPS/something such
that my error scenario can be said to be the same as Army's problem?
As Dan mentioned the "describe" command uses a metadata query which in turn has
a stored compiled plan. So yes, I think your scenario is probably similar to
the one I was seeing.
Thanks again to you and Dan for your replies!
Army
