【DG】DG备库报ORA-28000: the account is locked的解决办法

最新推荐文章于 2022-05-17 14:47:35 发布
最新推荐文章于 2022-05-17 14:47:35 发布
阅读量557 收藏
点赞数
文章标签： 数据库 面试
【DG】DG备库报ORA-28000: the account is locked的解决办法

测试用户为lhr
现象： 主备库的lhr用户的状态都是OPEN，但是，备库连接的时候报ORA-28000: the account is locked错误。在主库执行“alter user lhr identified by lhr account unlock;”同步到备库也不能解决，在备库该命令不能执行。
解决：重启DG环境的备库实例即可
参考：ORA-28000 On Active Data Guard (文档 ID 1922621.1)
用户密码请参考：http://blog.itpub.net/26736162/viewspace-2129595/

 

 主库

SYS@oradg11g > alter user lhr identified by lhr account unlock;


User altered.


SYS@oradg11g > 
SYS@oradg11g > 
SYS@oradg11g > 
SYS@oradg11g > conn lhr/lhr
Connected.
LHR@oradg11g >  alter user lhr identified by lhr account unlock;


User altered.

LHR@oradg11g > conn lhr/lhr
Connected.
LHR@oradg11g > select * from dba_users where USERNAME='LHR';


USERNAME                          USER_ID PASSWORD                       ACCOUNT_STATUS                   LOCK_DATE           EXPIRY_DATE         DEFAULT_TABLESPACE             TEMPORARY_TABLESPACE           CREATED       PROFILE                        INITIAL_RSRC_CONSUMER_GROUP    EXTERNAL_NAME                                                                                                                             PASSWORD E AUTHENTI
------------------------------ ---------- ------------------------------ -------------------------------- ------------------- ------------------- ------------------------------ ------------------------------ ------------------- ------------------------------ ------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------- - --------
LHR                                    95                                OPEN                                                 2018-03-24 11:49:18 USERS                          TEMP                           2017-04-03 21:01:18 DEFAULT                          DEFAULT_CONSUMER_GROUP                                                                                                                                           10G 11G  N PASSWORD

 


备库：

 

LHR@oradgphy >  conn lhr/aa
ERROR:
ORA-01017: invalid username/password; logon denied




Warning: You are no longer connected to ORACLE.
@ >  conn lhr/aa
ERROR:
ORA-01017: invalid username/password; logon denied




@ >  conn lhr/aa
ERROR:
ORA-01017: invalid username/password; logon denied




@ >  conn lhr/aa
 conn lhr/aa
ERROR:
ORA-01017: invalid username/password; logon denied




@ > 
 conn lhr/aa




ERROR:
ORA-01017: invalid username/password; logon denied




@ > @ >  conn lhr/aa




 conn lhr/aa




 conn lhr/aa




ERROR:
ORA-01017: invalid username/password; logon denied




@ > @ > @ >  conn lhr/aa


 conn lhr/aa




 conn lhr/aa




ERROR:
ORA-01017: invalid username/password; logon denied




@ > @ > @ > ERROR:
ORA-01017: invalid username/password; logon denied




@ > @ > @ > ERROR:
ORA-01017: invalid username/password; logon denied




@ > @ > @ >  conn lhr/aa






ERROR:
ORA-28000: the account is locked




@ > @ > ERROR:
ORA-28000: the account is locked




@ > @ > @ > ERROR:
ORA-28000: the account is locked




@ > @ > @ > ERROR:
ORA-28000: the account is locked




@ > @ > @ > @ >  conn lhr/aa
ERROR:
ORA-28000: the account is locked




@ > 
@ > 
@ > conn lhr/lhr
ERROR:
ORA-28000: the account is locked




@ >  conn lhr/lhr
ERROR:
ORA-28000: the account is locked




@ >  select * from dba_users where USERNAME='LHR';
SP2-0640: Not connected
@ > 
@ > conn  / as sysdba
Connected.
SYS@oradgphy >  select * from dba_users where USERNAME='LHR';


