Overview
enable_sys_unit_standalone specifies whether the unit of the system tenant is a standalone node.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Only the
systenant can modify this parameter. User tenants cannot modify it.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | Bool |
| Default Value | False |
| Value range |
|
| Modifiable | Yes, you can use theALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
When this parameter is set to True, the following impacts occur:
When creating or increasing the number of resource pools, you need to consider the units of the system tenant. That is, the units of a user tenant and those of the system tenant cannot be deployed on the same server.
The system will migrate other units on the same server as the unit belonging to the sys tenant away.
When a server is permanently decommissioned or deleted, the system first migrates the units of the sys tenant and then those of other tenants. Moreover, the units of other tenants cannot reside on the same server as those of the sys tenant.
During tenant group load balancing, the server hosting the system tenant unit is excluded from the list of available servers for the tenant groups. In other words, the units of the tenant groups are distributed across all servers except for the one where the system tenant unit resides.
Configuration example
Set the unit of the system tenant to prevent exclusive node occupation.
obclient> ALTER SYSTEM SET enable_sys_unit_standalone = False;