OpenText Analytics Database 26.2.x – Database management

Mc: Creating a database using MC

Mon, 01 Jan 0001 00:00:00 +0000

If you installed the Management Console using an RPM, there is a wizard to help you create a new database on an existing database cluster.

Note

If you did not install MC with an RPM, see one of the following:

For Management Console on Amazon Web Services (AWS) using a CloudFormation Template, see Creating an Eon Mode database in AWS with MC or Creating an Enterprise Mode database in AWS with MC.
For Google Cloud Platform (GCP), see Provision an Eon Mode cluster and database on GCP in MC.
To provision a new database and cluster on-premises, see Creating a cluster using MC.

Connect to Management Console, and log in.
On the home page, click View Infrastructure to go to the Database and Cluster View. This tab provides a summary of your environment, clusters, and databases.
If the Database row displays a database running on the cluster that you want to add a new database to, select the database and click Stop. Wait until the database status is Stopped.
In the Clusters row, click the existing cluster that you want to create a database on. If a database is already running on it, you must stop the database.
Click Create Database in the window to start the database creation wizard.
Follow the steps in the wizard to successfully create a database.

You can close the web browser during the process and sign back in to MC later. The creation process continues unless an unexpected error occurs.

Mc: Provisioning databases using MC

Mon, 01 Jan 0001 00:00:00 +0000

Management Console allows all users to create, import, and connect to databases using the MC Provision Databases tab.

Import cluster or database using IP discovery
Create a new cluster
Import and monitor a database in a Hadoop environment

Mc: Managing database clusters

Mon, 01 Jan 0001 00:00:00 +0000

Management Console allows you to monitor multiple databases on one or more clusters at the same time. MC administrators can see and manage all databases and clusters monitored by MC, while non-administrative MC users see only databases on which they have been assigned the appropriate access levels.

Depending on your access level, you can use the MC to perform the following database and cluster-related management operations:

Create an Eon Mode and Enterprise Mode database.
Install an Eon Mode and Enterprise Mode database in a cloud or on-premises environment.
Create an empty database in an existing cluster.
Import an existing database or cluster into the MC interface.
Start the database, unless it is already running.
Stop the database, if no users are connected.
Remove the database from the MC interface.

Note
Remove does not drop the database. A Remove operation leaves it in the cluster, hidden from the UI. To add the database back to the MC interface, import it using the IP address of any cluster node. A Remove operation also stops metrics gathering on that database, but statistics gathering automatically resumes after you re-import.
Drop the database when you are certain that no users are connected. Drop is a permanent action that drops the database from the cluster.

Database clusters in the cloud

When you use the Management Console to create a database or cluster on a supported cloud provider, you can perform the following operations on individual machines or the entire cluster:

Start
Stop
Revive
Reboot
Terminate

For details, see Viewing and managing your cluster.

Mc: Subclusters in MC

Mon, 01 Jan 0001 00:00:00 +0000

In Eon Mode databases, you can use subclusters (groups of nodes) to separate different workloads, to control how those workloads use resources, and to facilitate scaling your database up and down as workloads fluctuate. This allows you to better manage your cloud resource expenses or data center resources. For an overview of subcluster concepts and how subclusters work, see Subclusters.

MC makes it easy to view and manage your subclusters. You can track how queries are performing and how well your subcluster resources are balanced. Using MC, you can use the information to adjust the number and size of your subclusters to improve your query throughput and system performance.

Visualizing your subclusters

The charts on the Database Overview page allow you to view and drill down into the resource usage of your database at any level. You can look at the resource usage of all nodes, or all subclusters, or individual subclusters. For details, see Charting subcluster resource usage in MC.

You can view statistics for the individual nodes in each subcluster in table format on the Database Manage page, in the Subclusters tab.

For a tour of the monitoring features of the Manage > Subclusters tab, see Viewing subcluster layout in MC.

Managing your subclusters

For Eon Mode databases, MC supports actions for subcluster and node management for the following public and private cloud providers:

Note

Enterprise Mode does not support subclusters.