USERNAME                          USER_ID PASSWORD                       ACCOUNT_STATUS                   LOCK_DATE           EXPIRY_DATE         DEFAULT_TABLESPACE             TEMPORARY_TABLESPACE           CREATED       PROFILE                        INITIAL_RSRC_CONSUMER_GROUP    EXTERNAL_NAME                                                                                                                             PASSWORD E AUTHENTI
------------------------------ ---------- ------------------------------ -------------------------------- ------------------- ------------------- ------------------------------ ------------------------------ ------------------- ------------------------------ ------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------- - --------
LHR                                    95                                OPEN                                                 2018-03-24 11:49:18 USERS                          TEMP                           2017-04-03 21:01:18 DEFAULT                          DEFAULT_CONSUMER_GROUP                                                                                                                                           10G 11G  N PASSWORD


SYS@oradgphy >  conn lhr/lhr
ERROR:
ORA-28000: the account is locked




Warning: You are no longer connected to ORACLE.
@ > conn / as sysdba
Connected.
SYS@oradgphy > startup force
ORACLE instance started.


Total System Global Area  242171904 bytes
Fixed Size                  2227256 bytes
Variable Size             197133256 bytes
Database Buffers           37748736 bytes
Redo Buffers                5062656 bytes
Database mounted.
ORA-10458: standby database requires recovery
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1: '/u01/app/oracle/oradata/oradgphy/system01.dbf'




SYS@oradgphy > 
SYS@oradgphy > 
SYS@oradgphy > alter database recover managed standby database using current logfile disconnect from session;










Database altered.


SYS@oradgphy > SYS@oradgphy > SYS@oradgphy > SYS@oradgphy > SYS@oradgphy > 
SYS@oradgphy > 
SYS@oradgphy > alter database open;
alter database open
*
ERROR at line 1:
ORA-10456: cannot open standby database; media recovery session may be in progress




SYS@oradgphy >  alter database recover managed standby database cancel;


Database altered.


SYS@oradgphy > alter database open;
alter database open
*
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1: '/u01/app/oracle/oradata/oradgphy/system01.dbf'




SYS@oradgphy > conn lhr/lhr
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0




Warning: You are no longer connected to ORACLE.
@ > conn / as sysdba
Connected.
SYS@oradgphy > select value from v$diag_info;


VALUE
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TRUE
/u01/app/oracle
/u01/app/oracle/diag/rdbms/oradgphy/oradgphy
/u01/app/oracle/diag/rdbms/oradgphy/oradgphy/trace
/u01/app/oracle/diag/rdbms/oradgphy/oradgphy/alert
/u01/app/oracle/diag/rdbms/oradgphy/oradgphy/incident
/u01/app/oracle/diag/rdbms/oradgphy/oradgphy/cdump
/u01/app/oracle/diag/rdbms/oradgphy/oradgphy/hm
/u01/app/oracle/diag/rdbms/oradgphy/oradgphy/trace/oradgphy_ora_8346.trc
0
0


11 rows selected.


SYS@oradgphy > 
SYS@oradgphy > 
SYS@oradgphy > alter database recover managed standby database using current logfile disconnect from session;






Database altered.


SYS@oradgphy > SYS@oradgphy > SYS@oradgphy > col name for a100
SYS@oradgphy > set linesize 9999  pagesize 9999
SYS@oradgphy > col NEXT_CHANGE# for 999999999999999
SYS@oradgphy > SELECT THREAD#,
  2         NAME,
  3         sequence#,
  4         archived,
  5         applied, 
  6         a.NEXT_CHANGE#
  7  FROM   v$archived_log a
  8  WHERE  a.sequence# >= (select max(b.sequence#)-3 from v$log b where b.THREAD#=a.THREAD# )
  9  AND    resetlogs_change# = (SELECT d.RESETLOGS_CHANGE# FROM v$database d)
 10  ORDER  BY a.THREAD#,
 11            a.sequence#;


   THREAD# NAME                                                                                                  SEQUENCE# ARC APPLIED       NEXT_CHANGE#
