Database Reference
In-Depth Information
to be prefixed with OPS$ and that's why we call them OPS$ user
accounts. If os_authent_prefix init.ora paramenter is left as
default i.e. OPS$, then the Externally Authenticated User
Account can be created as follows.
CREATE USER ops$asim
IDENTIFIED EXTERNALLY;
On the other hand if its set to blank (os_authent_prefix = “
”) then no prefix is required as shown in the following example.
CREATE USER asim
IDENTIFIED EXTERNALLY;
Example:
ALTER USER asim
IDENTIFIED BY black123;
Or,
ALTER USER asim
DEFAULT TABLESPACE hr_data;
To change the password of asim or anything else related to user,
use the ALTER USER statement.
Once you have created the user and assigned him/her default
tablespace then the user is ready to go. He can now create
database objects (tables, views etc) under his schema. You can
also assign him access to objects under your schema using
GRANT statement and you can also take that privilege back
using the REVOKE statement.
Next very important concept I would like to give you is the
“role”. Role in database jargon means the group of privileges
bundled together and given a name or alias. So what is the
benefit of creating roles? For example, let say Human Resources
(HR) department of a company has 65 people and out of those 65
Search WWH ::
Custom Search