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:
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
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_20240614_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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThis page outlines the process for generating and reviewing AlloyDB Omni system dump files, which are crucial for analyzing issues like deadlocks, slow queries, and high resource usage.\u003c/p\u003e\n"],["\u003cp\u003eYou can generate a dump file using the \u003ccode\u003ealloydb-sysdump\u003c/code\u003e utility, specifying parameters such as the installation path, username, port, hostname, and container name.\u003c/p\u003e\n"],["\u003cp\u003eThe dump file is a plain text file saved in the data directory with a timestamped name, such as \u003ccode\u003ealloydb_system_dump_20240614_062953PM\u003c/code\u003e, and can be opened with any text viewer.\u003c/p\u003e\n"],["\u003cp\u003eIf you need help understanding the dump file, you can create a Google Cloud support case and attach the file for assistance from the AlloyDB team.\u003c/p\u003e\n"]]],[],null,["# Generate and diagnose AlloyDB Omni dump files\n\nSelect a documentation version: 15.5.4keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/manage-dump-files)\n- [16.8.0](/alloydb/omni/16.8.0/docs/manage-dump-files)\n- [16.3.0](/alloydb/omni/16.3.0/docs/manage-dump-files)\n- [15.12.0](/alloydb/omni/15.12.0/docs/manage-dump-files)\n- [15.7.1](/alloydb/omni/15.7.1/docs/manage-dump-files)\n- [15.7.0](/alloydb/omni/15.7.0/docs/manage-dump-files)\n- [15.5.5](/alloydb/omni/15.5.5/docs/manage-dump-files)\n- [15.5.4](/alloydb/omni/15.5.4/docs/manage-dump-files)\n- [15.5.2](/alloydb/omni/15.5.2/docs/manage-dump-files)\n\n\u003cbr /\u003e\n\nThis page describes how to generate AlloyDB Omni system dump files and analyze the causes of unexpected issues.\n\n\u003cbr /\u003e\n\n### Single-server\n\nBefore you begin\n----------------\n\nExtract the `alloydb-sysdump` utility that is included in the AlloyDB Omni Docker image you [installed](/alloydb/omni/15.5.4/docs/install): \n\n docker run --rm --entrypoint /bin/bash $IMAGE -c \"cat /usr/lib/postgresql/15/bin/alloydb-sysdump\" \u003e /tmp/alloydb-sysdump\n chmod +x /tmp/alloydb-sysdump\n\nGenerate an AlloyDB Omni dump file\n----------------------------------\n\nYou can manually generate an AlloyDB Omni dump file any time. Examining\nthe dump file helps you or Google Cloud Customer Care analyze issues with your AlloyDB Omni\ninstallation, such as deadlocks that block new connections, slow queries, slow\nvacuum, high usage of memory, CPU, or storage.\n\nTo generate a dump file, run the following command: \n\n sudo /tmp/alloydb-sysdump -D=\u003cvar translate=\"no\"\u003eINSTALL_PATH\u003c/var\u003e -U=\u003cvar translate=\"no\"\u003eUSERNAME\u003c/var\u003e -p=\u003cvar translate=\"no\"\u003ePORT\u003c/var\u003e -H=\u003cvar translate=\"no\"\u003eHOSTNAME\u003c/var\u003e -c=\u003cvar translate=\"no\"\u003eCONTAINER_NAME\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eINSTALL_PATH\u003c/var\u003e: the path to your AlloyDB Omni installation directory accessible from the host file system.\n- \u003cvar translate=\"no\"\u003eUSERNAME\u003c/var\u003e: the name of the user connecting to the database.\n- \u003cvar translate=\"no\"\u003ePORT\u003c/var\u003e: the TCP port where AlloyDB Omni accepts connections on. The default value is `5432`.\n- \u003cvar translate=\"no\"\u003eHOSTNAME\u003c/var\u003e: 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`.\n- \u003cvar translate=\"no\"\u003eCONTAINER_NAME\u003c/var\u003e: the name of the container in which AlloyDB Omni runs.\n\nThe command output displays the location of the system dump file.\n\nTo learn more about the command arguments, run: \n\n /tmp/alloydb-sysdump --help\n\nReview an AlloyDB Omni dump file\n--------------------------------\n\nAn AlloyDB Omni dump file is an ordinary text file that summarizes\nvarious aspects of the system's state. To review it, open it in a text editor, the\n`less` program, or any other program for viewing text files.\n\nAlloyDB Omni saves the file in your data directory, and it names\nthe file as `alloydb_system_dump_` followed by a timestamp. For example,\n`alloydb_system_dump_20240614_062953PM`.\n\nCreate a support case for assistance\n------------------------------------\n\nIf you need assistance in interpreting a system dump file to troubleshoot a\nproblem with AlloyDB Omni, then [create a support case](/support/docs/manage-cases#creating_cases) and attach the file to it. You must have\na Google Cloud account to create a support case.\n\nThe AlloyDB team responds to the case based on its priority and\nthe respective support service at the time of creation."]]