---------- ---------------------------------------------------------------------------------------------------- ---------- --- --------- ----------------
         1 /u01/app/oracle/flash_recovery_area/ORADGPHY/archivelog/2017_09_25/o1_mf_1_164_dwjyf088_.arc                164 YES YES                3218670
         1 /u01/app/oracle/flash_recovery_area/ORADGPHY/archivelog/2017_09_25/o1_mf_1_165_dwjydkp8_.arc                165 YES YES                3221768
         1 /u01/app/oracle/flash_recovery_area/ORADGPHY/archivelog/2017_09_25/o1_mf_1_166_dwjyf828_.arc                166 YES IN-MEMORY          3221806


SYS@oradgphy >  archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     162
Next log sequence to archive   0
Current log sequence           167
SYS@oradgphy > 10046
SP2-0226: Invalid line number
SYS@oradgphy > col name for a100
SYS@oradgphy > set linesize 9999  pagesize 9999
SYS@oradgphy > col NEXT_CHANGE# for 999999999999999
SYS@oradgphy > SELECT THREAD#,
  2         NAME,
  3         sequence#,
  4         archived,
  5         applied, 
  6         a.NEXT_CHANGE#
  7  FROM   v$archived_log a
  8  WHERE  a.sequence# >= (select max(b.sequence#)-3 from v$log b where b.THREAD#=a.THREAD# )
  9  AND    resetlogs_change# = (SELECT d.RESETLOGS_CHANGE# FROM v$database d)
 10  ORDER  BY a.THREAD#,
 11            a.sequence#;


   THREAD# NAME                                                                                                  SEQUENCE# ARC APPLIED       NEXT_CHANGE#
---------- ---------------------------------------------------------------------------------------------------- ---------- --- --------- ----------------
         1 /u01/app/oracle/flash_recovery_area/ORADGPHY/archivelog/2017_09_25/o1_mf_1_164_dwjyf088_.arc                164 YES YES                3218670
         1 /u01/app/oracle/flash_recovery_area/ORADGPHY/archivelog/2017_09_25/o1_mf_1_165_dwjydkp8_.arc                165 YES YES                3221768
         1 /u01/app/oracle/flash_recovery_area/ORADGPHY/archivelog/2017_09_25/o1_mf_1_166_dwjyf828_.arc                166 YES IN-MEMORY          3221806


SYS@oradgphy >  alter database recover managed standby database using current logfile disconnect from session;
 alter database recover managed standby database using current logfile disconnect from session
*
ERROR at line 1:
ORA-01153: an incompatible media recovery is active




SYS@oradgphy >  alter database recover managed standby database cancel;
































[1]+  Stopped                 rlwrap sqlplus / as sysdba
[oracle@rhel6lhr ~]$ 
[oracle@rhel6lhr ~]$ 
[oracle@rhel6lhr ~]$ 
[oracle@rhel6lhr ~]$ 
[oracle@rhel6lhr ~]$ sqlplus / as sysdba


SQL*Plus: Release 11.2.0.3.0 Production on Mon Sep 25 11:59:00 2017


Copyright (c) 1982, 2011, Oracle.  All rights reserved.




Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options


SYS@oradgphy > alter database open readonly;
alter database open readonly
                    *
ERROR at line 1:
ORA-02288: invalid OPEN mode




SYS@oradgphy > 
SYS@oradgphy > 
SYS@oradgphy > alter database open read only;


Database altered.


SYS@oradgphy > conn lhr/lhr
Connected.

 

 






ORA-28000 On Active Data Guard (文档 ID 1922621.1)

In this Document

Symptoms
Cause
Solution
References


APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

SYMPTOMS

Noticed one user account was locked in primary and its Active Data Guard instances. It was fine Primary Database after unlocking the User, but at the Active Data Guard Standby Database, it was showing ORA-28000 that the account is still locked. Followed

