Adam,

 

I'm getting exactly the same error as described above.

Is there any fix or workaround available for this. It was reported nearly 2 years ago but I didn't see any follow-up mail.

It is causing performance issues for us.

 

I will dearly appreciate a response of any sort on this.

 

cheers