Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 
 

ORA-28000: the account is locked tips

Oracle Error Tips by Burleson Consulting

 

Oracle docs note this about ORA-28000:

 

ORA-28000: the account is locked
Cause: The user has entered wrong password consequently for maximum number of times specified by the user"s profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account
Action: Wait for PASSWORD_LOCK_TIME or contact DBA

"The DBSNMP Account Becomes Locked And Database Shows A Status Of Down With A Metric Collection Error Of 'Ora-28000' " occurring in Enterprise Manager Grid Control 10.1-10.2.  ORA-28000 in DBSNMP is shown when DBSNMP is locked when trying to navigate to Database Monitoring Configuration page with the error:

error java.sql.SQLException: ORA-28000: the account is locked

This can also be shown when as the console is running, yet the database shows a down status with this error:

ORA-28000: the account
is locked (DBD ERROR: OCISessionBegin).

Sporadic at first, if the password is reset, the DBSNMP is locked daily.

Stored in the targets.xml file, if the dbsnmp password is not in sync with the reset DBSNMP password, ORA-28000 will be thrown. If this happens, the Agent account will be locked because it has attempted to logon to the database incorrectly a certain amount of times, and ORA-28000 will become a problem.

ORA-28000 can also occur if there is a service such as 9i Intelligent Agent trying to connect as DBSNMP with an invalid password, even if the DB target monitoring credentials are valid. 

In trying to resolve ORA-28000, keep in mind that FAILED_LOGIN_ATTEMPTS is maxed at 10 because DBSNMP has a default profile, after the 10 have been maxed, the account will lock.

Resolving ORA-28000 consists of a few steps, beginning with making sure you check the DB Target in EM Grid Console monitoring credentials are correct:

Navigation path:TARGETS > DATABASE > (DB_TARGET_NAME) > MONITORING
CONFIGURATION > TEST CONNECTION

If this fails, unlock DBSNMP account, and hit the Database target to Monitoring Configuration, set your DBSNMP password as the same as the password that you used upon verifying the credentials above. 

However, if ORA-28000 continues occurring after the credentials have been correctly set, make sure that all services which are connecting as DBSNMP have the correct passwords.  You might want to even make a different DBDNMP monitoring configuration profile using the following command after you have logged on to the Database as sysdba:

CREATE PROFILE MONITORING_PROFILE LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;ALTER USER DBSNMP PROFILE MONITORING_PROFILE;

To resolve ORA-28000 you can request that the administrator unlocks the account using something like the below, the user name is 'scott' and password is 'tiger' as an example:

SQL> alter user scott identified by tiger account unlock;

ORA-28000 has been thrown because during the installation, all of the existing accounts, with exception to sys and system, are defaulted as locked.  This being so, you can also try unlocking these accounts to resolve ORA-28000


 

 

  

 
  
 
 
 

 
 
 

Oracle training Excel
 
Oracle performance tuning software 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright ? 1996 -  2014

All rights reserved by Burleson

Oracle ? is the registered trademark of Oracle Corporation.


Hit Counter