Note 1600401.1: ORA-28000 "the account is locked" in the standby database, even after the account was unlocked in the primary

but it is still unlocked and user can not connect to standby database. Here is log:

 

SQL> select name,database_role , open_mode from v$database ;

NAME DATABASE_ROLE OPEN_MODE
--------- ---------------- --------------------
ELFVRFI1 PHYSICAL STANDBY READ ONLY

SQL> select username,account_status from dba_users where username = 'A472033';

USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
A472033 LOCKED(TIMED)


SQL> alter user A472033 account unlock ;
SQL> alter user A472033 account unlock
*
ERROR at line 1:
ORA-28015: Account unlocked, but the database is open for read-only access

 

CAUSE

This issue is detailed in 
Bug 16345308: LOGGING INTO ADG STANDBY GETS ORA-28000: THE ACCOUT IS LOCKED. AND IS NOT

It is not a bug, but a limitation of an Active Data Guard READ ONLY Database 

 

SOLUTION

Regardless of how the account becomes locked once locked it will stay locked in the Active Data Guard standby that is open read only.
You may have an account profile that sets how many times an incorrect password can be used before the account is locked.
In this case the standby instance needs to be restarted to reflect the correct status of the account again in the primary.

Or the profile may lock the account after it times out depending on the settings.
You can then unlock the account in the primary and the data dictionary is updated, but that which locks the account in memory is not.
So again you must restart the ADG standby.  This is not a bug it is a limitation of a read only standby database.

The issues with applications that have Identity in the database and applications that have Identity in the front end app. 
The later is not a problem for this issues.  With Identity in the database it can be.

 

Per this note  Bug 17732353 - ORA-28000 "the account is locked" attempting to log in as a remote SYSDBA user if SYS account is locked (Doc ID 17732353.8)

it is fixed in 12.1 and 12.2

REFERENCES

BUG:16345308  - LOGGING INTO ADG STANDBY GETS ORA-28000: THE ACCOUT IS LOCKED. AND IS NOT.
NOTE:1600401.1  - ORA-28000 "the account is locked" in the standby database, even after the account was unlocked in the primary.
NOTE:17732353.8  - Bug 17732353 - ORA-28000 "the account is locked" attempting to log in as a remote SYSDBA user if SYS account is locked

Bug 16345308 : LOGGING INTO ADG STANDBY GETS ORA-28000: THE ACCOUT IS LOCKED. AND IS NOT.
单击此项可添加到收藏夹 通过电子邮件发送此文档的链接 可打印页 转到底部转到底部
 

Bug 属性

 
类型 B - Defect 已在产品版本中修复
严重性 2 - Severe Loss of Service 产品版本 11.2.0.3
状态 92 - Closed, Not a Bug 平台 212 - IBM AIX on POWER Systems (64-bit)
创建时间 2013-2-22 平台版本 6.1
更新时间 2017-8-24 基本 Bug N/A
数据库版本 11.2.0.3 影响平台 Generic
产品源 Oracle 与此 Bug 相关的知识, 补丁程序和 Bug
 

相关产品

 
产品线 Oracle Database Products 系列 Oracle Database Suite
区域 Oracle Database 产品 5 - Oracle Database - Enterprise Edition 
Hdr: 16345308 11.2.0.3 RDBMS 11.2.0.3 DATAGUARD_ACTV PRODID-5 PORTID-212 ORA-28000
Abstract: LOGGING INTO ADG STANDBY GETS ORA-28000: THE ACCOUT IS LOCKED.  AND IS NOT. *** 02/21/13 03:48 pm *** (ADD: Impact/Symptom->WRONG RESULT - INCOR...) *** 02/21/13 03:48 pm *** BUG TYPE CHOSEN
===============
Code
 
