title: Getting "ORA-XXX: Message XXX not found; product=RDBMS; facility=ORA" instead of the custom exception on ODAC 12c
body: <p>In my scenario I'm executing oracle store procedure from MS BizTalk orchestration via WCF-Custom adapter (oracleDBBinding).
  This procedure in negative scenario throwing custom exception (pl/sql RAISE_APPLICATION_ERROR).</p>
  
  <p>If BizTalk Send port is configure UseAmbientTransactions = False  (this mean that transaction is not elevated in to MSDTC) I'm getting</p>
  
  <blockquote>
    <p>A message sent to adapter "WCF-Custom" on send port "MySendPort" with URI "oracledb://myoracledb/" is suspended.
    Error details: Microsoft.ServiceModel.Channels.Common.TargetSystemException: ORA-20901: Deal: 26252741.0.0 has already been processed</p>
  </blockquote>
  
  <p>If BizTalk Send port is configure UseAmbientTransactions = True  (this mean that transaction elevated in to MSDTC) I'm getting</p>
  
  <blockquote>
    <p>A message sent to adapter "WCF-Custom" on send port "MySendPort" with URI "oracledb://myoracledb/" is suspended.
    Error details: Microsoft.ServiceModel.Channels.Common.TargetSystemException: ORA-20901: Message 20901 not found;  product=RDBMS; facility=ORA ---> Oracle.DataAccess.Client.OracleException: ORA-20901: MySendPort;  product=RDBMS; facility=ORA</p>
  </blockquote>
  
  <p>So as you may see when I enable ambient transaction on send port the exception message is lost. The error number is returned but message is substitute with string Message XXX not fount. This happens only when i'm dealing with custom exceptions raided on oracle side, exceptions like wrong username and password are retrieved correctly.</p>
  
  <p>I'm wondering if it's wrong configuration of oracle client + OracleMTSRecoveryService + MSDTC or it's a bug in oracle client</p>
  
  <p>To put this in context I'm migrating my solution from BizTalk 2009 on windows 2008 (physical box) to BizTalk 2013R2 on windows server 2012R2 (virtual box). On on old estate (BizTalk2009) propagation of errors works as expected with Ambient Transactions enabled. The issue which I'm experiencing is on new estate BizTalk 2013R2 where i have new OS new Oracle Client and new BizTalk version. So i guess that ether I missed something in configuration / permission or I'm dealing with a bug in Oracle Client / WCF Oracle Adapter</p>
  
  <p>My environment:
  Operating System: Windows 2012R2
  Oracle client: 12c (12.1.0) both versions 32 and 64 bit
  BizTalk version:         2013R2
  OracleMTSRecoveryService: Installed on 64 bit oracle client</p>