on 2019 Apr 24 7:18 AM
Dear All,
what is best practice to decommission auditing in BO 4.2.x
I have a couple of small BO Servers with auditing configured - but not used -so it is only consuming rare hd space with Sybase anywhere and one installation does open too many connections to the oracle auditing schema - annoying the oracle DBA ...
So how to do a decommission of a configured audit properly?
Setting Set Events to off does only reduce saved events but not stopping the db activities...
- Wobi
Request clarification before answering.
If you don't want to use the Auditing functionality, check the KBA:
1954234 - How to disable auditing in Business Intelligence Platform 4.0 (BI)
Also, remove the client Auditing Proxy service from the APS, along with the steps mentioned by Jawahar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not sure if this is related - but since i decomissioned the Audit db - every Fiori report pops up a warning that commentary is not working anymore...
The resource of type "Service" with identifyer "Comments" is not available.
Since our Fiori is still experimental it is not a big issue but still annoying...
Wobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
and if you decommission the auditing db - fiori reports poping up a warning - even if commentary was never used or configured..
that seems a bug to me!
Wobi
Thank you Rajdeep, this was exactly what I was looking for...
Meanwhile I worked out a workflow to simply reduce the Audit db size.
use Sybase central to unload the database into a new one - so that deletes all the "deleted" old entries and reduces size
- with
dbstop with -Parameters - the old Audit db can be replaced with the new smaller one;
dbspawn with Parameters checks if this new one works - so any regular reboot makes the maintenance complete...
- Wobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Setting the events to off should stop the auditing activities.
If you still thin there are some activities recorded, remove the audit DB information like schema etc, and Turn off "ADS Autoreconnect" and ask your DBAs to remove the schema from the DB. So BO will not be able to write events to DB.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
52 | |
8 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.