ALTER GROUP
Use the ALTER GROUP command to alter a group with additional security-related clauses.
Synopsis
Syntax for altering a security
group:
ALTER GROUP <group-name> [WITH] [<alter_group_clause>]...
<alter_group_clause> ::=
ROWSETLIMIT <limit>
| SESSIONTIMEOUT <limit>
| QUERYTIMEOUT <limit>
| DEFPRIORITY <priority_type>
| MAXPRIORITY <priority_type>
| RESOURCELIMIT <percent>
| [ADD] USER { <user-name> },...
| DROP USER { <user-name> },...
| SYSID <id-number>
| OWNER TO <group-name>
| RENAME TO <group-name>
| COLLECT HISTORY { ON | OFF | DEFAULT }
| CONCURRENT SESSIONS <limit>
| ALLOW CROSS JOIN [TRUE|FALSE|NULL]
| ACCESS TIME { ALL | DEFAULT | ( <access-time>,... )
<access-time> ::= DAY { ALL | <day>, ... } [ <time-bound> ]
<time-bound> ::= START <time-literal> END <time-literal> ]
Inputs
The ALTER GROUP command has the following
additional inputs:
Input | Description |
---|---|
COLLECT HISTORY [ ON | OFF | DEFAULT ] | Determines whether this session collects history for a group. ON indicates that history is collected for this group when connected to a database that also has COLLECT HISTORY ON. OFF indicates that history is not collected for this group. DEFAULT means to examine groups this group is a member of to determine whether to collect history. If any group has COLLECT HISTORY ON, then history is collected when connected to a database that also has COLLECT HISTORY ON. If no group has COLLECT HISTORY ON, but a group has COLLECT HISTORY OFF, then no history is collected. If all groups have DEFAULT history collection, the history is collected. DEFAULT is the default for a group, if the COLLECT HISTORY clause is not specified. |
CONCURRENT SESSIONS <limit> | Sets the maximum number of concurrent sessions this group can have. A value of 0 means no limit to the number of concurrent sessions, unless a limit is imposed by a group. In that case, the minimum limit of concurrent sessions across all such groups is used. |
ALLOW CROSS JOIN [TRUE | FALSE | NULL] | Sets user or group permission to allow explicit cross joins.
If NULL is defined for a user, the system checks against the group
permission, and takes the lowest non-null value, where FALSE is lower
than TRUE. This setting involves a system-wide change, so notify all affected users before making this change. |
ACCESS TIME ALL | Indicates that this group can start sessions on the system at any time on any day. |
ACCESS TIME DEFAULT | Indicates that access time restrictions are taken from the groups. If no groups have access time restrictions, then the user can start sessions at any time on any day. The access time restriction is evaluated for every group that has one. If any group restricts access, the user cannot create a session. That is, the most restrictive access policy is applied. |
access-time | Specifies one access time subclause; several can be specified. An access time subclause defines one or more days by the standard SQL day number (1 = Sunday, 7 = Saturday). The keyword ALL can be use to specify all days of the week; it is equivalent to 1,2,3,4,5,6,7. An access time subclause optionally contains one time bound. If no time bound is specified, then the group can create a session at any time on the specified day. |
time-bound | Specifies a time range from a start time to an end time. The times can be specified as any valid SQL time literal. It is possible to repeat the same day specification multiple times with different time bounds. |
Outputs
The ALTER GROUP command has the
following output:
Output | Description |
---|---|
ERROR: permission denied. | You must have Manage Security privilege to alter a group. |
Description
For details about all the options
of the ALTER GROUP command, see theIBM® Netezza® Database User’s Guide.
The ALTER GROUP command has the following characteristics:
- Privileges required
- You must have Manage Security privilege to alter a group.
- Common tasks
- Use the ALTER GROUP command to alter a group with additional clauses.
Usage
The following provides sample usage:
ALTER GROUP FLIGHT WITH COLLECTHISTORY OFF;