WebSphere Adapter for Oracle Business Applications

Troubleshooting the sample applications

If you should encounter problems while running the tasks for these samples, they could be related to either running the Adapter for JDBC or to interacting with the Oracle database. Information is available to help you troubleshoot either area.

For problems while running the Adapter for JDBC, refer to the "Troubleshooting" section in the WebSphere Adapters: Adapter for JDBC User Guide. It describes how to contact IBM Software Support, how to enable logging and tracing, and how to enable the Common Event Infrastructure.

See the topics listed below for possible problems while interacting with Oracle E-Business Suite.

  1. Objects take a long time to generate

    The time it takes to generate objects varies according to the computing power of the hardware system on which you are running the Oracle E-Business Suite.

  2. During Create operation, Objects not moved to base tables

    During a Create operation, after the adapter sets the values in the interface tables, an Oracle function call is made, using a stored procedure. The function call moves the data from the Oracle interface tables to the base tables. If a problem occurs when this function call is made, Oracle writes error codes into the column in the interface tables called INTERFACE_STATUS.

    If your customer object fails to appear in the application after the Create operation is run, but no errors are reported by the Adapter for JDBC, then you should query the INTERFACE_STATUS column in each interface table to see if any errors have been reported. These errors could be due to problems such as not setting required values, or using a reference number or customer name that is already in the Oracle application's base tables.
    Note: For more information on the error codes for this column, refer to your documentation for Oracle Applications 11.5.10.

    In a production environment, these errors could be detected in a number of ways. You could run a separate Adapter for JDBC instance to look for and report errors from these columns. Another option could be to create an Oracle workflow to check for errors and report them using the Oracle E-Business Suite reporting system.


Terms of use |

Last updated: Thu 12 Oct 2006 03:45:39

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)