
09)
Password history:
Password history checks ensure that a user cannot reuse a password
for a specified time interval. These checks can be implemented using one of
the following:
PASSWORD_REUSE_TIME to specify that a user cannot reuse a
password for a given number of days
PASSWORD_REUSE_MAX to force a user to define a password
that is not identical to earlier passwords
When one parameter is set to a value other than DEFAULT or UNLIMITED,
the other parameter must be set to UNLIMITED.
10)
Steps for using resource limits:
Use the following steps to control the usage of resources with profiles:
o
Create a profile with the CREATE PROFILE command to
determine the resource and password limits.
o
Assign profiles with the CREATE USER or ALTER USER
command.
o
Enforce resource limits with the ALTER SYSTEM command or
by editing the initialization parameter file.

You've reached the end of your free preview.
Want to read all 4 pages?
- Spring '16
- data integrity, password history