Cluster and Node Management

cluster and node management commands allow administrators to manage storage clusters, create and manage storage spaces, create and manage nodes, and apply configuration changes to nodes, clusters, or the overall system cluster create cluster create cluster creates a new cluster in the current database the cluster name must be distinct from the name of any existing tables in the database to create a cluster, the logged in user must be a system level user for details about creating clusters, see ocient application configuration docid\ nneedy7yn8g1pennmamng for foundation clusters, if the system is configured with a single cluster configuration, when you add a second foundation cluster, the system automatically changes to a multi cluster configuration this change is irreversible and requires a full system restart to fully take effect syntax create cluster \[ if not exists ] cluster name \<create definition> \<create definition> = type \[=] foundation \| participants \[=] (node name1, node name2, ) \| storagespace \[=] storage space name 137,100,346 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type define clusters ( \<create definition> ) you must include these configuration settings when you create a new cluster 188,135,164 false true false unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type unhandled content type examples this example creates a foundation cluster named lts cluster0 using the storage space named my storage space with three participant nodes create cluster lts cluster0 type=foundation participants=(node1,node2,node3) storagespace=my storage space; drop cluster drop cluster removes an existing cluster from the system to remove a cluster, you must be a system level user syntax drop cluster \[ if exists ] cluster name 149,134,380 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type example this example removes an existing cluster named lts cluster0 drop cluster lts cluster0; alter cluster add nodes to an existing cluster alter cluster add participants adds the specified nodes to an existing cluster in the system this operation can overprovision the storage space if necessary for the system to recognize newly added nodes, you must restart the cluster to do this, you can follow the steps in expand and rebalance system docid\ r7mqd0slg1oiuksmraupo syntax alter cluster \[ if exists ] cluster name add participants \[=] ( node name1 \[, ] ); 149,134,381 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type example this example adds the node node3 to a cluster named example cluster , which already contains node1 and node2 following this operation, example cluster consists of three nodes alter cluster example cluster add participants (node3); remove nodes from an existing cluster alter cluster drop participants drops nodes from an existing cluster this sql statement fails for a foundation cluster dropping the specified nodes brings the number of participants below the total width of the storage space associated with that cluster syntax alter cluster \[ if exists ] cluster name drop participants \[=] ( node name1 \[, ] ); 149,134,381 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type example this example drops participant node node3 from a cluster named example cluster , which contains node1 , node2 , and node3 following this operation, the participants in example cluster consist of the nodes node1 and node2 alter cluster example cluster drop participants (node3); cluster scope configuration alter cluster alter config set sets a configuration override for the configuration at the cluster scope for an explanation of how configuration overrides work, see inspect the current configuration docid\ ve2h2zdvddbtwokmidjow if the specified path to the configuration setting does not exist, the system considers it as a new configuration and appends it to the collection of existing configurations to reset a configuration override for a specific key, use the reset keyword syntax \ to set a new configuration override alter cluster \[ if exists ] cluster name alter config set string definition \[=] string value \[, ] \ to reset a configuration override alter cluster \[ if exists ] clustername alter config reset \[ string definition \[, ] ] 177,112,306 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type examples this example alters the base configuration for cluster cluster name and sets the certificate for all nodes to a certificate named cert name crt alter cluster cluster name alter config set 'certificatestore cert' = 'cert name crt'; this example resets the certificate configuration for cluster cluster name alter cluster cluster name alter config reset 'certificatestore cert'; this example alters the configuration at the cluster scope for cluster cluster name and service role lts alter cluster cluster name alter config set 'lts numlevels' = '3'; cluster scope log level configuration alter cluster cluster name alter log level set sets the log level for a particular logger for all nodes in the provided cluster for an explanation of how configuration overrides work, see inspect the current configuration docid\ ve2h2zdvddbtwokmidjow syntax \ to set a new configuration override alter cluster cluster name alter log level set \[ \<logger parameters> \[, ] ] \<logger parameters> = { 'all' | logger name \[=] logging level } \ to reset a configuration override alter cluster cluster name alter log level reset \[logger name \[, ] ] 142,100,358 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type logger parameters ( \<logger parameters> ) 144,140,164 false true false unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type unhandled content type examples this example alters the log level at the cluster scope this sets the query log level for all nodes in the cluster to debug alter cluster cluster name alter log level set 'query' = 'debug'; this example resets the log level for the query logger for the entire cluster alter cluster cluster name alter log level reset 'query'; rename cluster rename an existing cluster in the system syntax alter cluster old cluster name rename to new cluster name 172,141,288 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type example this example renames an existing cluster named lts cluster 0 to lts cluster 1 alter cluster "lts cluster 0" rename to "lts cluster 1"; storagespace create storagespace create storagespace creates a new storage space the name of the storage space must be distinct from the name of any existing storage spaces in the system to create a storage space, you must possess the create storagespace privilege for the current system it is recommended that the total width of a production system be smaller than the number of foundation nodes in the cluster so that loading can continue even in the event of a node outage syntax create storagespace \[ if not exists ] storage space name \[ width \[=] width integer], \[ parity width\[=] pw integer ] 192,98,318 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type example this example creates a new storage space named ocient create storagespace ocient width = 10, parity width = 2; drop storagespace drop storagespace removes an existing storage space, along with all associated tables and views the sql statement fails if one or more storage clusters are linked to the storage space to remove a storage space, you must possess the drop storagespace privilege for the storage space note that this action cannot be undone syntax drop storagespace \[ if exists ] storage space name \[, ] 191,97,315 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type example remove an existing storage space named ocient ss drop storagespace ocient ss; remove multiple storage spaces drop storagespace ocient ss1, ocient ss2; alter storagespace alter storagespace rename renames an existing storage space to rename a storage space, the logged in user must be a system level user syntax alter storagespace \[ if exists ] old storage space name rename to new storage space name 221,113,260 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type example to rename an existing storage space named teststoragespace to storage space 1 alter storagespace "teststoragespace" rename to "storage space 1"; node drop node drop node removes an existing node from the system a node cannot be removed from the system if it is still part of a cluster or one of the two remaining administration nodes syntax drop node \[ if exists ] node name \[, ] 157,141,287 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type example remove a node named example node drop node example node; remove multiple nodes drop node example node1, example node2; alter node alter node rename to alter node rename renames an existing node to rename a node, you must be a system level user renaming a node can cause a mismatch between the name of the node and the hostname of the node furthermore, you have to update users and scripts to use the new name of the node use this statement only to reverse these situations that can arise naturally (for example, you must replace a node with a node that has a different name) if you have a dns configuration for the node, you must reconfigure the node address after renaming the node by using the cluster and node management /#alter node set address sql statement syntax alter node \[ if exists ] old node name rename to new node name 157,99,403 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type example this example renames an existing node named sql0 to sql1 alter node sql0 rename to sql1; alter node add role alter node add role adds a role to a node each node can have one or more roles that it performs to add a role, you must be a system level user syntax alter node \[ if exists ] node name add role \[ if not exists ] \<node role> \<node role> = { sql | streamloader | operatorvm | admin | health } 157,102,403 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type node roles ( \<node role> ) this table explains the supported roles for nodes 145,267,251,250 false true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type example to add sql role to the node sql1 alter node sql1 add role sql; alter node remove role alter node remove role removes a role from a node for a list of roles, see cluster and node management /#node roles noderole some node roles cannot be removed using an alter node sql statement, including health , lts , and operatorvm to remove a role, you must be a system level user the node must be restarted in order for this change to take effect if you remove a sql role from a sql node, the database removes the node from the connectivity pool you must restart all sql nodes so that the other sql nodes understand that the node is no longer a sql node when you remove the admin role, you must also remove the /var/opt/ocient/metadatastorage raft file syntax alter node \[ if exists ] node name remove role \[ if exists ] { sql | streamloader | admin } 157,100,403 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type example this example removes the sql role from a node alter node my node remove role sql; alter node alter config set alter node alter config set sets a configuration override for the configuration at the node scope for an explanation of how configuration overrides work, see inspect the current configuration docid\ ve2h2zdvddbtwokmidjow if the specified path to the configuration setting does not exist, it will be considered a new configuration and appended to the collection of existing configurations to reset a configuration override for a specific key, use the reset keyword syntax \ to set a new configuration override alter node \[ if exists ] node name alter config set string definition \[=] string value \[, ] \ to reset a configuration override alter node \[ if exists ] node name alter config reset string definition \[, ] 188,77,402 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type examples this example sets the certificate name for this node to cert name crt alter node node2 alter config set 'certificatestore cert' = 'cert name crt'; this example resets the certificate configuration for the node node2 alter node node2 alter config reset 'certificatestore cert'; this example alters the configuration at the node scope for node node2 for service role lts alter node node2 alter config set 'lts numlevels' = '3'; alter node alter log level set alter node node name alter log level set sets the log level for a particular logger on the specified node for an explanation of how configuration overrides work, see inspect the current configuration docid\ ve2h2zdvddbtwokmidjow the logger name specified can be any string specifying a logger name, or all for the root logging configuration see the log monitoring docid\ f1pitqcnfjxgupjryknmc for more details to reset a logger to the default log level (info), use the reset keyword syntax \ to set a new configuration override alter node \[ if exists ] node name alter log level set { \<logger parameters> \[, ] } \<logger parameters> = 'all' | logger name \[=] { 'edebug' | 'debug' | 'verbose' | 'info' | 'warn' | 'error' } \ to reset a configuration override alter node \[ if exists ] node name alter log level reset \[ logger name \[, ] ] 192,98,340 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type examples this example alters the log level at the node scope the example sets the query log level for this particular node to debug alter node node name alter log level set 'query' = 'debug'; this example resets log level for the query logger on the specified node alter node node name alter log level reset 'query'; alter node alter metric level alters the reporting level of various internal metrics on a specific node for details about internal metrics, see statistics monitoring docid\ jtynlpc rgdksxytttfyh to set metrics reporting on all nodes across the system, see cluster and node management /#alter system alter metric level syntax alter node \[ if exists ] node name alter metric level { set \<set options> | reset \<reset options> } \<set options> = \[ like | regex ] metric to alter \[ , ] \[=] { 'info' | 'debug' } \<reset options> = { \[ like | regex ] metric to reset \[ , ] | all } 157,100,403 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type set metric levels \<set options> the set sql statement assigns one or more specified metrics to the specified reporting level to set levels for a range of statistics, you can use wildcard characters with the like keyword alternatively, you can use regular expressions with the regex keyword 188,125,291 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type reset metric levels \<reset options> the reset sql statement reverts one or more specified metrics to the default log level you can use wildcard characters with the like keyword alternatively, you can use regular expressions with the regex keyword use the all keyword to revert all metrics to the default log level 188,125,291 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type examples in this example, the alter node sql statement sets the resultcache queries metric on the node oc1 to the debug level alter node oc1 alter metric level set 'resultcache queries' = 'debug'; this example uses the like wildcard keyword to capture any metrics prefixed by localstorageservice device smart and assign them to the info level alter node oc1 alter metric level set like 'localstorageservice device smart %' 'info'; similar to the previous example, this sql statement uses regular expressions to capture any metrics prefixed by localstorageservice device smart alter node oc1 alter metric level set regex 'localstorageservice device smart ' 'info'; this example alters the level of multiple metrics alter node oc1 alter metric level set 'resultcache queries' = 'debug', 'resultcache data' = 'info', like 'localstorageservice device smart %' 'info'; this example resets the same metrics alter node oc1 alter metric level reset 'resultcache queries', 'resultcache data', like 'localstorageservice device smart %'; alter node set address alter node node name set address ip address changes the internal ip address or hostname for any node you must restart the system after you change the address if you change the address of an administrator node, then you must update the bootstrap conf file for every node with the new address for details about this file, see ocient system bootstrapping docid 4005nflvguw4fqfqa1spu syntax alter node \[ if exists ] node name set address node address 157,100,403 false true unhandled content type unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type examples this example changes the ip address to 111 11 11 111 for the node named my node alter node my node set address '111 11 11 111'; this example changes the sql node sql1 to use the dns address sql1 alter node sql1 set address 'sql1'; connectivity pool create connectivity pool create connectivity pool creates a connectivity pool from participant sql nodes for a client connection connectivity pools enable you to change the ip address of the client connection client redirects happen only within connectivity pools for details about connectivity pools and managing them, see manage the network configuration of an ocient system docid\ dh zr9fe qvm3p7zqrytx all sql nodes must be part of at least one connectivity pool sql nodes only listen using the values set for the listen ip and listen port parameters the database uses the source ip , source port , and priority parameters when multiple connectivity pools exist that a client can use for the connection in this case, the database uses the connectivity pool with the highest priority the database commits all changes made from these sql statements after you restart all the sql nodes for information on all connectivity pools on the system, query the system catalog tables for system catalog docid 2zcc9xuscejvt5v ihgy6 to see the connectivity pool assignment for each node, query the system catalog table for system catalog docid 2zcc9xuscejvt5v ihgy6 syntax create connectivity pool \[if not exists] pool name \<create definition> \<create definition> = source address \[=] source ip \| \[ source port \[=] source port ] \| priority \[=] priority \| \[ sso integration \[=] sso name ] \| participants ( (node \[=] node name listen address \[=] listen ip listen port \[=] listen port advertised address \[=] advertised ip \[ advertised port \[=] advertised port ] \[ openapi port \[=] openapi port ), ) 175,93,330 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type examples create the connectivity pool named test pool with source address 1 2 3 4/32 and priority 1 for one sql node named sql0 the node has the ip address 111 1 1 1 and port number 4050 for listening specify the local ip address to return to the client create connectivity pool if not exists test pool source address '1 2 3 4/32' priority 1 participants ( (node sql0 listen address '111 1 1 1' listen port 4050 advertised address 'localhost')); create the connectivity pool named test pool with source address 1 2 3 4/32 , port number 44 , and priority 1 for one sql node named sql0 the node has the ip address 111 1 1 1 and port number 4050 for listening specify the local ip address and port number 4050 to return to the client create connectivity pool if not exists test pool source address '1 2 3 4/32' source port 44 priority 1 participants ( (node sql0 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050)); create the connectivity pool named test pool with source address 1 2 3 4/32 , port number 44 , priority 2 , and three participant sql nodes sql0 , sql1 , and sql2 the nodes have the ip address 111 1 1 1 and port number 4050 for listening specify the local ip address and port number 4050 to return to the client create connectivity pool if not exists test pool source address '1 2 3 4/32' source port 44 priority 2 participants ( (node sql0 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050), (node sql1 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050), (node sql2 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050)); drop connectivity pool drop connectivity pool removes the specified connectivity pool all nodes must belong to a connectivity pool the execution of this sql statement does not permit the removal of a pool such that a node becomes an orphan syntax drop connectivity pool \[ if exists ] pool name 157,141,287 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example remove the connectivity pool named test pool drop connectivity pool test pool; alter connectivity pool alter connectivity pool set alter connectivity pool set sets the metadata of a connectivity pool that includes the source ip address, source port number, priority, and node participants syntax alter connectivity pool \[ if exists ] pool name set \<connectivity pool definition> \<connectivity pool definition> = source address \[=] source ip | source port \[=] source port | priority \[=] priority | participants( (node \[=] node name listen address \[=] listen ip listen port \[=] listen port advertised address \[=] advertised ip \[advertised port \[=] advertised port] ), ) for parameter definitions, see cluster and node management /#create connectivitypool to directly edit the listen address , listen port , advertised address , or advertised port parameters, you must either remove the participants and add them back with new values for these parameters using the alter connectivity pool drop participants and alter connectivity pool add participants statements respectively, or use the alter connectivity pool set participants statement examples this example sets the priority to 2 of the connectivity pool named test pool alter connectivity pool test pool set priority = 2; this example sets the participants of the connectivity pool named test pool to the list of participants with sql nodes sql1 and sql2 when you execute this statement, the database resets the prior list of node participants to the new list the nodes have the ip address 111 1 1 1 and port number 4050 for listening specify the local ip address and port number 4050 to return to the client alter connectivity pool test pool set participants( (node sql1 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050), (node sql2 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050)); view the node identifiers of the participants of the test pool connectivity pool by querying the node identifier node id in the sys connectivity pool participants and sys connectivity pools system catalog tables select cpp node id from sys connectivity pool participants cpp inner join sys connectivity pools cp on cpp id = cp id where cp name = 'test pool'; alter connectivity pool rename to alter connectivity pool rename to sql statement renames the existing connectivity pool syntax alter connectivity pool \[ if exists ] pool name rename to new pool name 157,141,287 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type examples rename the test pool connectivity pool to new test pool alter connectivity pool test pool rename to new test pool; alter connectivity pool add participants alter connectivity pool add participants adds one or more nodes to the participant list of an existing connectivity pool for information on all connectivity pools on the system, query the system catalog tables for system catalog docid\ l4 86sztud4mozck0gxys to see the connectivity pool assignment for each node, query the system catalog table for system catalog docid\ l4 86sztud4mozck0gxys syntax alter connectivity pool \[ if exists ] pool name add participants( (node \[=] node name listen address \[=] listen ip listen port \[=] listen port advertised address \[=] advertised ip \[advertised port \[=] advertised port] ), ) examples add one node sql5 to the participant list of the connectivity pool test pool the node has the ip address 111 1 1 1 and port number 4050 for listening specify the local ip address and port number 4050 to return to the client alter connectivity pool test pool add participants( node sql5 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050); add two nodes sql6 and sql7 to the participants list of the connectivity pool test pool the nodes have the ip address 111 1 1 1 and port number 4050 for listening specify the local ip address and port number 4050 to return to the client alter connectivity pool test pool add participants( (node sql6 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050), (node sql7 listen address '111 1 1 1' listen port 4050 advertised address 'localhost' advertised port 4050)); alter connectivity pool alter participant alter connectivity pool alter participant modifies the configurations of one sql node assigned to the existing connectivity pool this sql statement can alter only one configuration parameter of a participant node at a time for information on all connectivity pools on the system, query the system catalog tables for connectivity pools for details, see system catalog docid\ mseqs gth3ngedbtncrp9 to see the connectivity pool assignment for each node, query the system catalog table for connectivity pool participants for details, see system catalog docid\ mseqs gth3ngedbtncrp9 syntax alter connectivity pool \[ if exists ] pool name alter participant node name set \<connectivity pool definition> \<connectivity pool definition> = { listen address \[=] listen ip \| listen port \[=] listen port \| advertised address \[=] advertised ip \| advertised port \[=] advertised port \| openapi port \[=] openapi port } 175,93,330 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example modify the sql node sql0 to use the new listen port value 4051 alter connectivity pool cp test alter participant sql0 set listen port 4051; alter connectivity pool drop participants alter connectivity pool drop participants removes one or more nodes from the participant list of an existing connectivity pool if you remove the last node of a connectivity pool, the ocient system automatically removes the connectivity pool for information on all connectivity pools on the system, query the system catalog tables for connectivity pools for details, see system catalog docid\ mseqs gth3ngedbtncrp9 to see the connectivity pool assignment for each node, query the system catalog table for connectivity pool participants for details, see system catalog docid\ mseqs gth3ngedbtncrp9 all nodes must belong to a connectivity pool the execution of this sql statement does not permit the removal of a node such that it becomes an orphan syntax alter connectivity pool \[ if exists ] pool name drop participants (node name, ) examples remove one node sql5 from the connectivity pool test pool alter connectivity pool if exists test pool drop participants sql5; remove nodes sql6 and sql7 from the connectivity pool test pool alter connectivity pool test pool drop participants (sql6, sql7); alter connectivity pool set sso integration alter connectivity pool set sso integration assigns a connectivity pool to use a specific sso integration connectivity pools look for the specified sso integration name for each database you are trying to connect to if the database doesn't support that sso integration name, it uses the default sso syntax alter connectivity pool \[ if exists ] pool name set sso integration sso name 157,141,287 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example alter connectivity pool cp test set sso integration sso test; alter connectivity pool remove sso integration alter connectivity pool remove sso integration removes an assigned sso integration syntax alter connectivity pool \[ if exists ] pool name remove sso integration sso name 157,141,287 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example this example removes the sso integration sso test from the connectivity pool cp test alter connectivity pool cp test remove sso integration sso test; sso integration create sso integration creates a new sso integration protocol, which can connect to databases as a database integration (see database, tables, views, and indexes docid\ uacarixqhe493vlhudb5b ) or connect using a connectivity pool (see cluster and node management /#alter connectivitypool set sso integration ) syntax create sso integration \[if not exists ] sso name protocol sso protocol \<sso property> \[, ] \<sso property> = \ literal or string value property name = value | \ list of values property name = \[ value \[, ] ] | \ map of values property name = { key = value \[, ] } 145,110,386 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type sso properties 128,88,109,113,236,205 false true left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left false unhandled content type example this example creates an sso integration protocol with the specified openid issuer "https //accounts google com" , client identifier, and default group each of these parameters is required to create a new sso integration the example assumes preset values for the client identifier and default group create sso integration sso test protocol oidc issuer = "https //accounts google com", client id = example database app id, default group = example database group; drop sso integration drops an sso integration protocol syntax drop sso integration \[ if exists ] sso name 145,110,386 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example this sql statement drops the sso integration protocol sso test drop sso integration sso test; alter sso integration alters an sso integration protocol by renaming it or modifying its properties alter sso integration sso name \[ if exists ] { rename to new name | set \<sso property> \[, ] } \<sso property> = \ literal or string value property name = value | \ list of values property name = \[ value \[, ] ] | \ map of values property name = { key = value \[, ] } 145,110,386 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type examples alter sso integration properties this example alters the sso integration to use different properties, changing the openid client identifier and the default group to "group2" the example assumes a preset value for the client identifier alter sso integration sso test set client id = different database app id, default group = "group2"; rename an sso integration this example renames the sso integration to sso test 2 alter sso integration sso test rename to sso test 2; system alter system alter config set alter system alter config set sets an override for the configuration at the system scope for an explanation of how configuration overrides work, see inspect the current configuration docid\ ve2h2zdvddbtwokmidjow if the specified path to the configuration setting does not exist, it is considered a new configuration and appended to the collection of existing configurations to reset a configuration override for a specific parameter, use the reset keyword this configuration override is set in the base node configuration by default to apply the override to a specific service role, prefix the key with the service role name syntax \ to set a new configuration override alter system alter config set parameter name \[=] parameter value \[, ] \ to reset a configuration override alter system alter config reset \[ parameter name \[, ] ] 223,93,330 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type examples this example alters the base configuration of the system scope the example sets the certificate name for each node in the entire system to cert name crt alter system alter config set 'certificatestore cert' = 'cert name crt'; this example resets the certificate configuration for the entire system alter system alter config reset 'certificatestore cert'; this example alters the configuration for service role sql the purgecachefrequency setting determines the frequency in seconds to purge the result set cache of stale values alter system alter config set 'sql purgecachefrequency' = 600; system scope log level configuration alter system alter log level set sets the log level for a particular logger for all nodes in the system for an explanation of how configuration overrides work, see inspect the current configuration docid\ ve2h2zdvddbtwokmidjow the logger name specified can be any string specifying a logger name, or all for the root logging config see the log monitoring docid\ f1pitqcnfjxgupjryknmc for more details syntax \ to set a new configuration override alter system alter log level set { \<logger parameters> \[, ] } \<logger parameters> = 'all' | logger name \[=] { 'edebug' | 'debug' | 'verbose' | 'info' | 'warn' | 'error' } \ to reset a configuration override alter system alter log level reset \[logger name \[, ]] 196,97,323 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type example this example alters the log level at the system scope alter system alter log level set 'all' = 'debug'; alter system rename to alter system rename to s ets the system name the system name appears in the sys system information system catalog table you can also see the current system name by using the other functions and expressions docid\ etxli7o estspkhqwbuzf function syntax alter system rename to system name 188,125,291 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type example alter system rename to "productionsystem"; alter system alter metric level alters the reporting level of various internal metrics across the system, including all nodes for details about internal metrics, see statistics monitoring docid\ jtynlpc rgdksxytttfyh to set metrics reporting for individual nodes, see cluster and node management /#alter node alter metric level syntax alter system alter metric level { set \<set options> | reset \<reset options> } \<set options> = \[ like | regex ] metric to alter \[ , ] \[=] { 'info' | 'debug' } \<reset options> = { \[ like | regex ] metric to reset \[ , ] | all } set metric levels \<set options> the set sql statement assigns one or more specified metrics to the specified reporting level you can assign metrics to info or debug levels to set levels for a range of statistics, you can use wildcard characters with the like keyword alternatively, you can use regular expressions with the regex keyword 188,125,291 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type reset metric levels \<reset options> the reset sql statement reverts one or more specified metrics to the default reporting level you can use wildcard characters with the like keyword alternatively, you can use regular expressions with the regex keyword use the all keyword to revert all metrics to the default level 188,125,291 false true unhandled content type unhandled content type false unhandled content type unhandled content type unhandled content type false unhandled content type examples in this example, the alter system sql statement sets the resultcache queries metric to the debug level alter system alter metric level set 'resultcache queries' = 'debug'; this example uses the like wildcard to capture any metrics prefixed by localstorageservice device smart and assign them to the info level alter system alter metric level set like 'localstorageservice device smart %' 'info'; similar to the previous example, this sql statement uses regular expressions to capture any metrics prefixed by localstorageservice device smart alter system alter metric level set regex 'localstorageservice device smart ' 'info'; this example alters the level of multiple metrics alter system alter metric level set 'resultcache queries' = 'debug', 'resultcache data' = 'info', like 'localstorageservice device smart %' 'info'; this example resets the same metrics alter system alter metric level reset 'resultcache queries', 'resultcache data', like 'localstorageservice device smart %'; alter system alter security set security settings using the alter system alter security sql statement replace \<security setting> with the security setting and \<value> with the value you can inspect the current values of system configuration settings using the sys config and sys node config system catalog tables syntax alter system alter security \<security setting> \[=] \<value> 188,125,291 false true unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type examples set a security setting for all databases set the password lifetime to 30 days for the entire system alter system alter security password lifetime days = 30; set multiple security settings s et multiple security settings in a single sql statement in this case, set the password lifetime to 30 days and the minimum password character length to 12 as with other similar sql statements, the = character is optional alter system alter security password lifetime days 30, password minimum length 12; related links other functions and expressions docid\ etxli7o estspkhqwbuzf create table sql statement examples docid 0rmcbcyysu 0ej2rmrcqy database password security settings docid 3fiusnpipj97zfs1tbm5g