Remove Database Parameters

This section explains how to remove custom parameters in an Exasol database.

Removing parameters that you have added or changed will remove your customization of the database configuration. If the parameters and/or values have a default configuration, the default behavior will return.

Invalid parameters or invalid configuration syntax will prevent the database from starting. To avoid unnecessary downtime, contact Support before you add or change database parameters.

This procedure can be carried out using either the Administration API or ConfD.

Prerequisites

The database must be stopped. For more information, see Stop a Database.

Procedure - Administration API

The following examples use curl on a Linux terminal to send REST calls to endpoints in the Administration API. You can also use other interfaces and languages to interact with the API. For more information, see Administration API.

Placeholder values are styled as Bash variables, for example: $EXASOL_IP. Replace the placeholders with your own values.

  1. To get information about the database, send a GET request to the /api/v1/databases endpoint.

    curl -k -X "GET" \
    "https://$EXASOL_IP/api/v1/databases" \
    -H "accept: application/json" \
    -H "Authorization: Basic $AUTH_TOKEN"

    The response includes the database ID, name, and version. Additional details are included depending on the configuration and platform.

  2. To see all currently configured additional parameters, send a GET request to the /api/v1/databases/DATABASE_ID/parameters endpoint.

    curl -k -X "GET" \
      "https://$EXASOL_IP/api/v1/databases/$DATABASE_ID/parameters' \
      -H "accept: application/json" \
      -H "Authorization: Basic $AUTH_TOKEN"

    The response will list all additional parameters currently defined in the configuration. If no additional parameters have been configured, the result will be empty. Default parameters are not shown. For example:

    {
      "parameters": {
        "-forceProtocolEncryption": "1",
        "-oidcProviderClientSecret": "abcd"
      }
    }
  3. To remove parameters, send a DELETE request to the /api/v1/databases/DATABASE_ID/parameters endpoint. Specify the parameters to be removed as query strings directly after the endpoint. For example:

    curl -k -X "DELETE" \
    "https://$EXASOL_IP/api/v1/databases/$DATABASE_ID/parameters?parameter=-oidcProviderClientSecret&parameter=-param_name2" \
    -H "accept: application/json" \
    -H "Authorization: Basic $AUTH_TOKEN"

    Make sure that only the parameter names are specified and that each parameter begins with a dash (-).

  4. To verify that the database configuration has been updated, send a GET request to the /api/v1/databases/DATABASE_ID/parameters endpoint. For example:

    curl -k -X "GET" \
      "https://$EXASOL_IP/api/v1/databases/$DATABASE_ID/parameters' \
      -H "accept: application/json" \
      -H "Authorization: Basic $AUTH_TOKEN"

    The response will list all additional parameters currently defined in the configuration. If no additional parameters have been configured, the result will be empty. Default parameters are not shown. For example:

    {
      "parameters": {}
    }

Procedure - ConfD

The following examples use the command-line tool confd_client in a Linux terminal connected to a database node. For more information about how to use this tool, see ConfD.

  1. To find the name of the database, use the ConfD job db_list. For example:

    confd_client -c db_list
    - Exasol
  2. To find currently defined custom parameters, use the ConfD job db_info. Any custom parameters will be listed in the params: section.

    confd_client -c db_info -a 'db_name: Exasol' | grep params
     params: -forceProtocolEncryption=0 -oidcProviderClientSecret&parameter=-param_name2 -soft_replicationborder_in_numrows=2000000
  3. To remove parameters, use the ConfD job db_configure and specify the parameters to remove. For example:

    confd_client -c db_configure -a '{db_name: Exasol, params_delete: ["-forceProtocolEncryption", "-soft_replicationborder_in_numrows"]}'
  4. To verify that the configuration has been updated, use the ConfD job db_info. Any custom parameters will be listed in the params: section. If no custom parameters are defined, this section will not be included in the response.

    confd_client -c db_info -a 'db_name: Exasol' | grep params
     params: -oidcProviderClientSecret&parameter=-param_name2

Next Steps

Start the database. For more information, see Start a Database.