CREATE USER
Valid in: SQL, ESQL, OpenAPI, ODBC, JDBC, .NET
The CREATE USER statement defines a new user.
The CREATE USER statement has the following format:
[EXEC SQL] CREATE USER user_name
[WITH with_item {, with_item}]
with_item = NOPRIVILEGES | PRIVILEGES = ( priv {,priv} )
| NOGROUP | GROUP = default_group
| SECURITY_AUDIT = ( audit_opt {,audit_opt})
| NOEXPIRE_DATE | EXPIRE_DATE = 'expire_date'
| DEFAULT_PRIVILEGES = (priv {,priv})| ALL | NODEFAULT_PRIVILEGES
| NOPROFILE | PROFILE = profile_name
| NOPASSWORD | PASSWORD = 'user_password'
| PASSWORD = X'encrypted_password'
| EXTERNAL_PASSWORD
| DBMS_AUTHENTICATION = 'REQUIRED' | 'OPTIONAL'
| LONG_NAME='long_name_string'
user_name
Specifies the user name to be created. Must be a valid object name.
NOPRIVILEGES
Assigns no privileges to the user.
PRIVILEGES = ( priv {, priv} )
Assigns one or more of the following subject privileges, which apply to the user regardless of the database to which the user is connected.
AUDITOR
Allows the user to register or remove audit logs and to query audit logs.
CHANGE_PASSWORD
Allows the user to change his password.
CREATEDB
Allows the user to create databases.
IMA_SEC_READ
Allows the user to access all IMA tables (including those that would otherwise require the security privilege) to monitor performance and system status.
MAINTAIN_AUDIT
Allows the user to change the ALTER USER SECURITY_AUDIT and ALTER PROFILE SECURITY_AUDIT privileges. Also allows the user to enable, disable, or alter security audit.
MAINTAIN_LOCATIONS
Allows the user to create and change the characteristics of locations.
MAINTAIN_USERS
Allows the user to perform various user-related functions, such as creating or altering users, profiles, group and roles, and to grant or revoke database and installation resource controls.
OPERATOR
Allows the user to perform database backups and other database maintenance operations.
SECURITY
Allows the user to perform security-related functions, such as creating and dropping users.
TRACE
Allows the user to use tracing and debugging features.
default_group
Specifies the default group to which the user belongs. It must be an existing group. For details about groups, see
CREATE GROUP.
If the GROUP clause is omitted, the default is NOGROUP, which means the user is not assigned to a group.
audit_opt
Defines security audit options:
ALL_EVENTS
Audits all activity by the user.
DEFAULT_EVENTS
Audits the types of events specified with the ENABLE and DISABLE SECURITY_AUDIT statements. This is the default if the SECURITY_AUDIT clause is omitted.
QUERY_TEXT
Audits the query text associated with specific user queries. Security auditing of query text must be enabled as a whole, using the ENABLE and DISABLE SECURITY_AUDIT statements with the QUERY_TEXT option. For example: ENABLE SECURITY_AUDIT QUERY_TEXT.
expire_date
Specifies an optional expiration date associated with the user. Any valid date can be used. Once the expiration date is reached, the user is no longer able to log on. If the EXPIRE_DATE clause is omitted, the default is NOEXPIRE_DATE.
DEFAULT_PRIVILEGES =
( priv {, priv} ) | ALL| NODEFAULT_PRIVILEGES
Defines the privileges initially active when connecting to Actian X. These must be a subset of those privileges granted to the user.
ALL
All the privileges held by the profile are initially active.
NODEFAULT_PRIVILEGES
No privileges are initially active. Allows default privileges to be removed.
profile_name
Allows a profile to be specified for a the user. If the profile clause is omitted, the default is NOPROFILE.
user_password
Allows the user to change his own password. If the oldpassword clause is missing or invalid the password is unchanged. In addition, a user with the MAINTAIN_USERS privilege can change or remove any password.
EXTERNAL_PASSWORD
Allows a user's password to be authenticated externally to Actian X. The password is passed to an external authentication server for authentication.
DBMS_AUTHENTICATION =
Indicates whether DBMS authentication is required or optional.
'REQUIRED'
Allows only connection requests that specify the user name and password defined at the DBMS Server level and to a dbms_authentication enabled DBMS Server to succeed; other connections fail. Users with the “security” privilege, including the installation owner, cannot be defined as DBMS_AUTHENTICATION='REQUIRED'.
'OPTIONAL'
Allows connection requests that specify a user name and password defined at the operating system level, an installation password, or a Kerberos principle to succeed. In particular, this allows a local connection to a dbms_authentication server to succeed through implicit OS login authentication, without requiring the DBMS password.
Default: 'OPTIONAL'
LONG_NAME='long_name_string'
Specifies a unique long name of up to 160 characters that defaults to user_name. This is useful, for example, for user names from single sign-on applications such as Salesforce, which consist of a name, or a name and an email address. LONG_NAME must not match a different user’s user_name.
The connection will be verified (and authenticated, if DBMS authentication is turned on), matching either the user_name or long_name_string. After connection is initiated and the incoming name is validated, the short user_name will be used to identify object ownership, identify the session, locate grants and privileges, and perform all operations that user_name can do.
The session can query the long_name_string through DBMSINFO, regardless of whether the connection was established with long_name_string or user_name.
Embedded Usage
In an embedded CREATE USER statement, specify the WITH clause using a host string variable (with :hostvar).
Permissions
You must have MAINTAIN_USERS privilege and be connected to the iidbdb database.
You must have MAINTAIN_AUDIT privilege to change security audit attributes.
Locking
The CREATE USER statement locks pages in the iiuser system catalog.
Related Statements
ALTER PROFILE
ALTER USER
CREATE PROFILE
DROP PROFILE
DROP USER