The document discusses how to use PDB lockdown profiles to define custom security policies for a PDB by restricting features, options, and SQL statements, and how to configure a separate OS user for each PDB using the PDB_OS_CREDENTIAL parameter.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
45 views
Managing PDB Lockdown Profiles
The document discusses how to use PDB lockdown profiles to define custom security policies for a PDB by restricting features, options, and SQL statements, and how to configure a separate OS user for each PDB using the PDB_OS_CREDENTIAL parameter.
Using PDB Lockdown Profiles Example: Disable specific Database Feature • Feature category examples: – AWR - Common Schema access – Connections - Network access • Refer to documentation for full list. ALTER LOCKDOWN PROFILE cdb1_profile DISABLE FEATURE=('UTL_HTTP','UTL_SMTP');
– External jobs – External table – PL/SQL library executions • Configure a separate OS user for each PDB using the parameter PDB_OS_CREDENTIAL • Datafiles creation is not affected by this parameter
1. Login to the root with EXECUTE privilege on DBMS_CREDENTIAL
2. Create an Oracle credential for the operating system user BEGIN DBMS_CREDENTIAL.CREATE_CREDENTIAL ( CREDENTIAL_NAME => 'PDB1_OSU', USERNAME => 'pdb1_osuser', PASSWORD => 'password'); END;
3. Login to the PDB and set the PDB_OS_CREDENTIAL
ALTER SYSTEM SET PDB_OS_CREDENTIAL = PDB1_OSU SCOPE = SPFILE;