Unfortunately I can't make the decision to drop powerbuilder. We have
been using it for at least 10 years without seeing this problem. By
default, powerbuilder uses the table (and schema which I removed above)
prefixes and the quotes around everything in all it's datawindow select
statements. I have made all the modifications suggested (remove
quotes, etc...) and run it through a PB created SQL utility we created
and it still shows the problem. I feel I should mention that I have
seen the problem in non-PB apps in the past (Toad and I think even
SQL*Plus once) but these were all machines that have PB or at least the
PB runtime dlls installed. We have never tried this on a machine that
has never had the PB dlls on it because we don't have any. Anyway,
more often than not it is a PB app that has the problem so I figure it
has something to do with the PB dlls.
I don't know why a select statement would lock anything, but I
monitored the locks through the session browser in toad while I ran the
select in our PB SQL utility and I didn't notice any locks between the
time that I executed the select and when the oracle server dropped my
session (about 40 seconds).
Received on Tue Sep 12 2006 - 14:58:02 CDT
