Rows are not committed

[Mockenrue]

Hello forum,

We have an application built with Forms 6i using Headstart for Oracle Applications on
a 8i database (8.1.7) and AIX unix platform.

Initially all worked fine until we had a crash of the AIX server. After that time, we
have problems regarding commit of rows. Our forms say "X rows commited" in the
status bar, but the rows are not committed (requery yields the old values and the
"Do you want to commit your changes" dialog appears).

We have our tables in a specific schema, say CUST. To implement multi org, these
tables are named, say EMP_ALL, DEPT_ALL and we use updateable views EMP, DEPT
but these views are in the APPS schema. Our forms are based on the updateable
views, so all DML is executed on the views, not on the tables directly.

We have checked all grants, synonyms etc., these seem o.k. We suspect it has to
do with the recovery of the AIX server but have no clue where to start.

Any suggestions ?

 

[sem]

Do you use intead-of triggers? If so, are they enabled?

 

[Mockenrue]

I assume you mean Form triggers that by-pass the Standard Event; no we don't use
these.

As said already, all DID work o.k., until that crash of the server.

 

[sem]

I mean DATABASE instead-of triggers that allow to update views, based on more than 1 table.

Or how else do you update views?

 

[Mockenrue]

No we don't use such triggers. In terms of EMP/DEPT we have a table EMP_ALL in
schema CUST and a view EMP in schema APPS which only lists the rows that match
the Org Id the user is working in.

CREATE OR REPLACE FORCE VIEW EMP
AS SELECT /*+ choose */ *
from EMP_ALL
where org_id =
nvl
( to_number
( decode
( substr( userenv('CLIENT_INFO'), 1, 1)
, ' ', null
, substr( userenv('CLIENT_INFO'), 1, 10)
)
)
, -99
)

 

[Mockenrue]

We found the cause. Some Headstart for Applications QMS constraints caused a
rollback for all DML statements:

Check constraint QMS_NEED_TO_CLOSE_TRANSACTION on table
qms_transactions.

Still unclear why it never happened before the crash.