This guide explains why OBD 3.6.0 mistakenly removes the primary tenant when deleting a standby tenant, demonstrates the issue with step‑by‑step commands and outputs, and provides a reliable procedure—decoupling, dropping, or failover—to safely delete or promote standby tenants.
This article describes how to identify and fix Greenplum standby segment failures by inspecting segment status, comparing missing files, generating a recovery configuration, executing gprecoverseg commands, and verifying that all segments return to normal operation without service interruption.
A detailed walkthrough shows how a mismatched COMPATIBLE parameter caused ORA-600 errors that blocked log apply on an Oracle 11.2.0.4 standby, and explains the step‑by‑step queries, diagnostics, and commands needed to correct the issue and resume synchronization.
A single‑instance Oracle 11.2.0.4 primary‑standby setup on Windows encountered ORA‑600 errors on archived logs 17620 and 17621 after manual file deletions, and the detailed troubleshooting revealed a mismatched COMPATIBLE parameter that was corrected, allowing the standby to apply the missing logs and resume synchronization.
This guide walks through preparing the primary and standby Oracle 11g databases on RH Linux, configuring listeners, tnsnames, force logging, adding standby redo logs, editing parameter files, transferring files with RMAN, verifying roles, activating Active Data Guard, using snapshot standby, switching logs, and setting an archive‑log deletion policy.
