Skip to main content

ORA-28007: THE PASSWORD CANNOT NE REUSED

            


- Here will see how to deal with  => ORA-28007: the password cannot be reused - 

  1. I got a request from client user, stating his account has been locked.
  2. When I check the status of the account I found the below.
  3. connect to SYS user & execute the below query of that database.

SQL> select password,username,account_status,profile from dba_users where username='TEST';

PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE
------------------             ----------------  -------------------------------           --------------------
AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS

So, then I have unlocked the account and checked the same again & I found the below results.

SQL>  select password,username,account_status,profile from dba_users where username='TEST';

PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE
------------------             ----------------  -------------------------------           --------------------
AB2Aa8AC9971521e3     TEST          EXPIRED(GRACE)                NONAPP_USERS

When I trying to reset his password same as his old password, using the encrypted password(AB2Aa8AC9971521e3). I'm getting below error.


SQL>  alter user TEST IDENTIFIED BY VALUES 'AB2Aa8AC9971521e3';

alter user TEST  IDENTIFIED BY VALUES 'AB2Aa8AC9971521e3'
*
ERROR at line 1:
ORA-28007: the password cannot be reused

SOLUTION:

Change the profile limit to unlimited like below.

Check the below first and make a note of them.

SQL> select * from dba_profiles where profile='NONAPP_USERS' and  RESOURCE_NAME in ('PASSWORD_REUSE_TIME');


     PROFILE                           RESOURCE_NAME              RESOURCE LIMIT
----------------------------         --------------------------------        --------------------------
NONAPP_USERS     PASSWORD_REUSE_TIME              PASSWORD .0006

SQL> select * from dba_profiles where profile='NONAPP_USERS' and  RESOURCE_NAME in ('PASSWORD_REUSE_MAX');

     PROFILE                           RESOURCE_NAME              RESOURCE LIMIT
----------------------------         --------------------------------        --------------------------
NONAPP_USERS            PASSWORD_REUSE_MAX               PASSWORD 4

Now change these values to unlimited.

SQL> select name from v$database;

NAME
---------
TCPT

SQL> alter profile NONAPP_USERS limit PASSWORD_REUSE_MAX UNLIMITED;

Profile altered.

SQL> alter profile NONAPP_USERS limit PASSWORD_REUSE_TIME UNLIMITED;

Profile altered.

Once the both changed to unlimited. Now try to alter the password. like below

SQL> alter user TEST  IDENTIFIED BY VALUES 'AB2Aa8AC9971521e3 ';

User altered.

Please check account status now.

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

USERNAME                       ACCOUNT_STATUS
------------------------------ --------------------------------
TEST                                             OPEN

Now we are able to ALTER the user password. Once password reset, alter profile limit like as previous. using the below queries.

SQL> alter profile NONAPP_USERS limit PASSWORD_REUSE_TIME 1/1440;

Profile altered.

SQL> alter profile NONAPP_USERS limit PASSWORD_REUSE_MAX 4;

Profile altered.


Here we are done :)

Thank You !





Comments

Popular posts from this blog

Issues and Solutions for Oracle 19c Grid Infrastructure Installation

     Common Issues and Solutions for Oracle 19c Grid Infrastructure Installation •       Check Log Files for Details Oracle installation issues often provide valuable clues in the log files. If the installer seems stuck or fails, check the following logs: ▪ Install log : /u01/app/oraInventory/logs/installActions<date>.log •       ▪ Grid Infrastructure log : $ORACLE_BASE/cfgtoollogs/ •         •       These logs can provide error messages and help identify the exact issue. •         •        Check Permissions and Ownership Verify that the Oracle Grid Infrastructure installation directories have the correct ownership and permissions. •        For example: •        Make sure the grid user has permission to write to the directories where the i...

CHANGING DBID FOR ORACLE DATABASE 11G

C:\Users\computer>sqlplus SQL*Plus: Release 11.1.0.7.0 - Production on Thu Sep 10 21:03:33 2013 Copyright (c) 1982, 2008, Oracle.  All rights reserved. Enter user-name: sys as sysdba Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select dbid from v$database;       DBID ---------- 2188161033 SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options C:\Users\computer>nid DBNEWID: Release 11.1.0.7.0 - Production on Thu Sep 10 21:04:44 2013 Copyright (c) 1982, 2007, Oracle.  All rights reserved. Keyword     Description                    (Default) ---------------------------------------------------- TARGET ...

How to Improve Oracle Data Pump Performance - IMPDP

  How to Improve Oracle Data Pump Performance:- Use Parallelism : Set the PARALLEL parameter to at least 2 * number of CPUs . This allows multiple worker processes to perform tasks simultaneously, speeding up both export and import processes. Example: PARALLEL=4 for a system with 2 CPUs. Perform Import Using NETWORK_LINK : Use the NETWORK_LINK parameter to import data directly from the source database. This method is particularly helpful when space is constrained, as it streams the data without needing to generate dump files on the source. It can also reduce time compared to exporting and then importing, as data is streamed directly from the source to the target database. Disable Archivelog Mode (Standalone Databases) : For standalone databases, temporarily disable archive logging during the import process. Import operations can generate a lot of redo logs, slowing down the import. Disabling...