They moved (copied) the target database to a new server running a newer version of Oracle. The problem does not seem to exist on the new one.

The old one is still in place, and I double-checked, and sure enuf, the old server has that LIKE problem.

At least they fixed it. I wonder how many applications around the world it might break if they fix such a big. Sometimes applications get coupled to such bugs by accident, and when they are fixed, kaboom! Has any company used that potential problem as an excuse not to fix bugs? MS?

Thanx