"Go" Oracle 11g has a password expiration issue

Prompt for "password expires after ora-28002:7 days" when logging into Oracle database using Sqlplus.

"Cause/Trigger factor"

This is due to the fact that "password_life_time=180 days" is set in the default profile in oracle11g.

"Impact and risk"

Effect

After the password expires, the business process connects to the database exception, affecting business use.

Frequency of problem occurrence

Once the database password expires, the business process will prompt for a connection failure once it restarts.

"Solutions"

Follow the steps below:

1, check the user's proifle is which, is generally default:

Sql>select username,profile from Dba_users;

2. View the password expiration settings for the specified profile (such as default):

Sql>select * from Dba_profiles s WHERE s.profile=\ ' default\ ' and resource_name=\ ' password_life_time\ ';

3. Change the password validity period from the default of 180 days to "unlimited":

Sql>alter profile DEFAULT LIMIT password_life_time UNLIMITED;

You do not need to restart the database after you modify it, it takes effect immediately.

4, after the modification, has not been prompted ORA-28002 warning account will not encounter the same prompt;

The account that has been prompted must change the password again, for example:

$sqlplus/as SYSDBA

sql> alter user SMSC identified by < original password >----do not change the new password

oracle11g startup parameter Resource_limit whether it is set to False or true, the password validity period is valid and must be modified in the above manner. The account name above is changed according to the account name you are actually using.

Ii. "Problem description"

Recently h ringtones feedback, using Sqlplus Landing Short message Oracle database Prompt "ORA-28000: Account is locked".

"Cause/Trigger factor"

It is determined that because the default profile is set to "failed_login_attempts=10" in oracle11g, the wrong number of times to enter a password will cause this problem.

"Impact and risk"

Effect

After the account is locked, the business process connects to the database exception, affecting the business use.

Frequency of problem occurrence

Once the database account is locked, the business process will prompt for a connection failure once it restarts.

"Solutions"

Follow the steps below:

1, check the user's proifle is which, is generally default:

Sql>select username,profile from Dba_users;

2. View the password expiration settings for the specified profile (such as default):

Sql>select * from Dba_profiles s WHERE s.profile=\ ' default\ ' and resource_name=\ ' failed_login_attempts\ ';

3, the number of attempts to log on failed to change from the default 10 times to "unlimited":

Sql>alter profile DEFAULT LIMIT failed_login_attempts UNLIMITED;

4, after the modification, has not been prompted ORA-28000 warning users will not encounter the same prompt;

An account that has been locked must be unlocked, for example:

$sqlplus/as SYSDBA

sql> alter user SMSC identified by Oracle account unlock;

5. After the modified default profile should be as follows:

Sql> SELECT * from Dba_profiles WHERE dba_profiles.profile=\ ' default\ ';

Profile Resource_name Resource_type LIMIT

------------------------------ -------------------------------- ------------- ----------------------

DEFAULT failed_login_attempts PASSWORD UNLIMITED

DEFAULT password_life_time PASSWORD UNLIMITED

You do not need to restart the database after you modify it, it takes effect immediately.

Original from the "Bit network", reproduced please keep the original link: http://soft.chinabyte.com/database/43/11835543.shtml