SQL Ambiguous Column
Two joined tables expose the same column name.
LIKELY CAUSE
Why it happens
Qualify the field with a table alias.
SAFE FIX
What to do
Use o.Status or i.Status rather than bare Status.
Debug in this order
- Reproduce the problem on the smallest sample that still fails.
- Inspect the exact keys, types, ranges or markup involved instead of only the displayed value.
- Fix the root cause, then rerun the original case and one known-good case.
- Document the rule if the same problem can return in recurring work.
Do not hide an unexplained data error with a cosmetic workaround. Make the input and matching logic predictable first.