|Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for AIX Based Systems (64-Bit)
Part Number E14771-06
This chapter describes issues associated with Oracle Technology Adapters. It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
This section describes issues and workarounds that are applicable to all adapters: Oracle AQ Adapter, Oracle JMS Adapter, Oracle Files/FTP Adapter, Oracle MQ Series Adapter, Oracle Database Adapter, and Oracle Socket Adapter.
This section includes the following issue:
ECID (Execution Context Identifier) propagation is not supported by Oracle Technology adapters. The ECID is used to keep track of message flow in Oracle Enterprise Manager, and hence this feature is not available in Oracle Technology adapters.
If an outbound adapter throws an exception with
GLOBAL_RETRY, then the retry configured at the outbound adapter level will not take effect. The retry falls back to the caller which could be a BPEL process. It is observed that the retry happens from the inbound to the BPEL process (caller of BPEL process) in either of the following transaction semantics in Oracle BPEL process:
<property name="bpel.config.transaction">requiresNew</property> <property name="bpel.config.oneWayDeliveryPolicy">sync</property>
<property name="bpel.config.transaction">required</property> <property name="bpel.config.oneWayDeliveryPolicy">sync</property>
If the adapter throws a
LOCAL_RETRY, then the retry configured at the outbound adapter level will take effect.
Note that for the inbound retry to work, Oracle BPEL process must not have any dehydration points.
Included per bug 8434136.
During forceful shutdown of Oracle WebLogic Server, if the severs are processing data, then you may see JCA Binding Component error messages. These messages are benign.
This section describes the following issues and workarounds related to Oracle File and FTP Adapters:
It includes the following sections:
The Oracle File Adapter picks up a file from an inbound directory, processes the file, and sends the processed file to an output directory. However, during this process if a failover occurs in an SOA managed server, then the file may be lost because of the nontransactional nature of Oracle File Adapter. As a result, some files read by the inbound adapter may not be sent to the output directory. You must configure the Oracle File Adapter for high availability, to ensure that files are not lost during a failover.
When Oracle File and FTP Adapters read a Unicode XML file with byte order mark (BOM), a DOM parsing exception is thrown at runtime. If the Unicode XML file does not use BOM, then an exception is not thrown.
In case of debatching scenarios with XML payloads that have errors such as extra tags and spurious data, output files are created along with the rejected messages.
If Oracle File and FTP Adapters use logical directories for inbound or outbound operations, then JCA property updates from Oracle Enterprise Manager Console are not applied.
You must use a synchronous process in case of Oracle FTP Adapter debatching scenarios on FTP over SSL (FTPS) for large payloads. If a synchronous process is not used, then the FTP server throws the error code, 421.
The Chunked Read feature of Oracle FTP Adapter is not supported for SFTP (Secure FTP) using SSH transport.
When a dynamic file name is specified for an output file, the
Append property must not be edited. However, the Oracle Enterprise Manager Fusion Middleware Control Console allows you to edit the
Append property even when you specify a dynamic file name for an output file. Ensure that you do not edit the
Append property when you specify a dynamic file name for an output file.
When using a dynamic file name the value of the
Append property must be
false. By default, the value of the
Append property is
false and this must not be edited while using a dynamic file name.
This section describes the following issue and workaround related to Oracle AQ Adapter:
It includes the following section:
In an SOA project that contains outbound AQ adapter, Mediator or BPEL, and an inbound AQ adapter, when you select the business payload option as Field within the Object, the national characters are garbled.This issue depends on server locale encoding and exists only on native locale. However, when the server is running on UTF-8 encoding, this issue does not exist.
It is recommended that you use Oracle Adapter for Oracle Applications to dequeue from queues in E-Business Suite Applications and not Oracle AQ Adapter.
When using the Adapter Configuration Wizard to configure the object payload, you may configure the Business Payload as either:
Field within the Object
If you select Field within the Object, and you do not check the Access to non-payload fields also needed option, your composite may fail at run time with an
The workaround for this issue is to always select the Access to non-payload fields also needed option when you configure the Business Payload by selecting the Field within the Object option.
For more information, see "The Adapter Configuration Wizard Object Payload Page" in the Oracle Fusion Middleware User's Guide for Technology Adapters.
This section describes the following issues and workarounds related to Oracle JMS Adapter:
Anytime the exception weblogic.messaging.kernel.QuotaException: Quota blocking time exceeded and no quota available is encountered, WLS JMS provider allows flow control settings that you can tweak to control the number of messages that are produced/consumed.
For more information about tweaking the control settings, see
The following is an example of the flow control settings used and the various thresholds for a message carrying a payload size of 5k:
Config JMSServer: Message Buffer Size:5000 Config JMSConnectionFactory: Flow Control: Flow Maximum: 30 Flow Minimum: 1 Flow Interval: 10 Flow Step: 10 check Flow Control Enabled Default Delivery: Send Timeout: 3000000 Config JMS Destinations: Bytes Threshold High: 50000 Bytes Threshold Low: 50 Messages Threshold High: 100 Messages Threshold Low: 1 Set Quota
While migrating a project from one environment to another, Oracle JMS Adapter Wizard populates the Destination and JNDI name fields in edit mode in the following pages:
Consume Operation Parameters page
Produce Operation Parameters page
Request Operation Parameters page
Reply Operation Parameters page
Request/Reply Operation Parameters page
However, if you click Next, the Adapter Configuration Wizard validates whether this is a valid destination, and accordingly, displays a warning message if found to be invalid. You have the option to proceed or enter a valid destination.
When you use Oracle JMS adapter with a distributed topic deployed in a cluster, the scenario would result in more messages processed than the actual number of messages passed to the topic.
Each subscriber to the topic is handed a copy of the message to be processed by WLS JMS. So, the number of processed messages will be equal to the number of active subscribers on the distributed topic. This is a known behavior of Oracle WebLogic JMS in Oracle WebLogic Application Server 10.3.
This section describes the following issues and workarounds related to Oracle Database Adapter:
While configuring an outbound Oracle Database Adapter to perform a SELECT operation, if you select Get Active Unit of Work in the Adapter Configuration Wizard - Advanced Option page, then the value of the
GetActiveUnitofWork property is not saved in the
The workaround for this issue is to manually add this property in the
.jca file of the Oracle Database Adapter, as shown in the following example:
<property name="GetActiveUnitOfWork" value="true"/>
Consider a scenario in which the Oracle Database Adapter retries the transaction at remote fault (that is, when the database is down) in a condition where the binding fault retry is specified in the
composite.xml file, and there is no fault policy defined. In such a scenario, the binding fault retry performed by the Oracle Database Adapter is not captured in the Audit Trail in the Oracle Enterprise Manager Console.
If you re-create an Oracle Database PL/SQL statement or other schema object (such as a data type), or recompile a package body, and re-deploy a SOA composite that uses the Oracle Database Adapter, then the Oracle Database Adapter runtime will throw an ORA-00902: invalid datatype exception.
The workaround for this issue is to set the following Oracle WebLogic Server properties:
Initial Capacity: 0
Statement Cache Size: 0
Adapter Connection Pool:
Initial Capacity: 0
If your SOA composite is incompatible with these property settings, the workaround for this issue is to stop and start the Oracle WebLogic Server.
For more information, see:
"Configuring JDBC Data Sources" in the Oracle Fusion Middleware Configuring and Managing JDBC for Oracle WebLogic Server
"Connection Management" in the Oracle Fusion Middleware Programming Resource Adapters for Oracle WebLogic Server.
In this release, Oracle recommends that you use the new distributed polling approach based on skip locking. When editing an Oracle Database Adapter service which has a
MarkReservedValue set, that value will be removed to enable the new best practice.
To use the old distributed polling approach based on a reserved value, select the value from the drop down menu.
This section describes the following issues and workarounds related to Oracle MQ Series Adapter:
Oracle MQ Series Adapter does not support asynchronous request-response pattern (where Mediator is the server).
If you select the outbound resource as XA, then the Oracle MQ Series Adapter throws an exception and does not retry because it does not support an outbound retry with outbound resource as XA. On the other hand, if the outbound resource is non-XA, then the retry happens correctly.
When working with more than one managed server, if you try to bring down the channel, then Oracle MQ Series hangs. This occurs in both Windows and UNIX operating systems.
Standard Java encodings and their mappings are provided with the MQ Series Adapter but the Adapter Configuration Wizard does not support addition of additional Java encodings that you may require.
To add support for the standard Java encodings that are not provided in the list, you can perform the following steps:
MQSeriesAdapter.jar file from the
mq.properties file from the MQSeriesAdapter.jar file.
Add the entry in the
mq.properties file. This file has two entries for a mapping between MQ Series encoding and Java encoding. For each new encoding that you require, you must make two entries to the
mq.properties file. Make an entry for the MQ Series encoding to the corresponding Java encoding and the other entry for the Java encoding to the corresponding MQ Series encoding.
Oracle JCA Adapter for MQ Series is certified with MQ Series version 188.8.131.52. If you are using XA transactions, then you must configure the server connection channel with a level of conversation sharing set to 0.
This section describes the following issue and workaround related to Oracle Socket Adapter:
Oracle Socket Adapter is not supported on a cluster-based environment. If you try to deploy an inbound Oracle Socket Adapter in a clustered environment, then one of the managed servers throws an error message that the server's port is already in use.
This section describes the following issue and workaround related to Native Format Builder:
In the Specify Delimiter's page of the Native Format Builder wizard, the
White space (any number of tab, space) option in the Delimited by list is not supported.
When payload validation is enabled, it may fail with a
java.lang.ClassCastException for payloads greater than 10 MB in size.
For more information, see "Payload Validation" in the Oracle Fusion Middleware User's Guide for Technology Adapters.
This section describes the following general issues and workarounds related to Oracle Adapter for Oracle Applications:
Certain PL/SQL APIs exposed from Oracle E-Business Suite take record types as input. Such APIs expect default values to be populated for parameters within these record types for successful execution.
The default values are
FND_API.G_MISS_CHAR for characters,
FND_API.G_MISS_DATE for dates, and
FND_API.G_MISS_NUM for numbers. Adapter for Oracle Applications can default these values when the parameters within the record type are passed as nil values, as shown in the following example:
<PRICE_LIST_REC> <ATTRIBUTE1 xsi:nil="true"/> <ATTRIBUTE2 xsi:nil="true"/> <ATTRIBUTE3 xsi:nil="true"/> ... </PRICE_LIST_REC>
This can be achieved with the help of a function in a Transform activity, or by directly passing the XML input with nil values and then assigning them to the record types within an Assign activity.
When a user has a SOA composite of a PL/SQL API created against an Oracle E-Business Suite Release 11i instance and intends to use it against the Release 12 instance or vice versa, for the compatibility in the target instance, the wrapper package of the SOA composite must be recreated. This approach updates the signature in the generated wrapper SQL file for the target instance and avoids the possible confusion whether the signature is the same or has changed in the target instance.
When a user creates a Partner Link by selecting a concurrent program through Adapter for Oracle Applications, the SQL script that creates a wrapper package to submit the concurrent request is getting generated under the XSD folder in the composite artifacts and is not directly under the root composite folder. Therefore, if a user creates the composite against one Oracle E-Business Suite instance and deploys it on a different Oracle E-Business Suite instance, the user needs to find the script under the XSD folder and run the same against the target instance.
For business event inbound retry to work properly with Adapter for Oracle Applications in this release, users need to use the older retry property names
retryInterval in place of the new jca retry properties
All retried instances of Adapter for Oracle Applications share the same ECID. The ECID of the original instance also does not match the ECIDs of the corresponding retried instances.
When multiple applications database connections are created in Oracle JDeveloper, if a user selects one database connection in the Adapter Configuration Wizard and clicks the Next button, but then realizes that a different database connection should have been chosen, instead of clicking the Back button to reselect a new database connection, he or she has to cancel the Wizard and restart the process. Clicking the Back button and reselecting a different database connection will not work in this release.
In case of an occurrence of a fault when a composite fails to process a message, the rejected message will not be handled appropriately by Adapter for Oracle Applications in this release.
When trying to create a new business event Partner Link with Oracle E-Business Suite Release 11.5.9, the associated event subscription is also created with the values for Rule Function and Out Agent as blank. As a result, the subscription will not be executed when the business event is raised.
The workaround is to manually edit the subscription by adding the value
WF_RULE.DEFAULT_RULE as the Rule Function and
WF_BPEL_QAGENT<system_name> as the Out Agent.
There are no known configuration issues at this time.
This section describes documentation errata. It includes the following topic:
Section 184.108.40.206, "Undying" in Chapter Oracle JCA Adapter for Database states that the new Undying property is supported. Instead, Undying is now always true, so the configuration property has been removed.