The following table shows the APARs (and CRs) fixed in Fix pack version 2.6.5 |
1 | 67959 | | Two positions where trace message 32017, not 32016 should be used |
Problem: There are two positions where trace message 32016 was used by mistake; 32017 is the correct trace message number. |
Fix: Trace message 32016 has been replaced with 32017 in these two positions. |
|
2 | 67929 | | Message of returned instance of class CWConnectorExceptionObject is not correct |
Problem: When the JDBC adapter handles a service request that fails due to an exception, it will retry the operation. If the second attempt to handle this service request fails again, the message of the returned instance of class CWConnectorExceptionObject is incorrect. |
Fix: This defect has been fixed. The message for the second failure is now correct. |
|
3 | 82879 | JR22976 | JDBC adapter receives an "Invalid Ref-Cursor" error when doing a RetrieveSP operation |
Problem: When trying to retrieve a business object from a table using a stored procedure that returns a ResultSet through a cursor, the JDBC adapter will encounter an "Invalid Ref-Cursor" error from Oracle. |
Fix: This defect has been fixed. |
|
4 | 74554 | JR22906 | JDBC adapter generates a java.sql.SQLException error: Not enough memory with CLOB in SP |
Problem: The JDBC adapter needs more memory to read and store CLOB type data. |
Fix: This defect has been fixed. To fix this issue, the JDBC adapter has optimized its memory allocation for CLOB type data. |
|
5 | 74241 | JR23258 | Application-specific information UNVL=NULL cannot work correctly |
Problem: When the application-specific information UNVL=NULL is specified and the value of this attribute is null, the JDBC adapter ignored this attribute, and therefore cannot update its value to null in the database as expected. |
Fix: This defect has been fixed. |
|
6 | 74237 | JR22731 | JDBC adapter 2.6.4 generates SQL sentence like "where ... xxx is null" that results in a CLI0612E exception |
Problem: For the RetrieveByContent verb, the JDBC adapter tried to set the redundant attribute value into preparedStatement when generating the SQL Query 'where ... is null'. |
Fix: This defect has been fixed. |
|
7 | 74225 | JR22760 | NUMBER field in the Oracle database is converted into String by the ODA |
Problem: The ODA does not use the separator that is needed between the precision and decimal positions. Also, the arithmetical operator +/- does not have any space. |
Fix: The length will be extended by 2 for those columns with Decimal data type. |
|
8 | 67678 | | The getVersion() implementation for the JDBC adapter needs to be updated |
Problem: The adapter version should be implemented from the Manifest file rather than from a static variable set in the code. |
Fix: This update has been done. |
|
9 | 67361 | | JDBC adapter prints out an incorrect error message when there is no record in the UID table |
Problem: When there are no records in the UID table, the adapter prints out an error message saying that there are problems in the database connection. |
Fix: This defect has been fixed and the adapter now prints out an appropriate error message. |
|
10 | 83827 | | Support on Solaris 10 platform needed |
Problem: JDBC adapter should be supported on the Solaris 10 platform. |
Fix: Support has been provided now. |
|
11 | 83714 | JR23663 | JDBC adapter writes an incomplete business object to the Oracle database |
Problem: If the JDBC adapter receives a shutdown message during a transaction, it executes a connection close operation. But for the Oracle database, the connection close operation requires that a commit operation be performed before the close operation, not a rollback. Otherwise, the transaction may result in inconsistent data in the Oracle database. |
Fix: When receiving a shutdown message, in order to make sure that the data in the database remains consistent, the JDBC adapter will explicitly execute a rollback operation. |
|
12 | 83686 | | References to data direct drivers in the JDBC ODA start scripts should be removed |
Problem: The data direct driver JAR files in the class path need to be removed from the start scripts of the JDBC ODA. |
Fix: The data direct driver references have been removed. You must add the appropriate JDBC driver files into the class path. |
|
13 | 83595 | JR23449 | DB2 sequence support for JDBC adapter has a bug |
Problem: Sequence is supported in DB2 8.X. So the JDBC adapter will support sequence for DB2 8.X. This feature was added into JDBC adapter in version 2.5. But the correct sql statement for the DB2 sequence cannot be generated. |
Fix: This defect has been fixed and the correct SQL statement for the DB2 sequence will be generated. This will be used to get the value from the DB2 sequence for UID in JDBC adapter. |
|
14 | 68092 | JR23653 | java.lang.ClassCastException is thrown when setting application-specific information PSC=true |
Problem: When setting the application-specific information PSC=true and executing a stored procedure, the JDBC adapter generates a java.lang.ClassCastException. This is a bug in the PreparedStatement cache for the stored procedure. |
Fix: A PreparedStatement will be declared for the SP SQL sentence first. Then this PreparedStatement will be cast into a CallableStatement. |
|
The following table shows the APARs (and CRs) fixed in Fix pack version 2.6.3 |
1 | 71314 | JR21597 | Extra where clause and "is null" support |
Problem: The "is null" support does not work when there is more than one attribute in the extra where clause, using retrieve verb application-specific information. |
Fix: This issue has been resolved by composing proper query using multiple attributes in verb application-specific information. |
|
2 | 71139 | JR21480 | 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. |
Problem: When an event has some keys set as null the adapter does not generate the SQL query with the "is null" clause. |
Fix: The use of CxBlank in the event object keys is fixed, and the adapter now builds the "is null" clause properly on poll. |
|
3 | 71391 | JR22459 | Cursor leak, max cursors exceed the set limit |
Problem: There is a cursor leak with the max cursors exceeding the set limit. |
Fix: The ResultSet is now closed when an empty ResultSet is returned from a stored procedure call. |
|
4 | 72378 | JR22444 | Using blank values in keys of the business object for retrieval purposes using the "is null" clause |
Problem: When processing an incoming business object with some keys designated as null, the adapter is not generating the query with the "is null" clause. |
Fix: Changes have been made to the adapter to provide the value CxBlank in the key value, so that the adapter builds the "is null" clause correctly. |
|
5 | 72988 | JR22446 | Output parameters returned from the execution of a function in the database are not retrieved in the correct order |
Problem: An incorrect index value was being used to retrieve output parameters of type String. |
Fix: This defect has been fixed. |
|
6 | 67474 | JR22154 | If CloseDBConnection is set to true, adapter waits indefinitely to fetch a connection. |
Problem: When the maximum number of database connections was reached, the thread exited the fetchConnection only when a connection was released and the thread was notified. If CloseDBConnection=false, notify was being called. But it was not called when CloseDBConnection=true. |
Fix: This defect has been fixed. |
|
7 | 67496 | JR22431 | JDBC adapter does not allow the insertion of data of size greater than 32k for input parameters of stored procedures |
Problem: No special handling was done for input parameters to stored procedures that were of type CLOB. |
Fix: This defect has been fixed. |
|
8 | 45825 | JR22463 | Extra pause statement in the startup script for Windows |
Problem: There are two pause statements in the startup script for Windows. |
Fix: That extra statement has been removed. |
|
9 | 61153 | JR21014 | RetrieveSP not executed for Child business objects when UseDefaultsForPolling is set to true |
Problem: If the value of that attribute was set to CxBlank, the SP application-specific information retriever does not parse SP application-specific information. This happens when UseDefaultsForPolling was set to true. |
Fix: This defect has been fixed. |
|
10 | 66540 | | JDBC adapter logs error when setting TimingStats to default |
Problem: The TimingStats property was missing from the template file. |
Fix: This defect has been fixed. |
|
11 | 67621 | JR22378 | JDBC adapter fails to handle CLOB data with length between 4000 and 4096 |
Problem: The check for the size of CLOB data was incorrect. |
Fix: This defect has been fixed. |
|
12 | 70569 | | References to data direct drivers in JDBC adapter start scripts should be removed |
Problem: The data direct driver JAR files in the class path need to be removed from the start scripts of the JDBC adapter. |
Fix: The data direct driver references have been removed. You must add the appropriate JDBC driver files into the class path. |
|
13 | 71729 | JR21809 | JDBC ODA 2.6.2 does not work with business object designer of AF |
Problem: The 2.4 framework is not bi-di enabled. The 2.6.2 JDBC ODA has bi-di enabled features and therefore fails on version 2.4. |
Fix: The fix has been made to the JDBC ODA to check for the BIDI enablement in the ODK and make calls appropriately, to ensure backward compatibility. |
|
14 | 72255 | JR21999 | JDBC adapter does not retrieve rows with empty CLOB columns |
Problem: When a CLOB type variable is null, a NullPointerException is thrown. |
Fix: A proper check for null value has been introduced. |
|
15 | 73153 | JR22462 | Retrieving N cardinality business objects with the Progress database fails |
Problem: If a "close" is issued on an already closed ResultSet, the Progress database throws an exception. |
Fix: Corrected to ensure "close" is called only once |
|
16 | 73466 | JR22458 | RetrieveSP appears to be called but does not return a ResultSet |
Problem: The AfterRetrieveSP stored procedures were getting called before the output parameters for the RetrieveSP were completely processed. |
Fix: This defect has been fixed. |
|
17 | 73476 | JR22447 | Support for long int datatype in stored procedures is missing |
Problem: When processing parameters of stored procedures, the DriverSupportForLong property was not being used. |
Fix: This defect has been fixed. |
|
The following table shows the APARs (and CRs) fixed in Fix pack version 2.6.2 |
1 | 61712 | JR21196 | JDBC adapter memory leak with CloseDBConnections=true |
Problem: JDBC adapter memory leak with CloseDBConnections=true. |
Fix: The fix involved checking for closeDBConnection set to true. If it is set to false, the adapter just creates the hash table entry of the connections, for use in prepared statement cache. |
|
2 | 45017 | JR21320 | Copy Attributes does not propagate values to child BO |
Problem: For a child object with an attribute having the following application-specific information values: PH=true:CA=..[ParentAttrName], although the appropriate value was being copied to the child attribute, the overall operation failed. This was due to improper handling of the PH application-specific information attribute. |
Fix: This defect has been fixed. |
|
3 | 61625 | JR21339 | When traversing, the adapter does not return the accurate error |
Problem: If a non-required, ownership child was not found on retrieval, the connector generated an error message. |
Fix: This defect has been fixed. |
|
4 | 44568 | JR21317 | Date processing with stored procedure causes a null pointer exception |
Problem: Date processing with a stored procedure causes a null pointer exception |
Fix: This defect has been fixed. |
|
5 | 66453 | JR21272 | The table xworlds_batch_events, created using archive_table_oracle.sql script is not used |
Problem: The table xworlds_batch_events, created using archive_table_oracle.sql script is not used. |
Fix: The table creation of xworlds_batch_events was removed from the script archive_table_oracle.sql. |
|