Generate and diagnose AlloyDB Omni dump files

Single-server

Before you begin

Extract the alloydb-sysdump utility that is included in the AlloyDB Omni Docker image you installed:

docker run --rm --entrypoint /bin/bash $IMAGE -c "cat /usr/lib/postgresql/15/bin/alloydb-sysdump" > /tmp/alloydb-sysdump
chmod +x /tmp/alloydb-sysdump

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:

sudo /tmp/alloydb-sysdump -D=INSTALL_PATH -U=USERNAME -p=PORT -H=HOSTNAME -c=CONTAINER_NAME

Replace the following:

• INSTALL_PATH: the path to your AlloyDB Omni installation directory accessible from the host file system.
• USERNAME: the name of the user connecting to the database.
• PORT: the TCP port where AlloyDB Omni accepts connections on. The default value is 5432.
• HOSTNAME: the hostname of the machine on which AlloyDB Omni runs. If the value begins with a slash, it is used as the directory for a Unix domain socket. The default value is localhost.
• CONTAINER_NAME: the name of the container in which AlloyDB Omni runs.

The command output displays the location of the system dump file.

To learn more about the command arguments, run:

 /tmp/alloydb-sysdump --help