|
-
user history
Hi,
how can i create report which includes user log in and log out information. also fail login as well.
Please guide!! totally new to this!!
Thanks
Pat
-
Auditing seems to be a pretty straightforward and well documented feature. Google had quite a few hits, but the second link seemed to be pretty specific. Just be aware the the adump directory in your admin directory might get rather full. Google is your friend and big brother!!!
http://www.google.com/search?q=oracl...nt=iceweasel-a
http://www.oracle-base.com/articles/...ting_10gR2.php
http://download-uk.oracle.com/docs/c...6521/audit.htm
-
As an alternative to Gandolf's suggestion you can always populate your own logon_audit table by resorting to AFTER LOGON, AFTER SERVERERROR 1017 and BEFORE LOGOFF triggers. They are nicely covered in Oracle documentation.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
-
will it contain failed log on as well??
-
Yes... a AFTER SERVERERROR 1017 Trigger would capture failed login attempts. Look at the documentation.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
-
would you please post the link i am new to this and can't get to find any thing!!
thanks
Pat
-
You can either code it yourself or use an Oracle feature, and there are valid reasons why you would choose one path and not the other.
Just be aware that if there is a problem with the logon trigger you could prevent non-DBA's from logging onto the database. For example if your tablespace fills up and you don't have any error handling an exception gets thrown and none of you users will be able to logon. You should also be somewhat familiar with writing PL/SQL. But as with anything good testing will help you to see what the pitfalls are.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|