ORA-28000

C:\Documents and Settings\anacondauser>sqlplus
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Apr 17 16:37:59 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: scott
Enter password:*-------------------------->tiger*
ERROR:
ORA-28000: the account is locked
Enter user-name: sys /as sysdba
Enter password:
Connected to:
Oracle Database 10g Release 10.2.0.1.0 - Production
SQL> alter user scott identified by tiger account unlock
2
SQL> define
DEFINE _DATE           = "17-APR-09" (CHAR)
DEFINE CONNECTIDENTIFIER = "orcl" (CHAR)
DEFINE _USER           = "SYS" (CHAR)
DEFINE _PRIVILEGE      = "AS SYSDBA" (CHAR)
DEFINE SQLPLUSRELEASE = "1002000100" (CHAR)
DEFINE _EDITOR         = "Notepad" (CHAR)
DEFINE OVERSION = "Oracle Database 10g Release 10.2.0.1.0 - Production" (
CHAR)
DEFINE ORELEASE = "1002000100" (CHAR)
SQL> quit
Disconnected from Oracle Database 10g Release 10.2.0.1.0 - Production
C:\Documents and Settings\anacondauser>sqlplus
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Apr 17 16:39:52 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: scott
Enter password:
ERROR:
ORA-28000: the account is locked
Enter user-name:
_// how can I unlock scott tiger on oca10g +xp pro(env settings checked) ?_                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Interesting,
What's the status when you do the unlocking from the sys account?
Show us the output of
E:\Documents and Settings\aristadba>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Apr 17 19:23:21 2009
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> alter user scott identified by tiger account unlock;
User altered.
SQL> desc dba_users
Name                                      Null?    Type
USERNAME                                  NOT NULL VARCHAR2(30)
USER_ID                                   NOT NULL NUMBER
PASSWORD                                           VARCHAR2(30)
ACCOUNT_STATUS                            NOT NULL VARCHAR2(32)
LOCK_DATE                                          DATE
EXPIRY_DATE                                        DATE
DEFAULT_TABLESPACE                        NOT NULL VARCHAR2(30)
TEMPORARY_TABLESPACE                      NOT NULL VARCHAR2(30)
CREATED                                   NOT NULL DATE
PROFILE                                   NOT NULL VARCHAR2(30)
INITIAL_RSRC_CONSUMER_GROUP                        VARCHAR2(30)
EXTERNAL_NAME                                      VARCHAR2(4000)
SQL> select username, account_status from dba_users where lower(username)='scott';
USERNAME                       ACCOUNT_STATUS
SCOTT                          OPEN
SQL>HTH
Aman....

