Something I discovered recently is that the DEFAULT profile for Oracle 11g sets the PASSWORD_LIFE_TIME to 180 instead of UNLIMTED by default. Applications will encounter an "ORA-28002: the password will expire within X days" error message if you keep the default value.
To change the PASSWORD_LIFE_TIME, you:
ALTER PROFILE default LIMIT password_life_time UNLIMITED;
One thing to keep in mind is that when you first encounter the ORA-28002 error, your dba_users.account_status will go into a "EXPIRED(GRACE)" state. You can "change" that users password to the same password it is now to clear it.
skip to main |
skip to sidebar
Oracle, MySQL, and IT Related stuff from the front lines.
Facebook Badge
Pageviews past week
Contributors
Best of (IMHO)
- Metalink Favorites
- Backup Top 11
- MySQL to an Oracle DBA, Part I
- MySQL to an Oracle DBA, Part II
- MySQL to an Oracle DBA, Part III
- MySQL to an Oracle DBA, Part IV
- Before Insert, Part I
- Before Insert, Part II
- Wicked ORA-27054, Part I
- Wicked ORA-27054, solved
- Trace It!
- Top N
- Setting up Multiple Listeners
4 comments:
join the club ;-) I had this one in production ;-( a couple of months ago
I had the pure luck my first 'test' DB (a playground) was alive for more than 3 months. So I could learn and adapt the installation procedures the easy way.
I failed to mention that an upgraded DB (at least using the manual method) doesn't set this same profile value. So it was only my new 11g dbs that got created from dbua.
yes... that can make app users, which each of user is locked.
I had the issue too and changed default profile -)
Post a Comment