Re: "Write once-Read many" table ?

Niall Litchfield wrote:

> Database Vault can be relatively trivially sidestepped by someone with
> access to the oracle software owner's account on the server (create a
> new password file) and may not be available for your version, write-
> once media tends not to be written to at the time of the initial write
> (a new piece of media for every single write is unsustainable) instead
> people move data to it periodically, triggers can be circumvented and
> so on.

If you think you can get into the tables owned by DVSYS that easily I'd be interested in seeing your test coce, off-line. At least when working with Audit Vault, it is not that easy. Nor is it easy to circumvent the event triggers.

-- 
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan_at_x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org