Latest Oracle Data Provider for .NET (11.2.0.3.20) breaks EF Update Wizard

Question

I have VS2012 and the latest 32-bit version of ODAC (Release 5 with Oracle Developer Tools) installed on a Win7 box. Everything is a clean install. In this environment, I ha

Answer 1

This workaround found in the Oracle forums helped me. (See the post on Dec 19 by user9948241.) Oracle has a new forums page, and the post referred to above apparently didn't make it into the new forums.

Apparently, in VS2012 with the latest ODAC, when you set up connection filter criteria you always have to include the default schema along with whatever schema you want.

UPDATE: Shown below is the Filters tab in the wizard for adding (or modifying) a Data Connection from the Visual Studio Server Explorer.

Look carefully and note that in the Value field of the 'Select the filter criteria,' I have two schema values (the actual values are erased from the screenshot) separated by a comma. One is the default schema value, and the other is the schema that I want. You can set these schema values by clicking the ellipsis that I have marked in red.

For some reason, I didn't have to do all that in VS2010 with previous version of ODAC, I removed the default schema and just added the schema I wanted.