Re: SYS can't own triggers?!

In article <3D5C51AE.1C7C9377_at_bigpond.com>, Richard says...
>
>Hi Peter,
>
>The way I describe this.
>

just to add a bit. things work DIFFERENTLY for sys cause sys is special.

o set transaction read only -- nope, won't work (as well as other things). SYS is used to do recursive sql and such and playing with its isolation level would be a *bad* thing

o try doing autotrace statistics for SYS.

o in 9i, we've made it really *hard* to log in as SYS, to see SYS owned things.

You should just pretend it doesn't exist.

>SYS is the "owner" of the database, at least the owner of the various
>internal tables and data structures that are used implicitly by Oracle
>during the general running of the database. SYS is like a special,
>hidden little chap that executes all this recursive code and ensures the
>database runs as required.
>
>Now if we do anything that might interfere with SYS doing it's job, it
>could impact directly on the running of the database with obvious
>possible disastrous results.
>
>Note SYS is also our "get in" user. No matter what might be occurring in
>the database, no matter what disastrous logon triggers are preventing
>everyone else from entering the database, SYS can always get in. Hey,
>this little guy is effectively God in the database. Locking SYS,
>dropping SYS, creating objects that SYS really shouldn't look after,
>creating objects as SYS that might take up space that's required for
>"real" sys objects, etc are all no nos (and not possible in many cases).
>
>Lastly, ever tried exporting SYS ? Bit tricky, so objects that you
>create as SYS are not easily manipulated in this manner.
>
>And lastly lastly, if you connect in as SYS and create things as SYS,
>you can also drop things as SYS. Why not, you're connected in as SYS
>right. Well such "accidents" such as dropping the wrong table when
>connected in as SYS can also have unwelcome repercussions. So I question
>even connecting in as SYS unless you are performing sysdba/sysoper type
>functions.
>
>In summary, if you (could) create a trigger as SYS, you would probably
>end up shooting yourself with it :)
>
>Cheers
>
>Richard
>
>Peter Chatterton wrote:
>>
>> > DON'T create anything, nothing, nada, nunca -- as SYS. Even these
>> triggers!
>>
>> This is finally getting to my implied question: what is so special about SYS
>> that you can't create anything?
>> Peter.

--
Thomas Kyte (tkyte@oracle.com)             http://asktom.oracle.com/ 
Expert one on one Oracle, programming techniques and solutions for Oracle.
http://www.amazon.com/exec/obidos/ASIN/1861004826/  
Opinions are mine and do not necessarily reflect those of Oracle Corp