[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-02 (世界標準時間)。"],[[["\u003cp\u003eThis page outlines error codes encountered in AlloyDB Omni, along with their descriptions and recommended fixes.\u003c/p\u003e\n"],["\u003cp\u003eError codes are extracted by checking the database cluster status conditions and \u003ccode\u003ecriticalincidents\u003c/code\u003e fields in the database cluster manifest obtained via \u003ccode\u003ekubectl\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eErrors such as \u003ccode\u003eDBSE0601\u003c/code\u003e and \u003ccode\u003eDBSE0604\u003c/code\u003e relate to pgBackRest failures during backup or restore processes, requiring checks of pgBackRest and PostgreSQL logs.\u003c/p\u003e\n"],["\u003cp\u003eErrors like \u003ccode\u003eDBSE1080\u003c/code\u003e, \u003ccode\u003eDBSE1081\u003c/code\u003e, and \u003ccode\u003eDBSE1082\u003c/code\u003e indicate issues with primary database stopping, standby promotion, or database rewinding during failover or switchover, which might require manual database repair or recreation.\u003c/p\u003e\n"],["\u003cp\u003eErrors like \u003ccode\u003eDBSE2411\u003c/code\u003e to \u003ccode\u003eDBSE2418\u003c/code\u003e point to replication-related problems, such as failing to set up replication, issues with synchronous standby names, or failed replication terminations, all of which require consulting the error message and potentially restarting the replication process.\u003c/p\u003e\n"]]],[],null,["# Diagnose error codes\n\nSelect a documentation version: 15.7.0keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/error-codes)\n- [16.8.0](/alloydb/omni/16.8.0/docs/error-codes)\n- [16.3.0](/alloydb/omni/16.3.0/docs/error-codes)\n- [15.12.0](/alloydb/omni/15.12.0/docs/error-codes)\n- [15.7.1](/alloydb/omni/15.7.1/docs/error-codes)\n- [15.7.0](/alloydb/omni/15.7.0/docs/error-codes)\n\n\u003cbr /\u003e\n\nThis page describes AlloyDB Omni error codes and recommended fixes.\n\n\u003cbr /\u003e\n\nExtract an error\n----------------\n\nTo extract an error code, follow these steps:\n\n1. To get your database cluster manifest, run:\n\n kubectl get dbclusters.a \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e -n \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAMESPACE\u003c/var\u003e -o yaml\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e: the name of your database cluster---for example, `my-db-cluster`.\n - \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAMESPACE\u003c/var\u003e: the name of the namespace of your database cluster.\n2. Check for database cluster status conditions and `criticalincidents` fields that might have some of the following error codes.\n\nAlloyDB Omni error codes\n------------------------"]]