== Component: RDBMS ==
======================
DETAILED PROBLEM DESCRIPTION
============================
Customer has a user id they want to use in ADG standby. 
CRMPTSI
DBA_USERS show in the primary and the standby the account is open. 
The can log into the primary but logging into the standby gets
ORA-28000: the account is locked 
This account shows in dba_users that it is open not locked.
 
Although the account shows as open in the standby customer states
"We have just restarted the standby DB and it did unlock the user." they mean
they were then able to log in with the account. "We do wish to follow through
you asked. Alert logs from both primary and standby and the Opatch
lsinventory list"
 
But per the diagnostics below, it does not show as locked.
 
DIAGNOSTIC ANALYSIS
===================
on the primary 
SQL> select USERNAME, USER_ID, ACCOUNT_STATUS, LOCK_DATE, EXPIRY_DATE,
CREATED, PROFILE
  2  from dba_users where username = 'CRMPTSI'  ;
 
USERNAME                          USER_ID ACCOUNT_STATUS                  
LOCK_DATE          EXPIRY_DATE        CREATED            PROFILE             
                                               
------------------------------ ---------- --------------------------------
------------------ ------------------ ------------------
------------------------------                                      
CRMPTSI                               196 OPEN                               
                14-may-13 17:20:23 11-jul-12 17:51:47 PROFILE_SOX            
                                            
 
1 row selected.
 
SQL> 
Connected.
SQL> 
SQL> show user
USER is "CRMPTSI
 
On the standby
SQL> select USERNAME, USER_ID, ACCOUNT_STATUS, LOCK_DATE, EXPIRY_DATE,
CREATED, PROFILE
  2  from dba_users where username = 'CRMPTSI'  ;
 
USERNAME                          USER_ID ACCOUNT_STATUS                  
LOCK_DATE          EXPIRY_DATE        CREATED            PROFILE             
                                               
------------------------------ ---------- --------------------------------
------------------ ------------------ ------------------
------------------------------                                      
CRMPTSI                               196 OPEN                               
                14-may-13 17:20:23 11-jul-12 17:51:47 PROFILE_SOX            
                                            
 
1 row selected.
 
SQL> 
ERROR:
ORA-28000: the account is locked 
 
 
Warning: You are no longer connected to ORACLE.
SQL> 
 
I had them do this to get stack trace.  
In the standby:
Do this in one session and the connect in another
 
session 1:
oradebug setmypid ;
oradebug unlimit ;
oradebug event 10046 trace name context forever,level ;
alter system set events  '28000  trace name errorstack level 3';
exit
 
session 2
sqlplus
connect CRMPTSI/portugal_2013
 
exit
 
Standby profile
SELECT * FROM DBA_PROFILES where profile ='PROFILE_SOX' ;
 
PROFILE                   RESOURCE_NAME                    RESOURCE LIMIT    
------------------------- -------------------------------- -------- ---------
 
 
WORKAROUND?
===========
No
 
TECHNICAL IMPACT
================
The customer cannot use this account for ADG
 
RELATED ISSUES (bugs, forums, RFAs)
===================================
I find on bug at all on this stack trace related to ADG standby.
 
HOW OFTEN DOES THE ISSUE REPRODUCE AT CUSTOMER SITE?
====================================================
Always
 
DOES THE ISSUE REPRODUCE INTERNALLY?
====================================
No
 
IS A TESTCASE AVAILABLE?
========================
No
 
Link to IPS Package:
====================
not available *** 02/21/13 03:49 pm *** *** 02/21/13 10:56 pm *** (CHG: Sta->10) *** 02/21/13 10:56 pm *** *** 02/21/13 10:56 pm ***  *** 02/21/13 11:36 pm ***  *** 02/22/13 07:15 am *** *** 02/22/13 07:18 am *** (CHG: RDBMS Ver.-> 11.2.0.2 -> 11.2.0.3) *** 02/22/13 09:00 am *** *** 02/22/13 09:55 am *** *** 03/06/13 09:12 am *** (CHG: Sta->16) *** 03/06/13 09:12 am *** *** 03/07/13 01:17 am *** *** 03/07/13 01:19 am *** (CHG: Sta->32) *** 03/07/13 01:19 am *** Key Symptoms/Summary/Rediscovery:
Account status remains OPEN after a user's account is locked on a standby 
database.
 
