To which release should you upgrade to? Plus: Extended Support?

A few days ago I blogged about the Current Support Status for Oracle Database Releases. And you’ve sent several questions to me. Some asked about clarification to which release should you upgrade to? Plus: Extended Support questions were quite frequent. So let me clarify this previous blog post a bit. To which release should you upgrade to? A few weeks ago we initiated global communication to all customers who had opened an SR within the past 3 years explaining to which release you should upgrade to. Just in case you haven’t seen this communication, I will give you more details…

Oracle 12.2 and higher: Set _cursor_obsolete_threshold to old default

Sometimes development groups change default parameter settings because it fits well for a specific feature. This has happened with _cursor_obsolete_threshold in Oracle Database 12.2. But there’s now an official recommendation for Oracle 12.2 and higher: Set _cursor_obsolete_threshold to old default. What is _cursor_obsolete_threshold? First of all, this is obviously an underscore parameter. And usually the policy is: Don’t change underscore parameters unless either you clearly understand what you are changing. Or unless Oracle Support (or another Oracle authority) advises you to do. We introduced this parameter in Oracle 11.2.0.3 for an issue of growing child cursors. An enhancement request was…

Drop public synonym XMLCONCAT prior to upgrade

Thanks to my team mates, Cindy and Hector, who alerted me on this newly detected issue. When your database has been upgraded from release to release, it could happen that a public synonym XMLCONCAT exists. And before you upgrade to Oracle 12.2.01 or Oracle 18c you must drop this public synonym to avoid upgrade errors. Drop public synonym XMLCONCAT prior to upgrade The public synonym XMLCONCAT in pre-9.2.0.2 Oracle databases pointed to a PL/SQL function of the same name. In 9.2.0.2, this PL/SQL function was changed to a C function.The public synonym was no longer needed nor pointing to a…

Clarification: Support Periods for Oracle 12.2.0.1 and 18c

Monday morning, another way-too-hot July day. Summer is crazy this year in Europe. We all enjoy nice sunny weather but nobody does enjoy a serious drought. Nowhere. While going through my inbox I spot this statement: ““Why should we go to 18.x with support till 2020?“. And this is not an unusual question. But I think I should write a Clarification: Support Periods for Oracle 12.2.0.1 and 18c. I receive plenty of such questions in the past weeks. And actually many from my colleagues. Clarification: Support Periods for Oracle 12.2.0.1 and 18c First of all, your Single Source of Truth…

Long Identifiers in Oracle 12.2 may cause trouble

LONG identifiers are one of the key features in Oracle Database 12.2.0.1. But as I learned the other day, you should be a bit careful when you exchange data between different databases. In certain situations, Long Identifiers in Oracle 12.2 may cause trouble. What are Long Identifiers? Long identifiers get introduced with Oracle Database 12.2.0.1. For ages, you could name a table or a column or a user or a package in Oracle with only 30 byte length. Hence, naming a table TAB_THIS_IS_MY_TABLE_AND_I_LIK is ok (30 byte – 30 characters) but naming it TAB_THIS_IS_MY_TABLE_AND_I_LIKE_IT is not possible as it requires…