How to stop CONNECT auditing

[mdet]

Hi there,
we're running oracle instances (8.0.5) and we disabled auditing (via init.ora entries). It's said that the default for auditing (if you just prefix the appropriate line in the file with a pound sign) is NONE. Hopefully this is true.
Although every "connect internal" through svrmgrl yields to a file in the default directory for auditing trails. The funny thing is that nothing happens if you did it through sqlplus.
The documentation states, that this particular auditing is always enabled but I guess there must be a way to disable this.
In our installation there are a lot of jobs that access the DB using svrmgrl. So the audit directory is full of useless audit trails and grows constantly.
OK, we can periodically delete this garbage, but we dont fumble this way.
We running Solaris Versions 6 and 8.

Is there anybody out there who solved this problem?

 

[sem]

Are you sure you DO NEED to use svrmgrl instead of sql*plus?

 

[mdet]

Hi sem,
We're going to think about changing to sqplus; good idea; thanks for that.
But I'm curious about the mechanisms behind that. Do you have a clue? I mean
- generally disabling auditing and
- the rules what is audited under what circumstances

Michael.

 

[rcurva]

You can not disable the auditing of the following database related actions.

Instance startup
Instance shutdown
Connections to databse with admin privileges (internal or as sysdba)

Robbie

"The rule is, not to besiege walled cities if it can possibly be avoided" -- Art of War

 

[mdet]

OK Robbie,
I finally got it. So w're going to delete these aud files.
And of course we'll stop to besiege walled oracle...

 

[rcurva]

Ooops... there's no intention of relating my "signature" with my reply.

Robbie

"The rule is, not to besiege walled cities if it can possibly be avoided" -- Art of War