Oracle Security in CDBs and PDBs - OCP: Oracle Database 12c Administrator Certified Professional - page 630

Assigning a Profile for the User
When you create a user you can assign a profile, which is a set of limits on password access
and database resources. The Oracle Database assigns the user a default profile if you do not
specify one. In this example, we create a new profile and then create a new user and include
the PROFILE clause.

SQL> CREATE PROFILE password_reuse
2 LIMIT PASSWORD_REUSE_MAX 5
3 PASSWORD_REUSE_TIME 60;

Profile created.

SQL> CREATE USER smith06
2 IDENTIFIED BY smith06
2 PROFILE password_reuse;

User created.

SQL>

Creating Common Users
To create a common user account, you must have the CREATE USER system privilege,
and the current container must be CDB$ROOT . Here are a few guidelines when creating a
common user:

User account names are in the USERNAME column in the ALL_USERS , CDB_USERS , DBA_USERS ,
and USER_USERS data dictionary views. Common users are indicated by the value YES in
the COMMON column.

■

Use the CONTAINER=ALL clause to create a common user. If you are logged into CDB$ROOT ,
the default for the CONTAINER clause is ALL .

■

Creating objects in a common user's schemas can cause problems when plugging in or
unplugging a PDB.

■

When you create a common user and you use the DEFAULT TABLESPACE , TEMPORARY
TABLESPACE , PROFILE , and QUOTA clauses, make sure that the tablespaces, tablespace
groups, and profiles have been defined in all containers of the CDB. If the objects are
not there, you'll get an error message and the user will not be created.

■

Schema objects owned by Oracle-created common users ( SYS , for example) are shared
with the entire CDB. User-created schema objects owned by common users in a PDB
cannot be shared with another PDB.

■