Explain why this is not a bug:
The account status reflects that of the account on the primary database. *** 03/07/13 07:28 am *** *** 03/13/13 09:22 am *** (CHG: Sta->16) *** 03/13/13 09:22 am *** *** 03/13/13 09:36 am *** (CHG: Sta->32) *** 03/13/13 09:36 am *** *** 03/28/13 08:05 am *** *** 04/23/13 02:48 am *** *** 07/22/13 01:10 am *** (CHG: Sta->92) *** 08/13/13 07:59 pm *** *** 08/26/13 12:46 pm *** *** 12/23/13 12:41 am *** *** 02/26/14 01:52 am *** *** 03/03/14 03:33 pm *** *** 09/02/14 08:19 am *** *** 10/07/14 04:17 pm *** *** 07/27/15 11:08 pm *** *** 10/18/15 10:56 pm *** *** 10/27/15 11:34 am *** *** 08/22/16 12:19 am *** *** 10/02/16 11:28 pm *** *** 10/10/16 07:13 pm *** *** 10/16/16 02:47 pm *** *** 12/01/16 02:42 pm *** *** 12/09/16 05:13 am *** *** 02/09/17 04:08 pm *** *** 04/07/17 12:34 pm *** *** 08/12/17 06:34 pm *** *** 08/18/17 05:51 am *** *** 08/23/17 06:22 pm ***




About Me

.............................................................................................................................................

● 本文作者：小麦苗，部分内容整理自网络，若有侵权请联系小麦苗删除

● 本文在itpub（http://blog.itpub.net/26736162/abstract/1/）、博客园（http://www.cnblogs.com/lhrbest）和个人微信公众号（xiaomaimiaolhr）上有同步更新

● 本文itpub地址：http://blog.itpub.net/26736162/abstract/1/

● 本文博客园地址：http://www.cnblogs.com/lhrbest

● 本文pdf版、个人简介及小麦苗云盘地址：http://blog.itpub.net/26736162/viewspace-1624453/

● 数据库笔试面试题库及解答：http://blog.itpub.net/26736162/viewspace-2134706/

● DBA宝典今日头条号地址：http://www.toutiao.com/c/user/6401772890/#mid=1564638659405826

.............................................................................................................................................

● QQ群号：230161599（满）、618766405

● 微信群：可加我微信，我拉大家进群，非诚勿扰

● 联系我请加QQ好友（646634621），注明添加缘由

● 于 2017-09-01 09:00 ~ 2017-09-30 22:00 在魔都完成

● 文章内容来源于小麦苗的学习笔记，部分整理自网络，若有侵权或不当之处还请谅解

● 版权所有，欢迎分享本文，转载请保留出处

.............................................................................................................................................

● 小麦苗的微店：https://weidian.com/s/793741433?wfr=c&ifr=shopdetail

● 小麦苗出版的数据库类丛书：http://blog.itpub.net/26736162/viewspace-2142121/

.............................................................................................................................................

使用微信客户端扫描下面的二维码来关注小麦苗的微信公众号（xiaomaimiaolhr）及QQ群（DBA宝典），学习最实用的数据库技术。

   小麦苗的微信公众号      小麦苗的DBA宝典QQ群1     小麦苗的DBA宝典QQ群2        小麦苗的微店

.............................................................................................................................................

ico_mailme_02.png
 DBA笔试面试讲解群1
 DBA笔试面试讲解群2
 欢迎与我联系



来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/26736162/viewspace-2145402/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/26736162/viewspace-2145402/