For Enterprise Mode databases, MC supports these actions:

In the cloud on AWS: Add Node action, Add Instance action.
On-premises: Add Node action.

Note

In the cloud on GCP, Enterprise Mode databases are not supported.

To view and manage your subclusters, select your database from the MC Home page or the Databases and Clusters page. MC displays your database's Overview page. Select Manage at the bottom of the Overview page.

To view the Subclusters page, click the Manage > Subclusters tab:

Eon Mode in the cloud

In Eon Mode on cloud platforms, you can use the Manage > Subclusters tab to add subclusters, rebalance your subclusters, stop and start subclusters, scale subclusters up or down, or terminate a subcluster. You can also stop or start a node, or restart a database node and its underlying instance.

Eon Mode on-premises

In Eon Mode on-premises, available subcluster and node actions behave a little differently than in the cloud, because your database nodes reside on actual machines in your data center rather than on cloud instances.

Subcluster Actions in Eon Mode on Premises

In Eon Mode on-premises, you can use the Manage > Subclusters tab to add subclusters, rebalance your subclusters, or delete a subcluster.
You can add (create) a subcluster only if additional database host machines are available.
When you delete a subcluster, MC deletes the subcluster from the database but does not delete the actual machines. MC stops the nodes in the subcluster, removes them from the subcluster, and deletes the subcluster. The database host machines are then available to be added to other subclusters.
When you start or stop a subcluster in an Eon Mode database on-premises, MC starts or stops the subcluster nodes on the database host machines, but not the machines themselves.
When you scale up a subcluster on-premises, the MC wizard displays a list of the available database host machines that are not currently part of a database. You select the ones you want to add to the subcluster as nodes, then confirm that you want to scale up the subcluster.

When you scale down a subcluster on-premises, MC removes the nodes from the subcluster in the database, but does not terminate the database host machines. The hosts are now available for scaling up other subclusters.
Scale Up displays the IP addresses of all available database hosts that are not part of the database. The Scale Up button is grayed out if there are no database hosts in the cluster that are not part of the database.

Node actions in Eon Mode on premises

When you start or stop a node on-premises, MC starts or stops the node in the database, but does not start or stop the database host machine. The Restart Node action is not available for on-premises Eon Mode databases.

Mc: Eon Mode on-premises

Mon, 01 Jan 0001 00:00:00 +0000

Mc: Managing queries using MC

Mon, 01 Jan 0001 00:00:00 +0000

Management Console allows you to view the query plan of an active query or a manually entered query specified by the user.

On the MC Home Page, click the database you want to view the Overview page.
Select the Activity tab to view the query activity.
Click the Explain tab to access the query plan.

See Working with query plans in MC and Accessing query plans in Management Console for further information.

Management Console provides two options for viewing the query plan: Path Information and Tree Path. For details on each, refer Query plan view options.

Additionally, you can also Viewing projection and column metadata using the MC Explain tab.

Mc: Working with query plans in MC

Mon, 01 Jan 0001 00:00:00 +0000

Management Console can show you a query plan in easy-to-read format, where you can review the optimizer's strategy for executing a specific query. You can view a query plan in either of two ways:

View the plan of an active query.
View the plan for any query that you manually specify.

Access the plan of an active query

At the bottom of the Management Console window, click the Activity tab.
From the list at the top of the page, select Queries.
On the activity graph, click the data point that corresponds to the query you want to view.
In the View Plan column, click Explain next to the command for which you want to view the query plan. Only certain queries use query plans—for example, SELECT, INSERT, DELETE, and UPDATE.
In the Explain Plan window, click Explain. The database generates the query plan.
(Optional) View the output in Path Information view or Tree Path view. To do so, click the respective view buttons on the left of the output box.

Access the plan for a specific query

Locate the query for which you want to see the query plan in either of the following ways:
- Queries Not Running — In the Explain window, type or paste the query text into the text box.
- Queries Currently Running — In the Find a Query By ID input window, perform one of the following actions:
  - Enter the query statement and transaction ID.
  - Click the Browse Running Queries link.
Caution
Entering the word EXPLAIN before the query results in a syntax error.
Click Explain. The database generates the plan.

If the query is invalid, Management Console highlights in red the parts of your query that might have caused a syntax error.
(Optional) View the output in Path Information view or Tree Path view. To do so, click the respective view buttons on the left of the output box.

Mc: Creating a database design in Management Console

Mon, 01 Jan 0001 00:00:00 +0000

Database Designer creates an design that provides excellent performance for ad-hoc queries and specific queries while using disk space efficiently. Database Designer analyzes the logical schema definition, sample data, and sample queries, and creates a physical schema that you can deploy.

For more about how Database Designer works, see the Creating a database design section of the documentation, and About Database Designer.

To use Management Console to create an optimized design for your database, you must be a DBADMIN user or have been assigned the DBDUSER role.

Management Console provides two ways to create a design:

Wizard—This option walks you through the process of configuring a new design. Click Back and Next to navigate through the Wizard steps, or Cancel to cancel creating a new design.

To learn how to use the Wizard to create a design, see Using the wizard to create a design.
Manual—This option creates and saves a design with the default parameters.

To learn how to create a design manually, see Creating a design manually.

Tip

If you have many design tables that you want Database Designer to consider, it might be easier to use the Wizard to create your design. In the Wizard, you can submit all the tables in a schema at once; creating a design manually requires that you submit the design tables one at a time.

Mc: Running queries in Management Console

Mon, 01 Jan 0001 00:00:00 +0000

You can use the Query Runner to run SQL queries on your database through Management Console (MC). After executing a query, you can also get the query plan and profile information for the query on this page.

To reach the Query Runner, select your database from the Home page or the Databases and Clusters page to view your database's Overview page. Select Query Execution at the bottom of the Overview page.

To familiarize yourself with how queries work in OpenText™ Analytics Database, you can refer to the Queries section of the documentation, as well as the SQL reference.

Limitations

You cannot execute COPY LOCAL statements using the Query Runner. To do so, use the vsql client installed on the server. See Using vsql. (To use MC to import data from Amazon S3 storage to your database, see Loading data from Amazon S3 using MC.)

Manually commit any transactions (INSERT and COPY statements) you perform by adding the COMMIT statement in the text box after the transaction statements. If you do not do so, the transaction rolls back.

In the following example, to insert values into table1, include a COMMIT statement in the text box and execute the two statements together: INSERT INTO table1 VALUES (1,2); COMMIT;

Format

To input a series of queries, delimit them with a semicolon (;).

To automatically format the SQL text you have input, click the Format icon ().

Privileges

It is important when running queries in MC that the database administrator has correctly set up MC user privileges. The administrator must map all MC user profiles to their corresponding database user.

The Query Runner only permits MC users to perform actions that their corresponding database roles allow.

To set up user mappings, go to Home > MC Settings > User Management.

For more about how mapping MC user profiles to database users works, see Database privileges. For information about database-level users and privileges, see the Database users and privileges section of the documentation.

Execute a query

The Query Runner provides several ways to input a query to run:

Input text. Enter the text for a query or series of queries into the text box.
Import a SQL script. Click the Upload icon () to the top right of the text box to upload a SQL script (plain text file, typically with an extension of .sql). The queries from that file appears in the text box.
Enter a previous query from the Query History tab. The Query History tab, on the left side of the page, displays the last 100 queries you have executed using the Query Runner on your current device and browser. Click any previous query in this tab to enter that query into the text box.

Hover over a query in the Query History tab to view all the query text. To clear queries from your history, hover over an individual query and click x, or click Clear all at the top of the tab. Click the star to the left of any query to favorite it, so it won't be cleared when you click Clear all.

Cick Execute Query to run the queries you have input.

You can also execute only a portion of the text entered into the text box, as long as the selected text is a valid query. To do so, select that portion of the text. The Execute selected text as query button then appears below the text box.

For example, you might execute only a part of the entered text if you have uploaded a SQL script that containing multiple queries, but you decide to run only one of those queries.

To customize your execution settings, click the Settings icon () at the top right of the text box:

Row Limit: Set the maximum number of rows to return. By default, the limit is 10000 rows.
Search Path: Specify the schema to query.

Get query results

The Query Runner returns results in a table format. If you ran multiple queries simultaneously, the results window displays a tab for each set of results. View the number of rows returned and the query execution time at the bottom of the results window.

If your result returns many columns, you can click Auto-resize all columns in the top right of the results window for a better fit, or click and drag column borders to manually resize individual columns.

Sort results by clicking on a column name, or use the search bar to narrow down results.

Query plans and profiles

Each query result also displays an option to retrieve the plan or profile for that query.

After retrieving a plan or profile, you can expand or collapse the results view to see different levels of detail. To view metadata for a projection or a column, click the object name in the path output. A pop-up window displays the metadata, if it is available.

Note that the Query Runner does not automatically provide query profiles for queries that run for less than 1 second. To do so, prepend the word PROFILE to the query and run it.

You can also profile your query on the Query Plan page. The Query Plan page provides more details about both plan and profile results, including a query plan drilldown by node, a tree path view, and a profile analysis.

Keyboard shortcuts

The Query Runner provides the following keyboard shortcuts:

?: Press the question mark to display or dismiss a list of the available keyboard shortcuts. (You can also click the question mark icon at the top right of the text box to view this list.)
alt + ↑: Press alt + up arrow to decrease the height of the text box.
alt + ↓: Press alt + down arrow to increase the height of the text box.
ctrl + enter: Press ctrl + enter to run the query.
ctrl + shift + enter: Press ctrl + shift + enter to run selected text.

Mc: Working with workload analyzer recommendations in MC

Mon, 01 Jan 0001 00:00:00 +0000

If queries perform sub-optimally, use Workload Analyzer to get tuning recommendations and hints about optimizing database objects.

Workload Analyzer is a utility that analyzes system information in the database system tables. It then returns a set of tuning recommendations based on statistics, system and data collector events, and database/table/projection design. You can use these recommendations to tune query performance.

Configuring the workload analyzer execution time

By default, Workload Analyzer runs each day at 2 AM. To optimize when Workload Analyzer uses resources, you can set Workload Analyzer to run at a different time for any or all databases that Management Console monitors. Alternately, you can set Management Console to never run Workload Analyzer automatically.

Note

Workload Analyzer automatically begins monitoring data one minute after the Management Console process starts. Workload Analyzer then runs once per day, or immediately after you import a database to Management Console. It continually gathers data in the background as long as the database is running. If you have not yet created a database, or if the database is down, Workload Analyzer does nothing until the database is back up.

On the Home page, click MC Settings.
Click the Monitoring tab.
Under the Workload Analyzer Assistant section of the Monitoring page, select your time zone.
Select the radio button for one of the options:
- All Databases: Select a time from the list. Workload Analyzer will run at that time on all databases that MC monitors.
- Specific Database at Specific Time: Select a database and a time from the list. At the time you specify, Workload Analyzer will run at that time on the database you selected.
- Do Not Run Workload Analyzer On Any Database: MC will never run Workload Analyzer automatically on any database it monitors.
Click Apply at the top right of the page.

For additional information about tuning recommendations and their triggering event, see Workload analyzer recommendations.

View workload analyzer recommendations

Workload Analyzer recommendations are available from the Quick Stats sidebar on the right of the database's Overview page. The Workload Analyzer module displays the number of tuning recommendations that the Workload Analyzer has generated.

To view the Workload Analyzer Results on the Database Designer page, click the number in the Workload Analyzer module.

The Workload Analyzer Results window allows you to view details about and perform actions using current and processed recommendations.

Click the Current Recommendations radio button to display available Workload Analyzer recommendations. When ANALYZE_STATISTICS is returned as a tuning recommendation, select the check mark to the left of the row and click Run Selected Recommendations to execute the recommendation automatically.

Click the Processed Recommendations radio button to display the Workload Analyzer recommendations that you previously executed. To remove a recommendation from the list, click the check mark to the left of the row and click Clear, located above the Close button in the bottom-right of the window. To expand or hide the processed recommendation's execution history, click the plus or minus sign to the left of the row.

You can force the Workload Analyzer task to run immediately by clicking Update Recommendations, located above the Status column.

The total recommendations and the number of recommendations currently selected to run are displayed under the recommendations grid. Use the settings under the grid to view more recommendations per page or to cycle through the recommendations that do not fit on the page.

The following columns are used to describe recommendations:

Tuning Description — Describes the Workload Analyzer recommendation.
Tuning Cost — Resource cost of running each command (LOW, MEDIUM, or HIGH).

Tip
When the tuning cost is HIGH, consider running the recommended tuning during off-peak load times.
Tuning Command — SQL command used to execute the recommendation.
Last Executed On — Date that the recommendation was last run. In MM/DD/YYYY format.
Status — Describes the execution stage of a tuning recommendation ran from Workload Analyzer Results.

For more information about tuning recommendations, see Getting tuning recommendations and ANALYZE_WORKLOAD.

Running workload analyzer recommendations to optimize a query

When the Workload Analyzer recommends that you run ANALYZE_STATISTICS to optimize a query, you can run the recommendation automatically from Workload Analyzer Results.

Record the data source and execution time for a query that is running sub-optimally.
1. Click the Query Execution tab at the bottom.
2. Use the Query Runner to execute a query that you want to optimize.
3. Record the database table or tables in the query's FROM clause, and record the Execution time, located under the Query Results table.
Click the Overview tab at the bottom of the window.
On the Overview page, click the number in the Workload Analyzer box on the right.

Workload Analyzer Results opens.
To filter the recommendations, enter the sub-optimal query's database table or tables in the field at the top of the Tuning Description column.
Select one or more ANALYZE_STATISTICS recommendations by clicking the check mark to the left of the row. To select all of the filtered ANALYZE_STATISTICS recommendations, click the check mark to the left of the Tuning Description column header.
Click Run Selected Recommendations, located in the bottom-right of the window.
This process might take several minutes.
After the tuning recommendations are completed, click the Processed Recommendations radio button at the top of the window.
The previously executed recommendations are displayed.
Locate any recommendations that you just executed, and verify that the Status column says COMPLETED.
Verify that the query was optimized.
1. Click the Query Execution tab at the bottom of the Management Console.
2. Execute the query that was performing sub-optimally. Note the Execution time under the query results to verify the performance increase.

Mc: Running Database Designer using MC

Mon, 01 Jan 0001 00:00:00 +0000

You can use Database Designer to create a comprehensive design, which allows you to create new projections for all tables in your database.

Additionally, you can use Database Designer to create an incremental design. An incremental design creates projections for all tables referenced in the queries you supply.

To run Database Designer using MC, follow the steps listed at Running Database Designer with Management Console.

Mc: Using the Management Console to replace nodes

Mon, 01 Jan 0001 00:00:00 +0000

On the MC Manage page, you can quickly replace a DOWN node in the database by selecting one of the STANDBY nodes in the cluster.

A DOWN node shows up as a red node in the cluster. Click the DOWN node and the Replace node button in the Node List becomes activated, as long as there is at least one node in the cluster that is not participating in the database. The STANDBY node will be your replacement node for the node you want to retire; it will appear gray (empty) until it has been added to the database, when it turns green.

Tip

You can resize the Node List by clicking its margins and dragging to the size you want.

When you highlight a node and click Replace, MC provides a list of possible STANDBY nodes to use as a replacement. After you select the replacement node, the process begins. A node replacement could be a long-running task.

MC transitions the DOWN node to a STANDBY state, while the node you selected as the replacement will assume the identity of the original node, using the same node name, and will be started.

Assuming a successful startup, the new node will appear orange with a status of RECOVERING until the recovery procedure is complete. When the recovery process completes, the replacement node will turn green and show a state of UP.

Mc: Import and monitor a database in a Hadoop environment

Mon, 01 Jan 0001 00:00:00 +0000

You can use Management Console to connect to and monitor a database that resides in an Apache Hadoop environment. To monitor the database in the Hadoop environment, you must connect to an Apache Ambari server.

Prerequisites

Before you begin, you must:

Install OpenText™ Analytics Database on a Hadoop cluster.
Install Apache Ambari version 1.6.1 or 2.1.0.
Enable Ganglia on your Hadoop cluster, to get the most information from your Hadoop environment.

Importing the database within a Hadoop environment

To import your database that resides in a Hadoop environment, connect to that Hadoop environment in Management Console through an Apache Ambari server.

From the Management Console home page, select Additional import options.
In Provisioning, select Connect using an Ambari server to impot Vertica within a Hadoop environment.
The Provision Access Within Hadoop Environment window provides the following options:
- Connect to a new Ambari server: Choose this option to create a enter your username and password for a new Ambari server connection.
- Known Ambari URLs: If you have a pre-existing Ambari connection that you want to use, select it from the drop-down list.
In the next window, select the Hadoop cluster with the database that you want to monitor.
Management Console automatically discovers Hadoop clusters that are currently monitored by the Ambari server that you specify. If Management Console does not monitor database clusters in the specified Hadoop environment, you can import clusters at this time.
After you select the Hadoop cluster, you receive confirmation that your Hadoop cluster is saved.
Enter the IP address for the database you want to import and monitor. If the database is running on multiple hosts, enter the IP address of one of them.
Enter the API key for the database cluster. The API key is generated during database installation, and you can find it in the /opt/vertica/config/apikeys.dat file.
The next window displays the discovered databases. Select one or more databases you want to import, and enter the corresponding username and password.
If the import is successful, you receive a success message. Click Done to go to the Existing Infrastructure page.

To import an additional database cluster within a Hadoop environment, click Import Cluster or database using IP address discovery under Provisioning. Management Console will automatically associate the cluster with the existing Hadoop environment.

Monitoring the database within a Hadoop environment

To monitor the database clusters in a Hadoop environment, navigate to the Existing Infrastructure page:

Click to select the Hadoop environment, and then click View Vertica Databases.

The Management Console displays information about the databases that reside in a Hadoop environment:

You can monitor information like resource usage, Hadoop services, and database and connection status.

Update or remove an ambari connection

To update or remove an existing Ambari connection, go to the MC Existing Infrastructure page, and click on the relevant Hadoop environment.

To update a connection, click Update Ambari Connection. Step through the wizard to update the connection.

To remove a connection, select Update Ambari Connection and choose Remove Connection, or click Discontinue Monitoring and then confirm that you want to remove the connection. Removing the connection also removes all databases associated with this connection from MC monitoring. You can re-import the databases later if needed.

OpenText Analytics Database 26.2.x – Database management

Mc: Creating a database using MC

Note

See also

Mc: Provisioning databases using MC

Mc: Managing database clusters

Note

Database clusters in the cloud

Mc: Subclusters in MC

Visualizing your subclusters

Managing your subclusters

Note

Note

Eon Mode in the cloud

Eon Mode on-premises

Node actions in Eon Mode on premises

Mc: Eon Mode on-premises

Mc: Managing queries using MC

See also

Mc: Working with query plans in MC

Access the plan of an active query

Access the plan for a specific query

Caution

Mc: Creating a database design in Management Console

Tip

Mc: Running queries in Management Console

Limitations

Format

Privileges

Execute a query

Get query results

Query plans and profiles

Keyboard shortcuts

See also

Mc: Working with workload analyzer recommendations in MC

Configuring the workload analyzer execution time

Note

View workload analyzer recommendations

Tip

Running workload analyzer recommendations to optimize a query

See also

Mc: Running Database Designer using MC

Mc: Using the Management Console to replace nodes

Tip

Mc: Import and monitor a database in a Hadoop environment

Prerequisites

Importing the database within a Hadoop environment

Monitoring the database within a Hadoop environment

Update or remove an ambari connection

See also: