The patch note contains the following sections:
This patch contains the following revisions since the last maintenance
release:
Available as of
Version |
APAR/CR Number |
Feature |
Description |
2.6.4 |
CR 73915 |
Code missing in Fix Pack code-line after merge from Interim Fix code-line. |
During merging of code from Interim Fix Code line to the Fix Pack
code line, a small block of code got deleted from DBManager class. This could result in failure of
stored procedure transactions, if the function call returned a simple
attribute of type ‘Float’. This has now been fixed. |
2.6.3 |
JR 21597/ CR 71314 |
Extra where clause and is null support. |
The ‘is null’ support does not work when we have more than one
attribute in the ‘extrawhereclause’, using retrieve verb ASI. This issue has
been resolved by composing proper query using multiple attributes in verb
ASI. |
JR 21480/ CR 71139 |
Using blank values in event keys to retrieve business objects using
‘is null’ clause. Using ‘CxBlank’ in event keys to generate is null clause in
retrieve query while polling. |
The poll of an event with some keys as null is not composing the
query with is null. Changes have been made to adapter to provide the value
‘CxBlank’ in the key value, so that the adapter builds the ‘is null’ clause
correctly. The usage of ‘CxBlank’ in the event object keys is fixed and the
adapter now builds the ‘is null’ phrase properly on poll. |
|
JR 22459/ CR 71391 |
Cursor leak, max cursors exceeding the set limit |
The fix involved closing the result set, when an empty result set was
returned from a stored procedure call. |
|
JR 22444/ CR 72378 |
Using blank values in keys of BO to retrieve using is null clause. |
When processing an incoming BO with some keys being null, the adapter
is not composing the query with ‘is null’. Changes have been made to adapter
to provide the value ‘CxBlank’ in the key value, so that the adapter builds
the ‘is null’ clause correctly. |
|
JR 22446/ CR 72988 |
When processing output parameters returned from the execution of a
Function in the database, they are not retrieved in the correct order. |
An incorrect index value was being used to retrieve output parameters
of type String. This has now been fixed. |
|
JR 22154/ CR 67474 |
When executing fetchConnection on Connection Pool, the method does
not exit, if CloseDBConnection=true. |
If the maximum number of DB connections was reached, the thread exits
fetchConnection only when a connection is released and the thread is
notified. If
CloseDBConnection=false, notify was being called. But it was not
called when CloseDBConnection=true. This has been fixed. |
|
JR 22431/ CR 67496 |
Adapter was not allowing the insertion of data of size > 32k for
input parameters of Stored Procedures |
There was no special handling done for input parameters to stored
procedures that were of type CLOB. This has now been fixed. |
|
JR 22463/ CR 45825 |
There are 2 pause statements in the startup script for Windows |
This has been corrected. The extra one has been removed. |
|
JR 21014/ CR 61153 |
RetrieveSP not executed for Child BOs when UseDefaultsForPolling set
to true. |
There was a bug in the SP ASI Retriever that did not parse SP ASI if
the value of that attribute was set to CxBlank, which happens when
UseDefaultsForPolling was set to true. This is has been corrected. |
|
CR 66540 |
Adapter logs Error when setting TimingStats to default |
The TimingStats property was missing from template file. It has now
been added. |
|
JR 22378/ CR 67621 |
Adapter failed to handle CLOB with length between 4000 and 4096 |
The check for size of CLOB was incorrect. That has been corrected. |
|
CR 70569 |
Remove references to data direct drivers in adapter start scripts |
The data direct driver jars in the ClassPath have been removed from
the adapter start scripts. Users should configure the same as needed i.e. add
any dependency jars, as per the user guide. |
|
JR 21999/ CR 72255 |
Adapter does not retrieve rows with empty CLOB columns |
When CLOB was null, a NullPointerException was thrown. Proper check
for null value has been introduced. |
|
JR 22462/ CR 73153 |
Retrieving N cardinality BOs with Progress DB fails |
The ProgressDB throws an exception if a close is issued on an already
closed resultset. Corrected to ensure close is called only once. |
|
JR 22458/ CR 73466 |
RetrieveSP appears to be called but is not returning resultset |
The AfterRetrieveSP SPs were getting called before the output
parameters for RetrieveSP were completely processed. This has been fixed. |
|
JR 22447/ CR 73476 |
Support for long int in stored procedures is missing |
The DriverSupportForLong property was not being used when processing
parameters of stored procedures. This has been fixed. |
|
JR 21196/ CR 61712 |
Memory leak with CloseDBConnections=true |
The fix involved checking for closeDBConnection=true, and if false
only we create the hash table entry of the connections, for use in prepared
statement cache. |
|
JR 21320/ CR 45017 |
Copy Attributes does not propagate values to child BO. |
For a child object with an attribute having the following ASI values:
PH=true:CA=..[ParentAttrName], although the appropriate value was being
copied to the child attribute, the overall operation would fail. This was due
to improper handling of the PH ASI attribute. The same has been fixed. |
|
JR 21339/ CR 61625 |
The adapter when traversing does not return the accurate error. |
If a non-required, ownership child was not found on retrieval, the
connector used to throw an error message The same has been corrected. |
|
JR 21317/ CR 44568 |
Date processing with Stored procedure causes a null pointer
exception. |
The same has been resolved in this release. |
|
JR 21272/ CR 66453 |
The table xworlds_batch_events,
created using archive_table_oracle.sql script is not used. |
The table creation of xworlds_batch_events has been removed from
script archive_table_oracle.sql. |
|
JR 20679 CR 58941 |
Timing Stats not printing the method name |
The method name was being passed to the utility method that traced
the message, but was not being included in the trace message. This has been
fixed. |
|
CR 60212 |
If a parent object with a key attribute having UID=AUTO in the ASI and has a child object which has an attribute etrieve to the parent
key as foreign key, the child object’s foreign key does not get populated
with the new identity column value from the parent. When a CREATE operation
is done. |
After the identity value was generated in table in the DB, it was not
being retrieved from the DB if the database type was DB2. This has been
corrected. |
|
CR 44732 |
ODA strips ‘_’ from BO attribute names |
The ‘_’ character, which was being stripped off earlier as a special
character would now be included as part of the BO attribute. |
|
JR 20440 |
Non-execution of AfterRetrieveByContent stored procedure in a
business object. |
The adapter failed to execute the stored procedure associated to
AfterRetrieveByContentSP. The same has been resolved |
|
CR 59112 |
Adapter fails to open new connection after database went down. |
There was an issue with the cleaning of the connection pool when the
database went down. This lead to leak of stale connections. The same has been
fixed. |
|
CR 58660 |
Usage of Stored procedure with OP=RS fails. |
The tracing mechanism had a defect and has been corrected. |
|
CR 59817 |
Return Dummy BO with OP=RS |
The Dummy BO created, when result set is null or empty in a
retrieveSP for container, was not being returned. The same has been resolved. |
|
CR 35078 |
Adapter should return APPRESPONSE TIMEOUT if the SPBeforePoll Call
Fails. |
The adapter will now return AppResponseTimeout if the stored
procedure call before polling fails. |
|
CR 43390 |
Retrieval of large CLOB data>30k fails, when using stored
procedures. |
The retrieval of large CLOB data using stored procedure is now
enabled. |
|
CR36188 |
Connector property RetryCountAndInterval does not work for child BO
data |
The adapter has been enabled to retry retrieve on child retrieval
failures. |
1. If the connector version is 2.2.0 or above, the lib directory under WBI Adapter installation should contain the WBIA.jar.
2. Apply the changes prescribed in each
table below, beginning with the entries at the bottom of each table and working
up to the most recent patch.
Add, replace,
or remove the following files and directories as indicated (Note that these are
rolled up in the patch you downloaded):
%INSTALLDIR% is
the name of the directory where WBI is installed.
For Connector Version |
Platform |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
2.6.4 - |
WIN & UNIX WIN & UNIX |
All the files in the fix pack zip or tar |
Extract all the files onto %INSTALLEDDIR%. The files will be copied over onto the folder as follows: |
Note: This adapter is backward compatible against previous versions of Adapter Framework. For Adapter Framework version support information, check ‘Software version’ under ‘Document Information’ in the fix pack link.
© 2005 IBM Corporation. Proprietary and Confidential. All Rights Reserved.