This page describes how to generate AlloyDB Omni system dump files and analyze the causes of unexpected issues.
Before you begin
Ensure that you have installed the AlloyDB Omni CLI.
Generate an AlloyDB Omni dump file
You can manually generate an AlloyDB Omni dump file any time. Examining the dump file helps you or Google Cloud Customer Care analyze issues with your AlloyDB Omni installation, such as deadlocks that block new connections, slow queries, slow vacuum, high usage of memory, CPU, or storage.
To generate a dump file, run the following command:
alloydb database-server system-dump
The command output displays the location of the system dump file.
Review an AlloyDB Omni dump file
An AlloyDB Omni dump file is an ordinary text file that summarizes
various aspects of the system's state. To review it, open it in a text editor, the
less program, or any other program for viewing text files.
AlloyDB Omni saves the file in your data directory, and it names
the file as alloydb_system_dump_ followed by a timestamp. For example,
alloydb_system_dump_20230816_062953PM.
Create a support case for assistance
If you need assistance in interpreting a system dump file to troubleshoot a problem with AlloyDB Omni, then create a support case and attach the file to it. You must have a Google Cloud account to create a support case.
The AlloyDB team responds to the case based on its priority and the respective support service at the time of creation.