Why don't you remove delete privs for this table to all users except for SYS
and SYSTEM? It must be the case that someone or some application is issuing
a "delete".
nbindal_at_my-dejanews.com wrote in message
<6jq83h$971$1_at_nnrp1.dejanews.com>...
>Hi,
>
>This is another mysterious problem that we are facing in our application.
>There is a table which contains 300 rows (loaded up while setting the
>application). No one is supposed to delete or insert from this table.
(select
>and updates are done on it continously from multiple processes).
>
>However what we have observed is that, daily 1-4 rows get deleted. I want
to
>know if there are other conditions in which the rows can get deleted - like
>locking, deadlocking etc (There are no user defined db trigger defined in
this
>application)
>
>To debug this problem we added a trigger (BEFORE DELETE) on this table, to
log
>into another dummy table the row that is getting deleted. Is there any way
to
>put in this trigger the processid of the client program which is deleting -
>that way we identify the source of problem. Also if anyone has other ideas
of
>finding the culprit, it would be very helpful.
>
>Thanks
>Nitin
>
>-----== Posted via Deja News, The Leader in Internet Discussion ==-----
>http://www.dejanews.com/ Now offering spam-free web-based newsreading
Received on Mon May 18 1998 - 17:57:03 CDT
