|
Hi,
I have some application written in Oracle
forms and
try to port it into SAP DB
environment.
I met following problem
When I use client side PL/SQL
like
begin
insert into table1 (field1) values
('a');
update table1 set field1='a';
end;
application locks itself out.
My explanation for such behaviour is that
Oracle Open Client Adapter
determines that SAP DB ODBC driver is not able
to support multiple
active statements per connection. It opens new
connection
for each statement so it makes possible for a single program to lock itself
out.
I can avoid this by writing stored
procedure and calling it from forms,
so it is not really big problem
I also noticed that after forms module
connects to SAPDB it opens new connection for every queried data
block . This makes very difficult to
coordinate master-detail relationship.
In practice it means, that it is neccessary to
commit every change when scrolling
records. This is not great
headache.
In comples form one can have many
blocks,
so a form module can open up 100 connections,
which does not look nice and
I'm affraid that several users could be able
to eat up memory resources on server.
Is it true that SAP DB does not support
multiple active statements per connection?
Maybe the reason for that behaviour is
somewhere else.
Wiesiek
|
- ODBC problem Hu Ping
- RE: ODBC problem Koetter, Thomas Theodor
- ODBC Problem Wiesław Poszewiecki
- ODBC Problem Jose Miselem
- RE: ODBC Problem Koetter, Thomas Theodor
- ODBC Problem David Blake
- Re: ODBC Problem Juergen Sauer
- RE: ODBC Problem Koetter, Thomas Theodor
