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.
A rare Oracle bug caused object IDs to exceed their maximum value, preventing creation of tables, sequences, and indexes; the article analyzes the error, shows how rapid DDL activity exhausts IDs, demonstrates reproduction steps, and offers short‑ and long‑term mitigation and monitoring recommendations.
