Current Oracle DB I am using is 'Oracle Database 12c Enterprise Edition Release - 64bit' and we have a use case for using 'Oracle 12.2.X.X.0'. We want to use the elongated object name lengths of 128 which come with Oracle 12.2

Is Oracle 12.2 backward compatible and supports everything on Oracle 12.1? Like Stored Procs, JBDC connections etc.

If new tables & columns with long names on 12.2 start coming in, Can those tables be used in conjunction with tables created on 12.1 for joins etc., and can they start residing in the same schemas?

  • The biggest risk is your old app, it must be able to deal with the longer names (and use the new JDBC driver version). Btw if you invest now to upgrade you should go to the final update of the 12.2 family, which is 19c.
    – eckes
    Sep 16, 2019 at 21:59

1 Answer 1


Here is the list of changes:

Behavior Changes, Deprecated and Desupported Features for Oracle Database 12c Release 2 (12.2)

Such basic functionality that you mentioned (table joins, stored procedures, JDBC connections) should of course work.

Sure, there are new features, and some changes, but I can not recall anything significant related to those areas that worked in 12.1 but did not in 12.2.

  • With over 35 years in this business, I confidently predict that if you start making use of 'enlongated' object names, you will soon come to regret it. I fail to understand why oracle ever allowed it. I found that even the 30-character limit to waaaay more than any reasonable object name could require.
    – EdStevens
    Sep 16, 2019 at 21:25
  • Stock naming e.g in datamodeler tend to generate quite long names. Mix this with some fancy naming guidelines and Oracle 20 will support 512 character object names :)
    – jmk
    Sep 17, 2019 at 16:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.