D Troubleshooting OracleAS Integration InterConnect

This appendix describes common problems that you might encounter when using OracleAS Integration InterConnect and explains how to solve them. It also gives detailed instructions on how to diagnose OracleAS Integration InterConnect problems. It contains the following topics:

Problems and Solutions
Need More Help?

D.1 Problems and Solutions

This section describes common problems and solutions. It contains the following topics:

iStudio Fails to Connect
Mappings in iStudio
Metadata Not Editable in iStudio
Subscribing Adapter Does Not Receive Messages From the Hub
Messages Are Not Getting Delivered to a Spoke Application
OracleAS Integration InterConnect Repository Does Not Start
DB Adapter Does Not Pick Up Messages That Have Been Published From the Database
FTP Adapter Cannot Match Incoming Message With Any D3L Definiton
AQ Adapter Does Not Pick Up Mesage From the Spoke AQ
CBR Issue with DB Adapter

D.1.1 iStudio Fails to Connect

iStudio is not connecting to the repository. For example, a message pops up saying "Failed to connect to the repository".

Problem 1

Incorrect hub database parameters entered in the Hub Information dialog.

Solution 1

iStudio uses the user name, password, and connect string entered in the 'Hub Information' dialog to establish a connection with the respository. Ensure that you have provided the correct hub database parameters, <hostname>:<tns_listener_port>:<db_sid>, for connecting to the Infrastructure Database. For example, myhost.us.mycompany.com:1521:orcl.

D.1.2 Mappings in iStudio

I have changed the mapping, but the adapter(s) still seem to use the old information.

Problem 1

Metadata is not refreshed.

Solution 1

In the File menu, select Sync Adapters. This pushes the updated metadata to the adapters.

Solution 2

Alternatively, you could perform the following steps to change the behavior after transformation:

Stop the adapters.
In the adapter.ini file, set the value of the parameter agent_delete_file_cache_at_startup to True, to delete all cached metadata at startup.

This parameter specifies whether to delete the cached metadata during startup. If any of the agent caching methods such as metadata caching, DVM table caching, or lookup table caching is enabled, then metadata from the repository is cached locally on the file system. However, if you change some metadata or DVM table using iStudio and you want the Adapter to use those changes the next time it is started, then you can either delete the cache files or set this parameter to true before restarting.
Restart the adapters.

D.1.3 Metadata Not Editable in iStudio

The metadata is not editable in iStudio as the "Edit" option is greyed out.

Problem 1

The metadata in the repository might belong to a different metadata owner than the one specified in the $ORACLE_HOME/integration/<version>/repository/repository.ini file.

Solution 1

Ensure that the "owner" of the data is same in both repositories. Data types have an owner, usually, that is "OAI". But you can change it in the repository.ini file. Only data that is owned by the local repository owner may be edited.

The metadata owner information is stored along with the objects at the time of their creation. If the repository owner name does not match the creation time owner name, then you will notice that the edit buttons are greyed out. You will need to edit the repository.ini file to change the owner name to the one used during creation and restart the repository. You will also need to reestablish the iStudio connection to the repository.

D.1.4 Subscribing Adapter Does Not Receive Messages From the Hub

The subscribing adapter is not able to pickup any message from the hub queue (oai_hub_queue). The messages are queued up in the hub queue but aren't subscribed by the subscribing adapter.

Problem 1

The value for the application, agent_subscriber_name, and agent_message_selector parameter in the $ORACLE_HOME/integration/<version>/adapters/<adapter_name>/adapter.ini file doesn't match the application name in iStudio.

Solution 1

Ensure that the value for the application, agent_subscriber_name, and agent_message_selector parameter in the $ORACLE_HOME/integration/<version>/adapters/<adapter_name>/adapter.ini file match the application name in iStudio.

Problem 2

Hub Queue name of the application may be longer than 20 characters.

Solution 2

Apply patch 2659228.

D.1.5 Messages Are Not Getting Delivered to a Spoke Application

If an adapter successfully received a message from the hub, but encounters a problem while transforming the message or delivering the message to the spoke application, then it will try to reprocess/resend the message in a certain interval until the problem has been resolved and the message has been successfully delivered. In most cases, this unfortunately means that all other pending messages that need to be processed to the spoke application won't get delivered until this one message has cleared out of the system.

Problem

OracleAS Integration InterConnect guarantees in-order-delivery of messages, meaning that if an adapter encounters a problem while processing a message, it will try to re-send the message until the problem has been resolved and the message can be delivered successfully. All other pending messages can't get delivered as this would change the order of delivery.

Solution 1

Refer to the error message and the oailog.txt file in $ORACLE_HOME/integration/<version>/adapters/<adapter_name>/logs/ directory, to resolve the error message.

Solution 2

