This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. In Microsoft BizTalk Server 2006 R2, you run a stored procedure through the Oracle Adapter. You use a user account that does not own the schema. In this scenario, the Oracle Adapter fails. Additionally, an Error event that resembles the following is logged in the Application log:
Event Type: Error Event Source: BizTalk Server 2006 Event Category: BizTalk Server 2006 Event ID: 5754 Description: A message sent to adapter "WCF-Custom" on send port Error details: Microsoft.ServiceModel.Channels.Common.TargetSystemException: ORA-06550: line 1, column 7: PLS-00201: identifier 'TESTER.GET_IB_DETAILS_SIMPLE' must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignored ---> Oracle.DataAccess.Client.OracleException ORA-06550: line 1, column 7: PLS-00201: identifier 'TESTER.GET_IB_DETAILS_SIMPLE' must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignored at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure) at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src) at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery() at Microsoft.Adapters.OracleDB.OracleDBXmlParser.ExecuteSingleCommand(OracleCommand command, Boolean recordPresent, Boolean accumateRowAffected) at Microsoft.Adapters.OracleDB.OracleDBXmlParser.ExecutePackProcFunc(AdapterDataTable parsedMessage)
Note This problem can also occur in non-BizTalk Server scenarios.
This problem occurs because the Oracle Adapter does not append the schema name in the package or in the stored procedure name.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
You must have Microsoft BizTalk Adapter Pack 1.0 installed before you apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
BizTalk Server 2006 R2, 32-bit versions
BizTalk Server 2006 R2, 64-bit versions
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you install this hotfix, you can call a stored procedure by using an account that does not own the schema. However, if the stored procedure uses Record types, these types must be defined in the same schema as the stored procedure. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates