richwiz11 schrieb am 15.01.2012 um 20:37 (-0000):

> The problem I am left with is how to protect a row from being deleted.

> The two method I have thought of is
> a) Using roles and remove the delete privilege (we currently just
> using SYSDBA, which is probably a bit bad anyway)
> or
> b) Add some kind of trigger logging to keep this deleted data and copy
> to another db.

Go with method (a). Why reinvent the wheel?

And do get rid of SYSDBA as your application user.
--
Michael Ludwig