DBA_JOINGROUPS

5.134 DBA_JOINGROUPS

DBA_JOINGROUPS describes join groups in the database. A join group is a user-created object that consists of two or more columns that can be meaningfully joined. The maximum number of columns that can be included in a join group is 255.

In certain queries, join groups enable the database to eliminate the performance overhead of decompressing and hashing column values. Join groups require an In-Memory column store (IM column store).

Related View

USER_JOINGROUPS describes join groups belonging to the user. This view does not display the JOINGROUP_OWNER column.

Column	Datatype	NULL	Description
`JOINGROUP_OWNER`	`VARCHAR2(128)`	`NOT NULL`	Join group owner. This is the user that created the join group.
`JOINGROUP_NAME`	`VARCHAR2(128)`	`NOT NULL`	This is the user specified name of the join group. The join group name is specified when the join group is created as part of the `CREATE INMEMORY JOIN GROUP` statement.
`TABLE_OWNER`	`VARCHAR2(128)`	`NOT NULL`	Table owner
`TABLE_NAME`	`VARCHAR2(128)`	`NOT NULL`	Table name
`COLUMN_NAME`	`VARCHAR2(128)`	`NOT NULL`	Column name
`FLAGS`	`VARCHAR2(6)`		Possible values: `MASTER`: Indicates which column in the join group is mastering the global dictionary. A join group is a group of columns sharing a global dictionary; the global dictionary is associated with one column and the other columns share the same dictionary. The column with which the global dictionary is associated is called the mastering column. NULL: Indicates that the column is not mastering the global dictionary.
`GD_ADDRESS`	`RAW(8)`		The memory address of the global dictionary. Ideally, all the columns in one join group should have the same global dictionary address (that is, they share the same global structure). This might not always be the case (for example, a column might be added to a join group after it was populated into memory - in which case its `GD_ADDRESS` field will be NULL). In such cases, you should force re-populate the tables that are part of the join group and check the views after the repopulates complete.

Note:

This view is available starting with Oracle Database 12c Release 2 (12.2.0.1).