We're connecting to an IFS(IFS is an ERP system) oracle database using ODP.Net and entity framework, and calling stored procedures created by IFS. With the 11.2 version I'd be able to catch the exception and get some useful information from it like "Error ActiveSeparate.NOFINDATE for order....". After updating to 12c, every single exception that bubbles up from calling these stored procedures just say the text in the heading. I've debugged the code and tried to see if the other exception has been hidden inside the inner exception but no luck.
Going back to 11.2 is not an option since we've migrated the solution to Visual Studio 2013. Which unfortunately now seems like the only option.
Anyone have any clues to what might be wrong or what I can do to rectify this problem?