Solution for bringing out ORA-28001 at the same time by ORA-28000

Today, you can not log on to the tomcat front-end interface, view the log found that the original is ORA-28001: thepasswordhasexpired error, this error is due to Or

Today, you can not log on to the tomcat front-end interface, view the log found that the original ORA-28001: the password has expired error, this error is caused by Or

Today, you can not log on to the tomcat front-end interface, view the log found that the original ORA-28001: the password has expired error, this error is caused by the new features of Oracle11G, when creating a user at Oracle11G, the default password expiration limit is 180 days (6 months). If the user password is not modified for more than 180 days, the user cannot log on.

================================================= =====

Recommended reading:

ORA-01172, ORA-01151 error handling

ORA-00600 [2662] troubleshooting

Troubleshooting for ORA-01078 and LRM-00109

Notes on ORA-00471 Processing Methods

ORA-00314, redolog corruption, or missing Handling Methods

Solution to ORA-00257 archive logs being too large to store

================================================= =====

You can use the following SQL statement

SELECT * FROM dba_profiles WHERE profile = 'default' AND resource_name = 'password _ LIFE_TIME ';

Query the password validity period settings. The LIMIT field is the password validity period.

When the password is about to expire or has expired, use the following statement to modify the password. After the password is changed, the user can connect to the database normally.

Alter user Username identified by password;

To remove the 180-day password lifecycle restriction, use the following SQL statement to disable it:

Alter profile default limit PASSWORD_LIFE_TIME UNLIMITED; ---- (not recommended)

Then, go to the sys account and unlock the account:

Alter user Username account unlock;

The result was not long before, and prompted the ORA-28000 the account is locked, always unlock, but every time is a few seconds immediately locked. It was found that the FAILED_LOGIN_ATTEMPTS parameter was incorrect.

Solution:

Alter profile default limit failed_login_attempts times or unlimited;