David,

Did you review the data in the field from the two databases?  Maybe the 9i database has all number values while the 10g database has some char values?

Tom

We have Oracle 10.2.0.3.  There is one field, test1 that is definite as char(2).  When we use 'where test1<88', it works fine in 9i, but we get 'ORA-01722 invalid number' error in 10g.  Once I add single quotes around 88, the error is gone.  I know the best practice is not to use implicit conversion.  Just wonder why it works in 9i, but not in 10g, more restriction in 10g or if there is any change in 10g that causes the error tracked?

See what you’re getting into…before you go there. Check it out!