Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Changing Default Isolation Lock - Websphere / ATG / DB2

133 views
Skip to first unread message

Sheila

unread,
Jun 1, 2005, 4:05:26 PM6/1/05
to
Hello,

I'm using ATG7.0/WSAD5.1 and DB2.
I am using ATG's SQLQueryRange droplet with a select query. It
produces this error:

[6/1/05 14:51:20:740 CDT] e75c318 SystemOut O
/atg/dynamo/droplet/SQLQueryRange Unable to execute query due to
SQLException: com.ibm.db2.jcc.c.SqlException: UNSUCCESSFUL EXECUTION
CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C90096, TYPE OF RESOURCE
00000302, AND RESOURCE NAME XXXXXXXXXX

I've tried to do a straight jdbc connection query and it gives me the
same type of resource unavailable error.

I've determined REASON 00C90096 was a possible isolation lock error.
I've tried to change the isolation lock to read committed
(wsOptimisticRead) through WSAD. (using this doc:
http://www.webspherepower.com/issuesprint/issue200410/00001357.html).

I mainly just want to do read-only hits to the database, so don't
really want to lock any rows/pages/tables. The data returns at least
5000 rows. If increasing the tablespace is not an option, is there an
alternative?

Thanks for any help.

0 new messages