how can I find out who is locking my ORACLE 10GR2 database
I have may users who us system accounts on my ORACLE 10GR2 database , I can see what I think this the connection that is locking it in the listener.log it looks as it is a pearl script of sometype , this is all on windows , how can i find out what workstation this is comming from , can I find out what ip addreess the locking action is comming from ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
johnsone
If you found the record in the listener log, it should have the IP address that the connection came from in there.
ASKER
the ip addrss are all comming from the same server that the database is on , it has a IIS on it so that may be comming from that as the application connects thru the IIS , I am looking at some enteries in the linstner.log and i see some that are from w3wp processes and some others from perl . this listerner mearly hands off the connection to the database and has no knowledge of weather or not the password is locked , so this log would never show any info about a locked account correct?
Sorry, I think we were thinking something different when you said locked.
Locked accounts can be found in DBA_USERS.
If you have an invalid attempt lockout on the user through a profile, there is not way to tell who locked it out without using a database trigger to log the failed attempts. But using the tiered architecture you are, you would most likely only get the IIS server as the "person" locking the account.
Locked accounts can be found in DBA_USERS.
If you have an invalid attempt lockout on the user through a profile, there is not way to tell who locked it out without using a database trigger to log the failed attempts. But using the tiered architecture you are, you would most likely only get the IIS server as the "person" locking the account.
ASKER
what is the exacy synatax i AM ANEWB at oracle?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.