How can I learn Oracle EBS applications

Troubleshoot operational problems with the Oracle E-Business Suite adapter

  • 9 minutes to read

This section explains how to use troubleshooting techniques to eliminate expiration errors that may occur when using the Microsoft BizTalk Adapter for Oracle E-Business Suite.

Enable tracing

More information on tracing support in the E-Business Adapter for Oracle, diagnostic tracing and message logging in the Oracle E-Business Suite Adapter.

known problems

The following are the most common errors you may encounter when using the BizTalk Adapter Pack, as well as the likely cause and solution.

Error loading adapter bindings

problem

When you try to start the Add Adapter Service References plug-in for Visual Studio or the Adapter Processing Service Add-in for BizTalk Projects, you receive the following error message:

root cause

When you try to start the Add Adapter Service Referrals plug-in or Adapter Processing Service add-in, WCF, the adapter will load bindings for any installed adapters. In return, the adapter bindings are dependent on the specific client software for the enterprise application. You could experience this problem for one or both of the following reasons:

  • The required LOB client software is not installed on the computer on which you installed the adapter.

  • If you have a standard or full installation of the adapter that installs all of the adapters that are included in the BizTalk Adapter Pack. However, the LOB client libraries can only be installed for one enterprise application. Therefore, the graphical user interface will load the bindings for the other adapters.

    resolution

  • Make sure that the required versions of the LOB clients are installed on the computer on which you installed the BizTalk Adapter Pack. Information about the supported client versions can be found in the installation manual available at : \ Program Files \ Microsoft BizTalk Adapter Pack.

  • Make sure that you install the adapter only with the adapter you need to perform a custom installation.

The adapter for Oracle E-Business Suite does not appear in the list of adapters in the BizTalk Server Management Console.

problem

Unlike the earlier version of the adapters that shipped with BizTalk Server, E-Business Adapters for Oracle shipped with the BizTalk Adapter Pack is not shown in the list of adapters in the BizTalk Server Administration Console.

root cause

The latest version of the E-Business Adapter for Oracle is a custom WCF binding. Therefore, while the BizTalk Server Administration Console shows the WCF-Custom adapter, it does not show the custom WCF bindings, and therefore does not show the WCF-based E-Business Adapter for Oracle.

resolution

You can explicitly add the E-Business Adapter for Oracle to the BizTalk Server Administration Console by following the steps Adding the Oracle E-Business Suite Adapter to the BizTalk Server Administration Console.

Failed to perform operations for Oracle E-Business Suite

problem

The adapter presents the following error on any operation in the Oracle E-Business Suite with BizTalk Server.

  • For BizTalk Server

    root cause

    The WCF action for the message was not specified. WCF requires a SOAP action to be specified for each operation that informs the adapter about the operation to be performed on the LOB application.

    resolution

    Specify the SOAP action in the send port or a context property of the message in a BizTalk orchestration. For instructions, see Configure the SOAP Action for Oracle E-Business Suite. See Messages and Message Schemes for Oracle EBS Adapters to view a list of actions for each operation.

The BizTalk process may crash due to an incorrect version of the Oracle client when a request message is deleted to the receive location

problem

After a request message is deleted from a receive location defined in a BizTalk orchestration, the orchestration gets the message and the BizTalk Host (BTSNTSvc.exe) crashes and is restarted.

root cause

Installing the Oracle client adds the reference to the latest client assemblies in the PATH variable. Additionally, the references to the latest installation, the Oracle client assembly, are the references to the existing client assemblies. Therefore, the latest Oracle client installation is not a supported client version, BizTalk host crashes, and then restarted.

For example, suppose the supported Oracle client 11.1.0.7 is already installed on the computer and the PATH variable has the following reference:

If an unsupported Oracle client, e.g. B. 10.2.0.3, installed on the same computer, the PATH variable will have the following reference:

Note that the unsupported client version is referenced before the supported version, and therefore the BizTalk host crashes. If multiple BizTalk hosts are running, the host adapter crashes.

resolution

If more than one Oracle client is installed on the same computer, ensure that the supported version of the Oracle client is referenced in the PATH variable before the other Oracle client versions. For example, the supported version of the Oracle client is 11.1.0.7, the reference in the PATH variable must look like this:

The adapter can throw a stack overflow exception when an operation is performed.

problem

Using the adapter when trying to perform an operation on Oracle numeric data types in DataSets or weakly typed REF cursors may cause the adapter to throw an overflow exception.

root cause

This happens when you specify a high value for the type of Oracle numeric data in DataSets or weakly typed REF CURSORS that do not fit into the respective .NET type.

resolution

If you want to pass large values ​​for the type of Oracle numeric data in DataSets or weakly typed REF CURSORS, you must enable safe input by setting the value of the EnableSafeTyping binding property to "true". Enabling safe typing exposes the numeric data type from Oracle in DataSets or weakly typed REF CURSORS as strings.

The adapter can throw an arithmetic overflow exception for the execution of an "ExecuteScalar" operation.

problem

Using the adapter, if you try to execute a SELECT statement in an "ExecuteScalar" operation that gets a large number, the adapter will throw the following exception: "System.OverflowException: Arithmetic operation overflowed."

