Shulou(Shulou.com)05/31 Report--

The purpose of this article is to share with you what to do if there are ORA-28000 errors in oracle. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

This problem is very rare, users will not be able to log in! According to the prompt, The account is locked this account is locked. What's the situation? let's log in to sysdba and have a look.

Format:

Select account_status,lock_date,profile from dba_users where username='USERNAME'

Parsing:

This sentence query fields account_status (account status), lock_date (lock data), profile profile field, then dba_users view the view chart of all user status, specify username, your account name can see the status.

Check this state when found to be LOCKED (TIMED), lock (time) has not seen this state before, I on Baidu, the system default configuration password login (wrong login) login 10 times, so give a time lock, know these easy, I feel that 10 times to enter the lock is too unsafe!

I want to change it to 3 times. First, we need to know how to check the default settings of the system, as follows.

Format:

Select resource_name,resource_type,limit from dba_profiles where profile='DEFAULT'

Explanation:

Query the resource name, type, limit the source table is the dba_profiles view (dba configuration file), specify default, so it comes out!

Format:

Alter profile default limit FAILED_LOGIN_ATTEMPTS unlimit (unlimited);-- I set it 3 times for safety (in non-production environment)

Explanation:

The default limit for changing the profile is 3 failed login attempts! It's easy to understand. No difficulty.

At this time, we can unlock the user.

Format:

Alter user scott account unlock;-- changes user's scott account to unlock

At this time, we checked in the dba_users view and found that the login was unlocked and the login was successful. I also specially tried 3 failed logins, and the error ORA-28000 still seems to be very effective! At this time, it is hoped that the problem-solving will be of some help to everyone.

Supplementary record:

Because I actually checked show parameter resource, I was surprised to find that resource limit,values-> false was not enabled. The resource shows that it is not enabled, but it takes effect 10 times. Why?

Access to some information and understanding, FAILED_LOGIN_ATTEMPTS is not subject to the constraints of resource limit, modified to use alter profile is the user password management, variables are resource management, passwords are not restricted by RESOURCE LIMIT, some textbooks divide profile into two categories: management passwords and resources.

It feels good to quote netizens' posts. Http://www.php.cn/mysql-tutorials-135104.html is more detailed than I am. Please refer to me and have a lot of knowledge.

Finally, I want to check how many times the user has failed to login in Oracle?

Format:

Select lcount from user$ where name='USERNAME';-- can see the statistics.

Format:

SQL > audit session whenever not successful

The audit was successful.

SQL > set linesize 1000

SQL > col userhost for A20

SQL > col COMMENT$TEXT for A30

SQL > col SPARE1 for A20

SQL > col NTIMESTAMP# for A35

SQL > select sessionid,userid,userhost,comment$text,spare1,to_char (ntimestamp#+1/3,'yyyy-mm-dd hh34:mi:ss') from aud$ where returncode=1017 order by ntimestamp# desc

Information about user$ and aud$ is very useful!

Thank you for reading! This is the end of the article on "what to do if there are ORA-28000 errors in oracle". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.