Oracle unlock user

Oracle unlock users this article is intended to solve the problem of Oracle 10 Gb user unlocking and restricted execution permissions. It is hoped that this article will help you understand Oracle
10 Gb user unlocking is helpful. 1) The user is locked, but he has been unable to unlock Oracle 10 Gb users. Note: a user is often locked at a site. He just used [alter user <user_name> account unlock;
Commit;] Then the user still cannot log on. The error still persists: the user is locked. Www.2cto.com solution: Check the DBA_USERS table to view the user's status. Whether it is LOCKED (changed to LOCKED (TIMED)
User is locked ). Select * from USER_HISTORY $ -- check whether the user password has expired select * from dba_profiles -- view the user's profile settings. Solution: sqlplus/nolog conn/as sysdba alter user <user_name> account unlock; -- Unlock alter user <user_name> password expire; -- password Expiration alter user <user_name> identified by <password>; -- reset the password or alter profile default limit failed_login_Attempts unlimited; then log on to [note] to view the password limit for any account, you can query the Expire_Date column in The DBA_USERS data dictionary view. If the user
You can query the Expiry_Date column in The USER_USERS data dictionary view (using SQL * Plus or a client-based query tool ). ORA-01031: insufficient privileges problem: ORA-01031: insufficient privileges error cause: Operating System Login with Oracle user, then, use sqlplus/nolog conn/as sysdba. The operating system user before connect needs to be in the DBA group. Therefore, first determine whether the Oracle user belongs to the DBA group.
Now it belongs to the staff group. Solution: After modifying the group attribute of an Oracle user, the problem is solved.