Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uqtI8-00Ejsk-Ln for pgsql-general@arkaria.postgresql.org; Tue, 26 Aug 2025 13:00:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uqtI8-0062wI-4g for pgsql-general@arkaria.postgresql.org; Tue, 26 Aug 2025 13:00:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uqtI7-0062wA-Pn for pgsql-general@lists.postgresql.org; Tue, 26 Aug 2025 13:00:48 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uqtI6-001xHs-0j for pgsql-general@lists.postgresql.org; Tue, 26 Aug 2025 13:00:48 +0000 Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-33685e3b16aso7680331fa.3 for ; Tue, 26 Aug 2025 06:00:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1756213245; x=1756818045; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=YODVwv09NpVHgiQ1Twhnpdvkz/EB86yvTMGH4DtA10Q=; b=bSiImzQb0GHEmxY2lLW9+WWucoCOfx7vUxvM0ga5x4p1r0IOCPpivt+fZHfH0hlY4G yTKiQ2jC9jjjYzJNjuS6Q4uXgBY+LBMUJcQ51rScyOv9NmXFhZ/VKUzElBm7MB6XsgBT q9cLSbRCcpsytMiIAQBa5UchpKb/A8tY3159NFehKiRNLI6nsTBXkwqUTeffjqAmDOmH CidrkAU6cbKadWhj0Oc/r1U52P+9qrfKdoMeFcCfx4CwKcPM/zcBhtLT+BIdW/3Jo1jA NhecmgAEo5g1bJMsT39BpI5xp/jh3VLFi2UPt2NuXZADaQDE2/yr7hhZW9qIzbDjzenM wWKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756213245; x=1756818045; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=YODVwv09NpVHgiQ1Twhnpdvkz/EB86yvTMGH4DtA10Q=; b=U9wtIT4nU+6bPwePx+i8jcObMyHGhuIj5I+TbsTGb9f3dFJv8mFprU9DUlT7UQgP7A d7HeoycNI5GgYc6KBW4FxwcccXdLaRfufAIyvm/Y1kTdFQaTU1Q/nffMzJASRkPd+KQr gBFDeLCpplObqQ9VU+JaZ8llhwmRQ4leR1oxUIuGk2qKEZntXcmKTXZssnGAwWJukhCx I1dFLt0ntJ/XWvpaJO8IGvviEKZaWlKkBWzHRfE7pH95WiYrmIleMImxk2ROSc7Fx1jj ajfzVnkaJurHPntHI2dlc0vG7JeQYSy691LvdbWJBF4puLWJanb1gpTTPoLCtxoC1zxX cKBw== X-Gm-Message-State: AOJu0YxnW5sIXG1A9fnguaoX9WfLtG+v3Q2Ga4Zz2S2qL+ibBXItbGtC hJkop8TifH3oFgFMMwgShiR0sJo1MTVTtCCqGfucE9VnTrLky2rXhWnHpOUflzNNJtTFqaRfQqF lsDdR963X04cUoiLv1fJHbQBN5a6cb/SGqdyVgNM= X-Gm-Gg: ASbGnctxdU9fERVt01dnx6rO6xLrmOmOqH1RlUnn7rToBAWeyQHUbqoaP1HEUy8qDoS mRISkUm8a8SPKC9WcuOTSmXY/cFF9gCCgfzZ5gW5qUeaWXPhGjzFpkZiPPGBzQS58K+yC8ML2gn a1w5mfFul/IaetZ0xFPgJkyGgH8mpOY9zZG3TwSa1JjoE+i4J/dGmq4qVZI7MwwVpgDErixOhJt XVx2DgNNgmsi9KXsXKpqnOkHFbrHpxP6g19IhG9 X-Google-Smtp-Source: AGHT+IGLaKEyMtGuZgVUPPm5Xi7iSNJz7DQqWEAUl813iKsOcoDzLowo51NnGaEG6YqmC8agD0FXZQo+R+IZVL8Ad6c= X-Received: by 2002:a2e:a54a:0:b0:336:8949:b029 with SMTP id 38308e7fff4ca-3368949bb8emr8067251fa.11.1756213244801; Tue, 26 Aug 2025 06:00:44 -0700 (PDT) MIME-Version: 1.0 From: Siraj G Date: Tue, 26 Aug 2025 18:30:34 +0530 X-Gm-Features: Ac12FXzcFINKn1D7kf003gXcrMeOt6ieBcnbjclklHBqJky3sQvynFVWP3ksy_Q Message-ID: Subject: DMS error where postgres is the destination To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000009b3a4f063d44428a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009b3a4f063d44428a Content-Type: text/plain; charset="UTF-8" Hello Experts! We are replicating data from Oracle to Postgres through GCP DMS. We are getting these errors in the DMS.. I do not think this is a postgres related issue, but trying to see if anyone can shed more light on this. Error: [DATABASE] recover row error: can't recover rollback row AABQbCAAIAAHWzvAAu from "gcp_dms_1eaf1ea0048b635c".t_6510a67e77c26be7 Regards Siraj --0000000000009b3a4f063d44428a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Experts!

We are replicating data from O= racle to Postgres through GCP DMS. We are getting these errors in the DMS..= I do not think this is a postgres related=C2=A0issue, but trying to see if= anyone can shed more light on this.

Error:
<= div>
[DATABASE] recover row error: can't recover rollback= row AABQbCAAIAAHWzvAAu from "gcp_dms_1eaf1ea0048b635c".t_6510a67= e77c26be7

Regards
Siraj
--0000000000009b3a4f063d44428a--