Error 2019: Member Mapping specified is not valid.

931245

Reference also these threads:

2310263

2333405

2267041

2322642

2339188




I wont elaborate too much since the problem seems to be well known:


Error 2019: Member Mapping specified is not valid. The type 'Edm.Int16[Nullable=False,DefaultValue=]'

Could not find schema information for the element 'oracle.dataaccess.client'.

Oracle.DataAccess.Client version 4.112.3.0

oracle.dataaccess.client section exists in both client and service apps and is ignored in both client and service apps


Please provide an answer my app builds but crashes when accessing data. Please provide a resolution to this thank you.

Edited by: 928242 on May 31, 2012 10:08 AM

Edited by: 928242 on May 31, 2012 4:20 PM

Alex Keh-Oracle

It would be helpful to see the ODP.NET section of your .NET config file.

931245

<oracle.dataaccess.client>
<settings>
<add name="bool" value="edmmapping number(1,0)" />
<add name="STP_OWN.LOOKUP_ACCOUNT.RefCursor.results" value="implicitRefCursor bindinfo='mode=Output'" />
<add name="STP_OWN.LOOKUP_ACCOUNT.RefCursorMetaData.results.Column.0" value="implicitRefCursor metadata='ColumnName=ACCT_NO;DataType=System.Int64;ProviderType=Int64;NativeDataType=Number;NumericPrecision=9;NumericScale=0'" />
<add name="STP_OWN.LOOKUP_ACCOUNT.RefCursorMetaData.results.Column.1" value="implicitRefCursor metadata='ColumnName=ACCT_NAME;ProviderType=Varchar2;NativeDataType=Varchar2'" />
<add name="STP_OWN.LOOKUP_CUSIP.RefCursor.results" value="implicitRefCursor bindinfo='mode=Output'" />
<add name="STP_OWN.LOOKUP_CUSIP.RefCursorMetaData.results.Column.0" value="implicitRefCursor metadata='ColumnName=CUSIP;ProviderType=Varchar2;NativeDataType=Varchar2'" />
<add name="STP_OWN.LOOKUP_CUSIP.RefCursorMetaData.results.Column.1" value="implicitRefCursor metadata='ColumnName=PIMCO_DESC;ProviderType=Varchar2;NativeDataType=Varchar2'" />
</settings>
</oracle.dataaccess.client>

931245

Thank you, Oracle, for your very public display of your commitment to excellence.
Thank you for demonstrating your willingness and ability to respond to the needs of your cash-paying customers.
You guys are the best!

Alex Keh-Oracle

No problem! Glad to help.

Your config file appears to be formatted correctly. I don't see any obvious problems with it.

The next most common reason for this type of error is the following:
--------------
When custom mapping in a configuration file has changed, re-generate the data model to solve compilation errors incurred by the new changes.

In some scenarios, custom mapping can cause compilation errors, when a project that uses custom mapping is loaded by Visual Studio. There are a few ways to resolve the compilation errors:

(a) Open Visual Studio Help/About Microsoft Visual Studio and click OK button to exit the dialog box or
(b) Open the to-be-used connection in Server Explorer

Then compile the project again to eliminate the compliation errors.

Once you have done the above and are still seeing custom type mapping related messages, use MKSNT touch.exe (or the like utility) on app.config to change its timestamp but leave its contents intact.

touch App.Config
This will force ODT/ODP to reread the custom type mapping.

934414

Hello,

you can edit the devenv.exe.config of Visual Studio to avoid this reoccurring error, see:
2310263
Then there should be no more need to call Help / About...