How To Lock/Unlock a Schema Account and Which Privileges are Required
(Doc ID 1073750.1)
Last updated on AUGUST 17, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.7.0 to 11.2.0.0 [Release 8.1.7 to 11.2]Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.3 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
User accounts can be created in lock mode for security reasons
--or--
A user account can become locked over time due if
- the user fails to provide the correct password after [x] number of attempts
- the account hasn't been used for [x] days
- etc
This article describes the command and privileges needed to lock or unlock a schema account.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |