Today, a netizen sent for help information, said a social security comprehensive management system of the connection of an Oracle user is frequently locked, use alter user XX account unlock unlocked one will still be locked, use Plsql login prompt ORA-28000 Let him execute this. SQL SELECT * from dba_profiles where resource_name like ' failed_login_attempts% '; He said limit is 10, the initial decision is due to frequent incorrect password login more than 10 times, resulting in the user is locked, you can use the Alter profile default limit Failed_login_attempts unlimited; But this is not the root of the problem. Check alert warning log, found that there are a large number of ORA-3136, this error is mostly negligible, the cause of this mistake is generally due to the client because the user is not using the correct password, connection timeout, from this error can be seen in the application level, he said there is an application link to the users , I suggest that he carefully check the application of the database password in the configuration is wrong, he again check that there is no mismatch, it is strange, but this problem must be in the application level, finally found in the application of a configuration file, the configuration of some parameters, if you modify the database configuration, to add-clean parameters, Otherwise, the original link will be read even after restarting the app. A direct restart of the app without-clean causes the configuration to not take effect. It seems that most of the problems are still on the surface of the day, and the first problem should be analyzed from the application level.
This article is from the "O Record" blog, so be sure to keep this source http://evils798.blog.51cto.com/8983296/1420886