coco3600
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
oracle 报错28000,Oracle11g报错ORA-28000theaccountislocked
weixin_39633276的博客
04-03 549
Oracle 11g 报错 ORA-28000 the account is locked，是由于oracle 11g中默认在default概要文件中设置了ldquo;PASSWORD_LIFE_TIM一、触发这个错误的原因及相关因素是由于Oracle 11g中默认在default概要文件中设置了“PASSWORD_LIFE_TIME=180天”所导致，在Oracle 11g中是存在密码过期问题的...
[重庆思庄每日技术分享]-DG备库用户被锁报ora-28000:the account is locked
XIANHUAFANG的博客
05-17 309
在备库上进行查询时，登录用户发现用户被锁定 报错：ora-28000:the account is locked 但SYS用户登陆后查看其用户状态为OPEN状态 一般是由bug导致的，是主库上修改了对应用户的密码，导致备库上的用户无法登录 解决方法： 1.可以尝试unlock用户 在备库端执行alter user account unlock;然后尝试登陆 SQL> conn / as sysdba Connected. SQL> alter user XXXX account
You are no longer connected to ORACLE
weixin_49687110的博客
11-04 2620
[oracle@localhost ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Tue Oct 27 16:10:14 2020 Copyright © 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production W
Warning: You are no longer connected to ORACLE.
Adela
06-11 1万+
Oracle安全性联系 SQL> alter user adela account lock; User altered. SQL> conn adela/SAP; ERROR: ORA-28000: the account is locked Warning: You are no longer connected to ORACLE.
Oracl数据库多个实例切换进行ora-28000用户账号锁定解锁
y2020520的博客
11-09 595
众所周知，Oracle数据库可以创建多个实例，每个实例可以创建多个表空间，每个表空间下可以创建多个用户（同时用户也属于表空间对应的实例）和数据库文件，用户可以创建多个表（每个表随机存储在一个或多个数据库文件中）。 当你使用plsql工具登录或者cmd命令登录时，被提示ORA-28000，用户账号被锁定。 需要进行以下操作才能够解锁，步骤如下： 步骤1：以dba超级管理员账号进行登录.（注意@后面跟的是SID实例名） sqlplus /@orcl as sysdba; 步骤2： 查询指定实例下的用户
【Oracle】数据库登陆错误：ORA-28000:the account is locked解决方法
小七的博客
07-06 3万+
问题描述 在连接Oracle数据库的时候出现了ORA-28000:the account is locked报错，登录账号被锁定，出现这种情况就需要将被锁定用户解锁。 解决方法 解锁方法就是通过用system账号登录数据库，然后修改被锁定账户状态，具体如下图所示： 输入命令依次为： sqlplus /nolog conn system账户名/system账户密码 alter user 需解锁的账户名 account unlock; 执行上面的命令之后，即可解锁账户 ......
oracle11g用户登录时被锁定问题的解决方法 （ora-28000 the account is locked）
09-09
最近在操作oracle11g的使用出现错误的现象：ora-28000 the account is locked,既用户无法登录问题，如何解决此问题呢？下面小编给大家带来了oracle11g用户登录时被锁定问题的解决方法，感兴趣的朋友一起看看吧
Oracle dbca时报：ORA-12547: TNS:lost contact错误的解决
12-16
最近在工作中遇到了一个问题，错误是Oracle dbca时报错：ORA-12547: TNS:lost contact，通过查找相关的资料终于找到了解决的方法，下面分享给大家，话不多说了，来一起看看详细的介绍吧。 环境： OS:RHEL6.5 x86-...
Mybatis出现ORA-00911: invalid character的解决办法
01-21
今天在项目中，使用Mybatis对oracle数据库进行操作的时候，报出ORA-00911: invalid character的错误，检查...以上所述是小编给大家介绍的Mybatis出现ORA-00911: invalid character的解决办法，希望对大家有所帮助，如果
ORA-28000错误的原因及解决办法
weixin_30872733的博客
11-01 844
当使用SQL*Plus登录时，Oracle数据库时提示“ORA-28000：帐号被锁定”。导致出现改错误的原因是：在oracle database 11g中，默认在default概要文件中设置了“FAILED_LOGIN_ATTEMPTS=10”，当输入密码错误次数达到设置值将导致此问题。 1.确认用户所使用的概要文件： SQL> select username,profile...
ORACLE数据库 某用户账户被锁定问题解决
ayt007的博客
05-17 2808
遇到的问题： [realestate][ERROR] [2022-05-17 14:27:11] com.alibaba.druid.pool.DruidDataSource$CreateConnectionThread.run(2469) | create connection SQLException, url: jdbc:p6spy:oracle:thin:@172.18.13.83:1521/orclxj, errorCode 28000, state 99999 java.sql.SQLExcep
Oracle 11g 密码过期被锁报 ORA-28000 the account is locked
09-10 149
一、触发这个错误的原因及相关因素 是由于oracle11g中默认在default概要文件中设置了“PASSWORD_LIFE_TIME=180天”所导致，在Oracle 11g中是 存在密码过期问题的...
ORA-01251错误oracle服务启动无法连接误删非法删除数据文件导致数据库不能打开ORA-01122 ORA-01251
IT小黑
12-20 2068
今天一同事找我，说他本地的数据库被他误删除了文件，导致不能打开，然给看看。 SQL> conn jjw/jjw ERROR: ORA-01033: Oracle initialization or shutdown in progress Warning: You are no longer connected to ORACLE. SQL> 数据库已经启动，但连接报错。如是，
oracle创建用户并授权
热门推荐
ly510587的博客
07-11 18万+
一、创建用户 登录到system用户以创建其他用户 创建的： create user username identified by password; 二、授权 在这里插入代码片
oracle 01251,非法删除数据文件导致数据库不能打开ORA-01122 ORA-01251
weixin_42306054的博客
04-04 133
今天一同事找我，说他本地的数据库被他误删除了文件，导致不能打开，然给看看。SQL> conn jjw/jjwERROR:ORA-01033: Oracle initialization or shutdown in progressWarning: You are no longer connected to ORACLE.SQL>数据库已经启动，但连接报错。如是，我重启一下，看报什么...
Oracle数据库用户锁定原因以及处理方式（ORA-28000）
weixin_33691817的博客
05-09 1559
现场在实施过程中，基于安全考虑（用户名和密码之前暴露给其他公司了），需要对用户密码进行修改。 修改过程很简单（alter user [username] identified by [password];），但是在修改之后出现该用户被锁定的问题。 原因：数据库参数文件中设置了输错密码的次数，登录时当输错密码的次数超过所设置的次数时，则锁住该用户。默认一般为10次。输错密码锁住用户的设计原因：防...
[Oracle11g] ORA-28000: the account is locked 的解决办法
u013623100的专栏
11-16 4194
用scott账户在PL/SQL中连接Oracle的时候，提示ORA-28000: the account is locked。 解决方案： 第一步：在%ORACLE_HOME%NETWORK\ADMIN目录中找到sqlnet.ora文件，其中%ORACLE_HOME%为Oracle的安装路径。 我的为：D:\app\haojiec\product\11.2.0\dbhome_1\NE
Eclipse line number
weixin_30873847的博客
09-20 186
转载于:https://www.cnblogs.com/kakaisgood/p/9679677.html
无法debug断点跟踪JDK源代码——missing line number attributes的解决方法
weixin_34148340的博客
06-22 431
在项目工程->Properties->Java Build Path->Libraries中导入的JRE System Library库里，给jar包添加JDK源代码包后，能够直接打开JDK的各种类文件源代码，如Object、String、HashMap等 但是，在给这些源代码打断点开启debug跟踪的时候，却发现eclipse报了一个Unable t...
ORA-28000: the account is locked
最新发布
08-31
ORA-28000: the account is locked是一个Oracle数据库的错误代码，它表示用户账户被锁定了。当用户登录失败次数超过了系统设定的限制时，数据库会自动锁定用户账户以保护安全性。这通常是由于用户密码错误多次导致的...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值