root cause

This happens because of the well-known ExecuteScalar process in ODP.NET. ODP.NET tries to fit in the data in the .NET Decimal data type, and the exception is thrown if the result is too large for in the .NET Decimal type.

resolution

Use TO_CHAR () on the SELECT statement in the ExecuteScalar operation to convert the returned data as a string.

Adapter client may throw the following exception on the execution of an operation: "Could not get user id, responsibility id, application id. Check that the correct values ​​were passed."

problem

The adapter clients can throw this exception when performing operations on Oracle E-Business Suite artifacts (interface tables, interface views, concurrent programs, and requirement sets).

root cause

This happens if you specify an incorrect combination of Oracle user name, password, and responsibility name when performing the operations on interface tables, interface views, concurrent programs, and requirement sets. The e-business adapter for Oracle required that these values ​​set the application context for these artifacts. For more information on setting application context, see Setting the Application Context.

resolution

Provide a correct combination of the Oracle username, and password responsible for setting the application context for an item for Oracle E-Business Suite accordingly. To provide values ​​for the Oracle username and password, you must use the OracleUserName and OraclePassword Binding properties. To specify the value for Oracle Responsibility, you can either use the OracleEBSResponsibilityName Binding the property or message context property.

RootNode TypeName failed in BizTalk projects

problem

In a BizTalk project in Visual Studio, when the schemas are generated from the Adapter Processing Service add-in contains invalid characters or reserved words for the RootNode TypeName Property will occur when compiling the project, the following error will occur:

resolution

  1. Right-click the Rood node referenced in the bug and choose properties.

  2. For the RootNode TypeName -Property, do not remove any illegal characters or reserved words, e.g. B. Period (.).

Invalid binding warning when using the adapter in Visual Studio

problem

When using the adapter to create an application in Visual Studio 2013 and opening the configuration file (app.config) generated by the adapter, a warning similar to the following is displayed:

root cause

This warning appears because the E-Business Adapter for Oracle binding is not included in a standard binding with the Windows Communication Foundation (WCF).

resolution

You can ignore this warning.

BizTalk Server throws an exception if you use more than one notification scheme in the same application or the notification scheme for multiple applications on the same host

problem

BizTalk Server throws an XLANG exception or an exception that states that the application cannot find the document specification because multiple schemas match the message type.

root cause

In this case, due to one of the following:

  • You have deployed multiple generated notification schemes in a BizTalk Server project in a BizTalk Server application, and then run the application to receive notifications from the Oracle database. Because the notification schemes are used, there is a conflict between the schemes that are provided in the BizTalk Server application.

  • For multiple projects, you have deployed a notification scheme for each of the BizTalk Server projects, have generated a separate BizTalk Server application on the same host for each project, and then run an application or applications to receive notifications from the Oracle database . Because the schemas and assemblies are accessible through the applications in BizTalk Server, there is a conflict between the general schemas that are deployed under different BizTalk Server applications and assemblies.

    resolution

    Use a single notification schema file for a BizTalk Server application. If you want to use the notification scheme in multiple BizTalk Server applications on the same host, create an application with a single notification scheme, and then use the notification scheme for all other applications in BizTalk Server.

Exception when browsing the Oracle E-Business Suite artifacts in Visual Studio

problem

When browsing the Oracle E-Business Suite artifacts in a Visual Studio project using the Add Adapter Metadata Wizard, Add Adapter Service Reference Plug-in, or Adapter Processing Service Add-in, a time-out exception might be thrown.

root cause

This can occur when the Oracle E-Business Suite host server is slow, is in a remote location, or the schema under searched has a large number of elements.

resolution

You can either increase the value SendTimeout Bind property, or enter a search term in the search in category Text box to reduce the number of elements the adapter gets.

For more information about specifying binding properties, see Configure the binding properties for Oracle E-Business Suite. For more information about how to find items in Oracle E-Business Suite, see Searching, Finding, and Retrieving Metadata for Oracle E-Business Suite Operations.

Memory usage and thread count increase when the adapter is used in a transactive inbound operation

problem

In the case of a transactive inbound process such as retrievals if there is no data, retrieved from the table and the adapter queries whether there has been an increase in memory usage and the number of threads over a period of time.

root cause

If there is no data, it is retrieved from the tableafter each cycle timeout received Windows Communication Foundation (WCF) creates a new thread to continue the polling process. Therefore, the thread count and memory usage increase over time. However, if the table is fetched that contains some data, all subsequent fetches continue to be in the same thread.

resolution

It is recommended to set the ReceiveTimeout the maximum possible value is 24.20: 31: 23.6470000 (24 days) so that a new thread is only created for 24 days. This ensures that the number of memory and thread counts does not grow too early.

More information about the ReceiveTimeout For the binding property, see About the BizTalk Adapter for Oracle E-Business Suite Binding Properties. For instructions on specifying the remote service binding properties, see Configure the binding properties for Oracle E-Business Suite.

Note

Using the adapter with BizTalk Server, setting the timeout to a high value will not affect the functionality of the adapter.

See also

Bugfix for the adapter for Oracle EBS