ramdan wrote:
>
> We have a table called segment_weights of following struc
>
> segement varchar2(50)
> studyid varchar2(50)
> weight number(4,4)
>
> with 5000 rows.
>
> We delete various values with:
>
> delete from segment_weights where segment = '44'
> commit;
>
> select * from segment_weights where segement = '44'
> returns no rows. thus rows deleted.
>
> However 20-30 minutes later the rows reappear. There are NO triggers
> anywhere, and table does not have forgein keys or appears as forgein key
> anywhere. In addition we added 1000 rows, they were there when we checked,
> yet later on 50 were missing.
>
> No one else has access to table and no process ran affecting tables. Any
> ideas?!?!?!
Someone else must have been active to insert and delete rows behind your
back. To help track this down, you should consider:
- put some triggers on the table to audit who is changing what
- set some oracle audit options to see who else is logging in
- worst case: try setting the init parameter SQL_TRACE=TRUE to trace
everything happening in your database. Of course, this must be done with
caution.
Received on Mon May 03 1999 - 06:44:50 CDT
