One of these messages appears in Symantec Data Loss Prevention (DLP) Enforce.
Oracle locks the DLP user account (default is PROTECT) after too many failed attempts to log in to DLP Enforce. This can occur during installation or when the DLP user account password was changed in the DB but not in the Enforce configuration.
select account_status from dba_users where username='[username]';Note: Remember to add the semicolon or the command will not execute.
e.g.
select account_status from dba_users where username='PROTECT';
alter user [username] account unlock;
e.g.
alter user PROTECT account unlock;
NOTE: The examples assume a Windows installation; for Linux, substitute the appropriate paths (e.g. /opt/Vontu/Protect/bin)
<DLP 15.0 and older> cd *\SymantecDLP\Protect\bin
<DLP 15.1 and later> cd *\Symantec\DataLossPrevention\EnforceServer\15.7\Protect\bin
For version 15.0 and earlier the syntax for DBPasswordChanger is:
DBPasswordChanger <PasswordFilePath> <New Oracle Password>
e.g. for Windows
DBPasswordChanger c:\SymantecDLP\protect\config\DatabasePassword.properties potato
Linux:
./DBPasswordChanger "opt\SymantecDLP\protect\config\DatabasePassword.properties" potato.
For version 15.1 and later The syntax for DBPasswordChanger is:
DBPasswordChanger <PasswordFilePath> <New Oracle Password>
e.g. for Windows:
DBPasswordChanger "C:\Program Files\Symantec\DataLossPrevention\EnforceServer\15.7\Protect\config\DatabasePassword.properties" potato
Linux:
./DBPasswordChanger "opt\Symantec\DataLossPrevention\ EnforceServer\15.7\Protect\ config\DatabasePassword. properties" potato.