6.684 USER_USERS
USER_USERS
describes the current user.
Column | Datatype | NULL | Description |
---|---|---|---|
|
|
|
Name of the user |
|
|
|
ID number of the user |
|
|
|
Account status:
|
|
|
|
Date the account was locked if account status was |
|
|
|
Date of expiration of the account |
|
|
|
Default tablespace for data |
|
|
|
Name of the default tablespace for temporary tables or the name of a tablespace group |
|
|
|
Default local temporary tablespace for the user |
|
|
|
User creation date |
|
|
|
Initial resource consumer group for the user |
|
|
|
User external name. For centrally managed users, if the database user mapping is an exclusive mapping, then this will be the directory service DN for the user. If this database user is a shared schema, it will be the DN of a group. |
|
|
|
Indicates whether a user can connect directly ( For more information about creating proxy user accounts and authorizing users to connect through them, see Oracle Database Security Guide. |
|
|
|
Indicates whether a given user is common. Possible values
|
|
|
|
Denotes whether the user was created, and is maintained, by Oracle-supplied scripts (such as catalog.sql or catproc.sql). A user for which this column has the value |
|
|
|
Indicates whether the user definition was inherited from another container ( |
|
|
|
Default collation for the user’s schema |
|
|
|
Indicates whether this user is a common user created by an implicit application ( |
|
|
|
In a sharded database, the value in this column indicates whether the user was created with shard DDL enabled. The possible values are:
In a non-sharded database, the value in this column is always |
See Also:
-
Using Oracle Sharding for more information about sharded database management