Similar Messages

  • Problem with ora-28000 error

    Hi all,
    I got a problem with ORA-28000 in my form. In my app, it allows user to try maximum 3 time to logon, if the user fails, his/her user will be locked. The problem is, when Oracle locked that user, in on-error trigger I cannot catch that error and show the error message.
    Anybody, please give me a hand.
    Thank alot

    I put code (in the on-error trigger) here. please have look, thanks again.
    IN_ERR_CODE NUMBER := ERROR_CODE;
    BEGIN
         IF(IN_ERR_CODE = 28001) THEN
         ELSIF (IN_ERR_CODE = 28002) THEN
         ELSIF (IN_ERR_CODE = 28011) THEN
         ELSIF (IN_ERR_CODE = 28000) THEN
              MESSAGE(ERROR_TEXT);
              --LEAVE_FORM;
              --clear_form(no_validate);
              --RAISE FORM_TRIGGER_FAILURE;
              --EXIT_FORM(NO_VALIDATE);
         END IF;
    END;

  • Help required with Ora-28000 Error, Account is Locked

    Hello all,
    I have an user who is getting ORA - 28000, Account is Locked Error, while connecting to an instance, she has connected to this instance successfully several times earlier. Myself and several other users are able to connect to the same instance.
    How to resolve this issue and help the user to get connected to that instance successfully, please advise me.
    Thanks a lot for cooperation in advance.
    Regards,
    Suranjita

    You can run the following in sql plus
    alter user username account unlock;
    to unclock the account
    Regards

  • How to trap ora-28000 (account is locked) from a remote db in pl/sql ??

    i need to trap an ora-28000 (account is locked) exception comming from a remote db in my pl/sql block.
    something like ...
    declare
    account_locked exception;
    pragma exception_init(account_locked,-28000);
    e number;
    begin
    begin     
    select dummy into e from dual@remote;
    -- assign a query to a ref cursor
    exception when acount_locked then
    -- assign a different query to a ref cursor (not invloving the remote table)
    end;
    end;
    /

    Here example, from local 10.2.0.3 to remote 8.1.7.4 :
    SQL> conn system/demo102@demo102
    Connected.
    SQL> create database link mydbl connect to scott identified by tiger using 'demo817';
    Database link created.
    SQL> create or replace procedure myproc
      2  is
      3    account_locked exception;
      4    pragma exception_init(account_locked,-28000);
      5    e number;
      6  begin
      7    select count(*) into e from emp@mydbl;
      8    dbms_output.put_line('ALL WORKD FINE');
      9  exception when account_locked then dbms_output.put_line('ACCOUNT LOCKED WAS CATCHED');
    10            when others then        dbms_output.put_line('ACCOUNT LOCKED WAS NOT CATCHED');
    11  end;
    12  /
    Procedure created.
    SQL> conn system/manager@demo817
    Connected.
    SQL> alter user scott account lock;
    User altered.
    SQL> conn system/demo102@demo102
    Connected.
    SQL> set serveroutput on
    SQL> exec myproc
    ACCOUNT LOCKED WAS CATCHED
    PL/SQL procedure successfully completed.
    SQL> Here example, from local 8.1.7.4 to remote 10.2.0.3, I got the same error as your, but nothing to do with account locked or not, need to set to FALSE the GLOBAL_NAMES on the 8i db :
    SQL> conn system/manager@demo817
    Connected.
    SQL> create database link mydbl connect to scott identified by demo102 using 'demo102';
    Database link created.
    SQL> create or replace procedure myproc
      2  is
      3    account_locked exception;
      4    pragma exception_init(account_locked,-28000);
      5    e number;
      6  begin
      7    select count(*) into e from emp@mydbl;
      8    dbms_output.put_line('ALL WORKD FINE');
      9  exception when account_locked then dbms_output.put_line('ACCOUNT LOCKED WAS CATCHED');
    10            when others then        dbms_output.put_line('ACCOUNT LOCKED WAS NOT CATCHED');
    11  end;
    12  /
    create or replace procedure myproc
    ERROR at line 1:
    ORA-04052: error occurred when looking up remote object
    [email protected]
    ORA-00604: error occurred at recursive SQL level 1
    ORA-02085: database link MYDBL.US.ORACLE.COM connects to
    DEMO102.REGRESS.RDBMS.DEV.US.ORACLE.COM
    SQL> alter system set global_names=false;
    System altered.
    SQL> create or replace procedure myproc
      2  is
      3    account_locked exception;
      4    pragma exception_init(account_locked,-28000);
      5    e number;
      6  begin
      7    select count(*) into e from emp@mydbl;
      8    dbms_output.put_line('ALL WORKD FINE');
      9  exception when account_locked then dbms_output.put_line('ACCOUNT LOCKED WAS CATCHED');
    10            when others then        dbms_output.put_line('ACCOUNT LOCKED WAS NOT CATCHED');
    11  end;
    12  /
    Procedure created.
    SQL> conn system/demo102@demo102
    Connected.
    SQL> alter user scott account lock;
    User altered.
    SQL> conn system/manager@demo817
    Connected.
    SQL> set serveroutput on
    SQL> exec myproc
    ACCOUNT LOCKED WAS CATCHED
    PL/SQL procedure successfully completed.
    SQL> HTH,
    Nicolas.

  • ORA-28000: the account is locked Error

    Hello ---
    I'm trying to set up a data source to an 11g DB from WLS 11gR1. When I go to test it I get the following error even though the account is definitely not locked :
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    Truncated. see log file for complete stacktrace
    Caused By: weblogic.common.ResourceException: ORA-28000: the account is locked
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:479)
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:173)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:244)
    Truncated. see log file for complete stacktrace
    Any ideas? Thanks!

    Hi. Please add your details to this program and run it in that environment.
    Thanks,
    Joe
    import java.sql.*;
    import java.util.*;
    import javax.sql.*;
    import java.lang.reflect.Method;
    public class thinXACon {
    public static void main (String argv[]) {
    String UserName = "myUser";
    String Password = "myPassword";
    String SID = "mySID";
    String ServerName = "myDBMSBox";
    String PortNumber = "1588";
    String URL = "jdbc:oracle:thin:@" + ServerName + ":" + PortNumber + ":" + SID;
    try {
    // load XA driver and get connection
    oracle.jdbc.xa.client.OracleXADataSource ods = new oracle.jdbc.xa.client.OracleXADataSource();
    initProp(ods, "User", UserName);
    initProp(ods, "Password", Password);
    initProp(ods, "SID", SID);
    initProp(ods, "PortNumber", PortNumber);
    initProp(ods, "ServerName", ServerName);
    initProp(ods, "URL", URL);
    XAConnection xaConn = ods.getXAConnection();
    } catch (Exception e) {
    e.printStackTrace ();
    private static void initProp(Object ds, String propName, Object value) {
    try {
    Method[] meths = ds.getClass().getMethods();
    Method meth = null;
    String setterName = "set" + propName;
    Class paramType = null;
    for (int i = 0; i < meths.length; i++) {
    if (meths.getName().equalsIgnoreCase(setterName) &&
    meths[i].getParameterTypes().length == 1) {
    meth = meths[i];
    paramType = (meths[i].getParameterTypes())[0];
    break;
    if (meth != null) {
    Object val = value;
    if (value instanceof String) {
    if (paramType == int.class) {
    val = Integer.valueOf((String)value);
    } else if (paramType == boolean.class) {
    val = Boolean.valueOf((String)value);
    meth.invoke(ds, new Object[]{val});
    } else {
    meth = ds.getClass().getMethod(
    "setProperty", new Class[]{String.class, Object.class});
    meth.invoke(ds, new Object[]{propName, value});
    } catch (Exception ignore) { }

  • ORA-28000: the account is locked  Connection : false

    Now if I chnage my java code a little bit I am getting this error.
    ORA-28000: the account is locked
    Connection : false
    Connection is not established.
    Please can someone explain what is wrong here?

    ORA-28000
    Error: 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 database administrator has locked the account.
    Action: Wait for PASSWORD_LOCK_TIME or contact the database administrator
    To unlock an user manually:
    ALTER USER username ACCOUNT UNLOCK;
    to change his password:
    alter user username identified by new_password;
    Edited by: Fran on 26-nov-2012 3:22

  • ORA-28000: the account is locked error getting frequently

    Hi Team,
    We are getting ORA-28000: the account is locked while login.We unlocked the user and we tried to change the password as well but no luck.Can anyone please suggest on this..
    My db version is 10.2.0.3.0
    Thanks
    Edited by: Nabin on Nov 26, 2012 3:20 AM

    ORA-28000
    Error: 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 database administrator has locked the account.
    Action: Wait for PASSWORD_LOCK_TIME or contact the database administrator
    To unlock an user manually:
    ALTER USER username ACCOUNT UNLOCK;
    to change his password:
    alter user username identified by new_password;
    Edited by: Fran on 26-nov-2012 3:22

  • OEM 10G and ORA-28000: the account is locked

    windows xp 2; 10G base
    Get ORA-28000: the account is locked when starting database from the browser?
    TIA

    first open the account and change password
    in sql plus conn / as sysdba
    SQL> alter user scott indentified by tiger account unlock;
    then try to login

  • SRKIM: r11.5.10:Patch 적용 시 Ora-28000 account locked on the apps account

    Purpose
    Release 11.5.10
    adpatch 로 patch 적용 시 Ora-28000 account locked on the apps account Error에 대한 solution을 알아 보도록 한다.
    Symptom
    adpatch 로 patch 적용 시 아래와 같은 error 가 발생 하면서 더 이상 patch 작업을 진행 할 수가 없다.
    Ora-28000 account locked on the apps account Error
    Solution
    해당 error 는 apps user 에 대한 password attempt 가 profile 에 지정된 limit 을 초과 해서 해당 account 에 lock 이 걸려 발생하는 error 이므로 아래와 같이 변경을 해 주도록 한다.
    1. 아래 sql 로 profile option 설정을 확인 한다.
    select PROFILE, RESOURCE_NAME, RESOURCE_TYPE, LIMIT
    from dba_profiles
    where profile='AD_PATCH_MONITOR_PROFILE';
    2. 1번 sql 수행 시 limit 이 설정 되어 있음이 확인 되면 아래와 같이 조치 한다.
    SQL> alter profile AD_PATCH_MONITOR_PROFILE limit failed_login_attempts unlimited;
    SQL> alter profile default limit failed_login_attempts unlimited password_lock_time 1/1440;
    SQL> alter user apps account unlock;
    -- 현재 apps account 가 lock 이 발생한 상태 이므로 unlock 작업도 수행 해 준다.
    3. 다시 adpatch 작업을 수행 한다.
    Reference
    Note. 420001.1 - adpatch Ora-28000 Account Locked apps

    Hi ,
    I've followed the below steps to update schema password please let me know if there is something wrong      
    1- Through web console I Navigated to Datasources "Summary of JDBC Data source " -> configuration then i ve changed schemaaa password for all the below data sources
    EDNDATASource
    EDNLocalTxDataSource
    mds-oim
    mds-owsm
    mds-soa
    oimJMSStoreDS
    oimOperationsDB
    OraSDPMDataSource
    SOADataSource
    SOALocaLTxtDataSource
    2- In the WebLogic Administrative console, navigate to Security Realms, myrealm, and then Providers.
    - Click OIMAuthenticationProvider
    - Click Provider Specific.
    -In the DBPassword field, enter the new Oracle Identity Manager database schema password
    3. Change domain credential store configuration:
    - Login to Enterprise Manager by using the following URL http://ADMIN_SERVER/em
    - Navigate to Weblogic Domain, and then DOMAIN_NAME.
    - Right click oim, and navigate to Security, Credentials, and then oim.
    - Select OIMSchemaPassword, and click Edit.
    - In the Password field, enter the new password, and click OK
    4. Restart the WLS AdminServer
    5. Start the SOA managed server

  • SQL*Loader-128: unable to begin a session ORA-28000: the account is locked

    Hi everyone,
    I am migrating from a SQL Server 2000 DB to Oracle 10g. I followed the migration tutorial and got all the way till the data migration process. The DB data capture scripts capture the data from the SQL Server successfully but i encounter the following error while i run the oracle_ctl.bat file on the Oracle side:
    SQL*Loader: Release 10.2.0.1.0 - Production on Tue Jun 9 14:08:27 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    SQL*Loader-128: unable to begin a session
    ORA-28000: the account is locked
    I checked the account and its unlocked and the user name/password combination is the correct one. All the log files have the same error messages. The user has all the required privileges.
    Any ideas why this might be happening ?
    Thanks,
    Amo.

    Hello,
    there may be several causes for this:
    1) account in grace period, it can login to sqlplus but could not logn with sqlldr
    2) kind of user being specified (sys as sysdba for example)
    Could you please paste first lines of modified batch file and
    output from select user and status in dba_users ?
    Try anyway to run the unlock command
    ALTER USER username ACCOUNT UNLOCK;
    Thanks
    Regards,
    Marcello
    Edited by: MGILIBER on Jun 12, 2009 3:02 AM

  • Ora-28000 (Account is Locked)

    After installation Oralce 10g ..it takes to this weblink
    http://192.168.1.135:1158/em/console/logon/logon...asking for username and password...
    In the normal mode i typed scott/tiger iam getting Ora 28000...What is the Username and password i have to give their...

    Did you create default schemas like HR, Scott etc. ? By default schemas like Scott, HR will be locked in 10g.
    Please login as DBA and unlock them.
    SQL> alter user scott
    account unlock;
    Did you remember the password for scott which you set while installation ? If not change it.
    SQL> alter user scott
    identified by user558229;
    FYI, the link you provided here is for enterprise manager. Please read about it here.
    http://download-east.oracle.com/docs/cd/B19306_01/em.102/b31949/toc.htm

  • ORA-28000 in Java program while account is not actually locked

    Hi all,
    we got error ORA-28000: the account is locked in Java program which connects to Oracle.
    But account is not locked, 'cause we can log in using Oracle SQL Developer.
    What can be wrong?

    I would bet my bottom dollar that you are not logging in to the same account in the same database when you connect via SQL Developer that the Java application is connecting to.  Perhaps there is a difference in the TNS configuration the two tools are using that makes it look like they should be connecting to the same database.  Perhaps the Java application is not using the username that you expect, etc.
    Have you enabled auditing of both successful and failed connections to this database to see whether you see both connections and whether they are using the same account?
    I suppose it is possible that you've found a bug that needs to be reported to Oracle Support where an incorrect error message is returned.  But it is vastly more likely that Oracle is right and you've made a mistake.
    Justin    

  • ERROR - ORA-28000: the account is locked

    I've successfully installed Oracle 10g standard edition in my PC...And when i tried to log in into isql plus environment with user name scott and password tiger it flashes ORA-2800 error and shows that the account is locked...pls tell me what to do to unlock that account and so that i can work in ISqlplus environment....

    Hello,
    there is a space after /
    sqlplus / as sysdba will work since 9i before you it should sqlplus "/ as sysdba"
    look on the spaces.
    I will also suggest to alter user <username> identified by <password> account unlock;
    The reason is why ? Id like default passwords on systems.
    regards
    Peter

  • Could not create pool connection.  ORA-28000: the account is locked

    hi
    here what i did
    i was running my ADF page on 11g weblog normally and i tried to deploy it, and this error occured when deploying it
    and also now i cannot run my page from JDeveloper and the same error occure too
    please so so so urgent
    thanks

    This can happen on the first launch of the application on a reel weblogic server.
    This code will solve your problem. As SYSDBA :
    ALTER USER yourUserName ACCOUNT UNLOCK;
    regards
    Luc-

  • ORA-28000: The account is locked

    hi, all I've tried to connect to db as sys more then 10 times and now I am banned^).
    But I tried this to know how much time it will take:
    SELECT * FROM DBA_PROFILES
    WHERE profile = 'DEFAULT' AND resource_name = 'PASSWORD_LOCK_TIME'
    UNLIMITED
    What should I do? Now I am working as SYS with sysdba privileges.

    Hi,
    Use
    SQL> alter user "USER" account unlock.
    Regards
    Jafar

Maybe you are looking for