Use the $ORACLE_HOME/integration/<version>/adapters/<adapter_name>/ignoreErrors script to drop the problem message out of the system. The ignoreErrors script will reconfigure the adapter, so that it ignores a specific error code. The adapter will then drop all messages that fail with that specific error code rather than trying to resend them, which ensures that other pending messages can be processed.

D.1.6 OracleAS Integration InterConnect Repository Does Not Start

The OracleAS Integration InterConnect repository does not start properly and there are java excpetions in the $ORACLE_HOME/integration/<version>/repository/reposlog.txt file. For example, "Could not register with the hub database. Please check your hub database parameters." Error message: "Retrying in 10 sec.java.sql.SQLException: Io exception: The Network Adapter could not establish the connection".

Problem 1

The information in the $ORACLE_HOME/integration/<version>/hub/hub.ini file is not valid.

Solution 1

Provide the correct information in the $ORACLE_HOME/integration/<version>/hub/hub.ini file.

[Database]hub_username=ichub

encrypted_hub_password=<encrypted_password> use $ORACLE_HOME/integration/<version>/bin/encrypt for encryptionhub_host=<hub_host_name>

hub_instance=<database_sid>

hub_port=<tns_listsner_port>

hub_use_thin_jdbc=true

[Repository Info]repository_name=InterConnectRepository1012

Problem 2

The hub schema does not exist on the hub database.

Solution 2

Run the $ORACLE_HOME/integration/<version>/repository/hubschema script to create the hub schema.

D.1.7 DB Adapter Does Not Pick Up Messages That Have Been Published From the Database

The database adapter does not pick up messages that have been published from the database, even though the publshing PL/SQL procedure was performed successfully and the message object record exists in the MESSAGEOBJECT table.

Problem

You might have published the message for the wrong application. The value provided for srcAppName+partition id parameter in the publishing PL/SQL procedure pub_<event/procedure_name>_<metadata_owner>_<version> does not match the application parameter value in the $ORACLE_HOME/integration/<version>/adapters/<adapter_name>/adapter.ini file.

Solution

Ensure that the value provided for the srcAppName+partition id parameter matches the value of the application parameter in the $ORACLE_HOME/integration/<version>/adapters/<adapter_name>/adapter.ini file.

D.1.8 FTP Adapter Cannot Match Incoming Message With Any D3L Definiton

The FTP adapter throws an error message that it cannot match the incoming message with any of the D3L defintions, and drops the message.

Problem 1

The ota.d3ls parameter is either empty or points to the wrong D3L file(s).

Solution 1

Provide a valid D3L file for ota.d3ls (or list of D3L files).

Problem 2

The D3L header does not contain the correct information for OracleAS Integration InterConnect event mapping.

Solution 2

Ensure that the

name tag in the D3L header matched the BusinessObject event name in iStudio.
Object Name field in the Define application View window of the Publish/Subscribe/Invoke/Implement wizard is not empty.
object tag matches the value of the Object Name field in the Define application View window of the Publish/Subscribe/Invoke/Implement wizard.

D.1.9 AQ Adapter Does Not Pick Up Mesage From the Spoke AQ

The AQ adapter does not pick up message that have been enqueued to a spoke AQ.

Problem 1

You have not provided the name of the spoke queue in the Deploy Tab in iStudio for this integration point.

Solution 1

Provide the name of the spoke queue. The AQ adapter log file should contain a line "<timestamp>: AQ Adapter: created a reader for queue <queue_name>".

Problem 2

The spoke queue might be a multiconsumer queue (JMS Topic) and you might connect to it with an incorrect consumer name.

Solution 2

Ensure that the aq_bridge_consumer_name parameter in the $ORACLE_HOME/integration/<version>/adapters/<adapter_name>/adapter.ini file is correct and matches the name of the consumer that the message was enqueued for.

D.1.10 CBR Issue with DB Adapter

I created an event with the name ProdRelease. The root element name is BatchProdRelease. When I restart the adapter, it displays the following error:

"An exception occured while evaluating the CBR expression: (ProdRelease_CO:OAI_META/V1.BatchProdRelease_CO:OAI_META/V1.Header.PlantCode == "GFL"). Following is a detailed message. oracle.oai.agent.common.AgentRuntimeException: Specified attribute (BatchProdRelease_CO:OAI_META/V1) does not exist in Data Type (ProdRelease_CO:OAI_META/V1)."

Problem

The root element name is a substring of the event name.

Solution

Ensure that the root element name does not have a substring of the event name. The root element name in this situation is BatchProdRelease and the event name is ProdRelease. This causes the adapter to fail. A workaround for this is to change either the root element name or event name.

D.2 Need More Help?

You can find more solutions on Oracle MetaLink, http://metalink.oracle.com. If you do not find a solution for your problem, log a service request.