The Oracle11g startup parameter resource_limit takes effect regardless of whether it is set to false or true. Therefore, you must modify the password in the preceding method. The preceding account name
Whether set to false or true, the Oracle 11g startup parameter resource_limit takes effect for the password validity period. Therefore, you must modify the password in the preceding way. The preceding account name
You do not need to limit the expiration time of your account during development, so you need to make some settings.
1. Check the user's proifle, which is generally default:
SELECT username, profile from dba_users;
2. view the password validity period settings of the specified profile (such as default:
SELECT * FROM dba_profiles s WHERE s. profile = 'default' AND resource_name = 'password _ LIFE_TIME ';
3. Change the password validity period from the default 180 days to "unlimited ":
Alter profile default limit PASSWORD_LIFE_TIME UNLIMITED;
After modification, the database does not need to be restarted and takes effect immediately.
4 after the modification, the account that has not been prompted ORA-28002 warning will not again 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 <Original password> ---- New password is not required
Whether set to false or true, the Oracle 11g startup parameter resource_limit takes effect for the password validity period. Therefore, you must modify the password in the preceding way. The preceding account name must be changed based on the actual account name.