Did you forget to set your database passwords to never expire? Don’t worry, it’s a common mistake. If you’re facing the consequences of expired passwords 180 days later, follow these 5 easy steps to resolve the issue.
Start by using the “dba_users” view to identify the affected accounts, and then use a simple SQL command to fix the problem.
Contents
- 1 For DBAs: How to Fix Expired Passwords on Newly Created Databases in 5 Easy Steps”
- 1.0.1 1. Identify Affected Accounts with this Simple SQL Command: Check dba_users View
- 1.0.2 2. “Reset Passwords for Locked Accounts: Tips for Finding Lost Passwords in Weblogic 12.2”
- 1.0.3 3. Unlock Users with Ease: Simple Command to Use Once Password is Found”
- 1.0.4 4. Prevent Future Password Issues: “Create a New Profile with Unlimited Password Lifetime”
- 1.0.5 5. Last Step: Add your users to this new profile:
- 2 Prevent Future Headaches: Set Up a Monitoring Query to detect Users with a Default Profile
For DBAs: How to Fix Expired Passwords on Newly Created Databases in 5 Easy Steps”
1. Identify Affected Accounts with this Simple SQL Command: Check dba_users View
To identify which accounts are affected by a certain issue, use this simple SQL command that checks the “dba_users” view. It’s a quick and easy solution that can save you time and effort.
select * from dba_users where ORACLE_MAINTAINED=’N’ AND PROFILE=’DEFAULT’ AND ACCOUNT_STATUS!=’OPEN’ ORDER BY USERNAME ASC;
2. “Reset Passwords for Locked Accounts: Tips for Finding Lost Passwords in Weblogic 12.2”
After running a command to check the “dba_users” view, you may discover that certain accounts need their passwords reset. If the account is also locked, you will need to set a new password.
This can be difficult if the password configuration is unknown, especially if there are multiple application servers involved.
A possible solution is to follow the “Decrypt Lost Passwords of Weblogic 12.2“ article to locate the password on a Weblogic server. For other middleware products, you’ll need to conduct further research.
3. Unlock Users with Ease: Simple Command to Use Once Password is Found”
alter user USERNAME identified by PASSWORD ACCOUNT UNLOCK;
4. Prevent Future Password Issues: “Create a New Profile with Unlimited Password Lifetime”
Why bother resolving an issue only to have it resurface in 180 days? To avoid this hassle in the future, it’s recommended to create a new profile with an unlimited password lifetime. This simple step can save you time and effort in the long run.
create profile PW_NEV_EXP limit PASSWORD_LIFE_TIME unlimited;
5. Last Step: Add your users to this new profile:
alter user USERNAME profile PW_NEV_EXP;
By creating a new profile with an unlimited password lifetime, you can bid farewell to the hassle of dealing with expiring passwords. Say goodbye to the stress of password maintenance and enjoy a long-lasting password lifetime with ease.
Read also: Cannot connect to Node Manager [Security:090479] – Resolve WLSTException
Prevent Future Headaches: Set Up a Monitoring Query to detect Users with a Default Profile
After creating a new profile with an unlimited password lifetime, it’s recommended to set up a monitoring query that checks for users with the DEFAULT profile. This will help you detect potential issues in the future and prevent expiring passwords from becoming a recurring problem.
By following these simple steps, you can fix expiring password issues and keep your database running smoothly. Remember to always double-check the password lifetime settings when creating new users to avoid any oversights.
Read also: Get Started with RMAN: A Comprehensive Beginner’s Guide to Oracle’s Backup and Recovery Tool
0 Comments