Re: billing cpu usage of a monthly basis

"Pete Finnigan" <pete_at_petefinnigan.com> wrote in message news:tMpDABBxruC$EwQ6_at_peterfinnigan.demon.co.uk...
> Hi Hans
>
> I am sure that if you create the aud$ table under another schema and
> point at it with a synonym you might invalidate your support contract.
> Oracle no longer supports moving aud$ to another tablespace than system
> let alone another schema. This was due to some customer not being able
> to perform a recovery.
>
> You do not need to do what you suggest as the system triggers allow you
> to capture logon/logoff providing you have the right version?
>
> hth
>
> kind regards
>
> Pete
> --
> Pete Finnigan
> email:pete_at_petefinnigan.com
> Web site: http://www.petefinnigan.com - Oracle security audit specialists
> Book:Oracle security step-by-step Guide - see http://store.sans.org for details.

... and if the OP does not have the right version .. even then he can with great enthusiasm :) archive the sys.aud$ multiple times a day. That is /supported/.

.. and yes, I agree that Oracle has it stated explicitly on metalink, that moving sys.sud$ table is unsupported.

In reference to OP's question about how to figure out clean disconnects and aborts ... sys.aud$ table will record it if its an unclean disconnect (e.g. logoff by cleanup). However afaik sys.aud$ does not record the time interval that the user was connected.

This way of billing seems quite ridiculous though!

Anurag Received on Tue Jul 08 2003 - 19:08:09 CDT