UniVerse Database

[fuit]

LSH, did you ever get to resolve your record locking problems? I'm facing the same thing. If you did, kindly share with me.

[LSH]

Hi,
The record-locking problems are because of a bug in IBM's driver. The
DatabaseMetaData.supportsTransactionLevel function (which ColdFusion uses to
determine whether or not you can change the isolation level) incorrectly
returns FALSE instead of TRUE. I'm honestly not sure if they've released a new
version yet or not (we found a work-around and I haven't spent much more time
on it). Hope this helps.

Lynnette


Here's the ticket we submitted to IBM:

--------------------------------------------------------------------------------
-------------
Product: UniVerse - UV Dbase: UniVerse Platform:
Release: 9.6.1.14 Dbase Rel: 9.6.1.14 OS: HP-UX
Problem Cat: Functionality OS Rel: 11

--------------------------------------------------------------------------------
---------------
Call Summary:
Problem: Using the UniVerse JDBC driver with ColdFusion, we are not able
to change the transaction isolation level.

Details:

Using the UniVerse JDBC driver, the function
DatabaseMetaData.supportsTransactionLevel is returning FALSE. However,
setting the transaction isolation level is supported with this driver
using setTransactionIsolation, and
DatabaseMetaData.supportsTransactionLevel should be returning TRUE.


We use this driver with ColdFusion, and because of this incorrect response
from supportsTransactionLevel, it assumes it is not possible to set the
transaction level, and the setTransactionIsolation command is ignored.


In the guide 'Using the IBM JDBC Driver for UniData and UniVerse', pg 5-24
lists methods of the DatabaseMetaData interface that are not supported,
and this function is not in that list.

Solution:

To fix this problem, we would need the driver to return TRUE from
DatabaseMetaData.supportsTransactionLevel.

******************************************

Here was IBM's response on getting it fixed:

-----Original Message-----
Sent: Tuesday, November 09, 2004 4:00 PM

> For my information what does this mean? That a fix is needed and it will
> appear some time in the future or can you be more specific - say a patch
> or release date?

By creating an ECase (Engineering issue), I am indeed acknowledging that
there is an issue with the product. However I do not have any control on
what is happening next.
Engineering has to plan/prioritize issues and sometimes it may not even be
fixed. We can put a better visibility for any issue with a business case.

If fixed it will only be available with a next release of the client CD
(10.1B or later depending on the planning for the fix).

Reynal Cocaign
IBM - U2 Technical Support