Using ODP.NET To Call Oracle Apps Stored Procedures Results In Unexpected Behavior On Second Call
Last updated on JULY 05, 2017
Applies to:Oracle Data Provider for .NET - Version 188.8.131.52 and later
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
***Checked for relevance on 31-May-2013***
You have an Oracle Applications environment (for example, 184.108.40.206) and you want to call a stored procedure that interacts with this environment.
When calling the stored procedure from SQL*Plus it works each time you call it.
When calling the same stored procedure from a .NET application using the Oracle Data Provider for .NET (ODP.NET) it works the first time and fails on all subsequent calls.
The stored procedure you are calling may be making a call to FND_GLOBAL.APPS_INITIALIZE().
This behavior may have always existed, or you may have applied an Oracle Applications patch (for example, ATG.RUP5) that has caused the change in behavior.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms