OpenText Analytics Database 26.2.x – Using diagnostic tools

Admin: Determining your version of OpenText™ Analytics Database

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

To determine which version of OpenText™ Analytics Database is installed on a host, log in to that host and type:

$ rpm -qa | grep vertica

The command returns the name of the installed package, which contains the version and build numbers. The following example indicates that both Vertica 9.3.x and Management Console 9.3.x are running on the targeted host:

$ rpm -qa | grep vertica
vertica-9.3.0-0
vertica-console-9.3.0-0.x86_64

When you are logged in to your database, you can also run a query for the version only, by running the following command:

=> SELECT version();
                  version
-------------------------------------------
 Vertica Analytic Database v9.3.0-0

Admin: Collecting diagnostics: scrutinize command

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

The diagnostics tool scrutinize collects a broad range of information from an OpenText™ Analytics Database cluster. It also supports a range of options that let you control the amount and type of data that is collected. Collected data can include but is not limited to:

Host diagnostics and configuration data
Run-time state (number of nodes up or down)
Log files from the installation process, the database, and the administration tools (such as, vertica.log, dbLog, /opt/vertica/log/adminTools.log)
Error messages
Database design
System table information, such as system, resources, workload, and performance
Catalog metadata, such as system configuration parameters
Backup information

Requirements

scrutinize requires that a cluster be configured to support the Administration Tools utility. If Administration Tools cannot run on the initiating host, then scrutinize cannot run on that host.

Admin: Exporting a catalog

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

When you export a catalog you can quickly move a catalog to another cluster. Exporting a catalog transfers schemas, tables, constraints, projections, and views. System tables are not exported.

Exporting catalogs can also be useful for support purposes.

See the EXPORT_CATALOG function for details.

Admin: Exporting profiling data

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

The diagnostics audit script gathers system table contents, design, and planning objects from a running database and exports the data into a file named ./diag_dump_<timestamp>.tar.gz, where <timestamp> denotes when you ran the script.

If you run the script without parameters, you will be prompted for a database password.

Syntax

/opt/vertica/scripts/collect_diag_dump.sh [ -U value ] [ -w value ] [ -c ]

Arguments

-U value: User name, typically the database administrator account, dbadmin.
-w value: Database password.
-c: Include a compression analysis, resulting in a longer script execution time.

Example

The following command runs the audit script with all arguments:

$ /opt/vertica/scripts/collect_diag_dump.sh -U dbadmin -w password -c