It is imperative to know what users have what privileges, especially when it comes to the almighty SYSDBA or SYSOPER privilege. To quickly determine this use this SQL script:
select * from V$PWFILE_USERS;
What’s going on behind the scenes? This query grabs data from the password file The V$ view can be viewed while the database is in any state (closed, no-mount, mount, or open). The view will also display users with the SYSASM privilege, this privilege is only applicable to ASM instances.
Tags: oracle privileges, password file, privilege, sql privileges, sysdba, sysoper, v$, V$PWFILE_USERS, views
Auditing… great for stats not so great for space on your hard drive. Frequently people(non-technical people) say they want “all auditing” turned on… while this is necessary in a few instances, in general it should be avoided. Fine grain auditing is tricky and can cause more problems if used incorrectly(or if you don’t have a lot of HD space).If you want to give your customer/boss a rock solid reason here it is: there are TONS of processes that run in oracle 24/7 throughout the day. Every time one of these processes logs off or on or does anything different it will create a record. This may not sound like a lot at first, but 100s of processes on and off (some thousands of times a day) really can fill up your hard drive. Without further adieu if you do find yourself in clogged up situation where you cannot even log onto your database this solution is your draino!