Anda dapat membuat file dump AlloyDB Omni secara manual kapan saja. Memeriksa
file dump membantu Anda atau Google Cloud Layanan Pelanggan menganalisis masalah terkait penginstalan AlloyDB Omni, seperti kebuntuan yang memblokir koneksi baru, kueri lambat, vakum lambat, penggunaan memori, CPU, atau penyimpanan yang tinggi.
Untuk membuat file dump, jalankan perintah berikut:
INSTALL_PATH: jalur ke direktori penginstalan AlloyDB Omni Anda yang dapat diakses dari sistem file host.
USERNAME: nama pengguna yang terhubung ke database.
PORT: port TCP tempat AlloyDB Omni menerima koneksi.
Nilai defaultnya adalah 5432.
HOSTNAME: nama host
mesin tempat AlloyDB Omni berjalan.
Jika nilai dimulai dengan garis miring, nilai tersebut akan digunakan sebagai
direktori untuk soket domain Unix.
Nilai defaultnya adalah localhost.
CONTAINER_NAME: nama
penampung tempat AlloyDB Omni berjalan.
Output perintah menampilkan lokasi file dump sistem.
Untuk mempelajari lebih lanjut argumen perintah, jalankan:
/tmp/alloydb-sysdump--help
Meninjau file dump AlloyDB Omni
File dump AlloyDB Omni adalah file teks biasa yang merangkum berbagai aspek status sistem. Untuk meninjaunya, buka di editor teks, program
less, atau program lain untuk melihat file teks.
AlloyDB Omni menyimpan file di direktori data Anda, dan memberi nama
file sebagai alloydb_system_dump_ yang diikuti dengan stempel waktu. Contoh, alloydb_system_dump_20240614_062953PM.
Buat kasus dukungan untuk mendapatkan bantuan
Jika Anda memerlukan bantuan dalam menafsirkan file dump sistem untuk memecahkan masalah pada AlloyDB Omni, buat kasus dukungan dan lampirkan file tersebut ke kasus dukungan. Anda harus memiliki
akun Google Cloud untuk membuat kasus dukungan.
Tim AlloyDB akan merespons kasus berdasarkan prioritasnya dan
layanan dukungan yang relevan pada saat pembuatan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis guide details how to generate system dump files for AlloyDB Omni, which are essential for analyzing and troubleshooting unexpected issues.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ealloydb-sysdump\u003c/code\u003e utility, extracted from the AlloyDB Omni Docker image, is used to create these dump files.\u003c/p\u003e\n"],["\u003cp\u003eTo generate a dump file, you need to use a specific command with details such as the installation path, username, port, hostname, and container name.\u003c/p\u003e\n"],["\u003cp\u003eDump files are stored in your data directory, and they are text files that summarize the system's state at the time they were created, identifiable by a timestamp in their name.\u003c/p\u003e\n"],["\u003cp\u003eIf you need help interpreting a dump file, you can create a support case and attach it, ensuring you have a Google Cloud account.\u003c/p\u003e\n"]]],[],null,["# Generate and diagnose AlloyDB Omni dump files\n\nSelect a documentation version: Current (16.8.0)keyboard_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\nBefore you begin\n----------------\n\nExtract the `alloydb-sysdump` utility that is included in the AlloyDB Omni Docker image you [installed](/alloydb/omni/current/docs/install): \n\n### Docker\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\n### Podman\n\n podman 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\n The command output displays the location of the system dump file.\n\n To 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."]]
