Where does the database link SYS_HUB come from?

This blog lives a lot from customer’s feedback and updates. And these days, Nicolas Jardot from dbi-services in Switzerland sent me an email asking: Where does the database link SYS_HUB come from? And if he can delete it or if it has any deeper purpose. Neither Google nor MOS reveal a lot of useful information Where does the database link SYS_HUB come from? I took my vanilla 18.3.0 database in our hands-on lab and check: column owner format a5 column db_link format a12 column username format a12 column host format a12 select con_id, owner, db_link, username, host from cdb_db_links; CON_ID…

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…

Databases need to be patched to a minimum before April 2019

CORRECTION: After I published this blog post saying “April 2019” my fellow support colleagues changed the alert to “June 2019”. Just saying … the topic itself is still the same. Simon Pane from Pythian talked to me at OUGN (Oracle User Group Norway) Conference about a recently released alert in MyOracle Support saying “Databases need to be patched to a minimum before June 2019“. He was curious if I know more details. I did some investigation but shortly afterward the MOS Note got updated as well. So here’s a quick summary of things you should be aware of – but…