Dear Readers,
My name is Franz Devantier, creator of this blog. I am an Oracle Certified
Professional (OCP DBA 11g) Security DBA.
I will be sharing with you the basic duties of an Oracle DBA, and also
some of the undocumented, and not so well known tasks.
I will make a deal with you: If you refer me to a company that needs
database support, from a few hours per week to full time, and I am able to sign
a contract with them.
Then I will give you 10% of the monthly
contract or deal price every month. When
the contract ends, and we re-sign the contract, I will again give you 10% of
the monthly contract price. This will go
on until the company no longer employs or contracts me or my agents to look
after their databases.
I can do this, because that 10% is my
marketing budget. When we re-sign the
contract, in the future, it may depend on you giving the thumbs up again, and
that is worth 10% of the monthly contract price, to be given to you as
commission.
Contact:
Franz
Security,
Privileges, Roles, Profiles and Resource Limitations - Part
14
Profiles
A profile is a named list of attributes that
is granted to a user. It may be the
default profile. It could also be a
secure application profile, or a password protected profile
Profiles are also used in Oracle Internet
Directory, and in this case contains a wide range of attributes, relevant to
directory usage and authentication for each user.
Profiles in Oracle Label Security contain
attributes that are useful in label security user administration, as well as
for operations management.
Profile attributes could include restrictions
on system resources. Database Resource
Manager is preferred over Profiles, for restricting system resources.
Determining Values for Resource Limits
Before defining hard resource limits, it is best to spend
some time determining the appropriate values for each resource limit that you
are going to set.
You will need to have an idea of the type of operation that
a typical user will perform. For example
you will need to determine the average usage of logical data block reads, for
the resource limit for most of the users.
Then those users that are running batch jobs, will have a completely
different limit set for them. You can
then set the parameters LOGICAL_READS_PER_SESSION and LOGICAL_READS_PER-CALL
limits conservatively for the average user.
For a specific user profile, you would probably need to
gather historical information, in order to determine a value that is representative
of the expected requirement. You could
use the AUDIT SESSION clause in order to gather statistics on the CONNECT_TIME,
LOGICAL_READS_PER_SESSION, and LOGICAL READS_PER_CALL.
You can also gather statistics for other limits using the
monitor feature of Oracle Enterprise Manager, specifically the Statistics
monitor. You can also gather this
information in SQL*Plus.
Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com
Classifieds
No comments:
Post a Comment