Remember my blog post about time zone problems during import from one year ago? When you try to import into an Oracle database and your source database you exported from had a higher time zone (DST) patch level than the target, the impdp failed with ORA-39405 and stopped. In this blog post I showed several workarounds including some insane ones by Rodrigo and Kamil. And I’ve been contacted by customers and colleagues quite a few times asking for a general remedy.

Photo by Pascal Debrunner on Unsplash
There is a fix for it
Spoiler – you can request a backport …
Continue reading...








Again I’ll have to thank my colleague Roland GrΓ€ff from the German ACS Support team in Stuttgart for bringing this into our radar. Roland alerted me a week ago about an issue with exports in Oracle 12.1.0.2 only when you are on a certain patch level. I summarize the issue here under Data Pump 12.1.0.2 – Wrong Dump File Version – ORA-39142.
We recently worked with a customer who noticed that they were not able to use transportable tablespaces to connect the same tablespace data files to two databases at the same time, even after setting the tablespaces
Nice little best practice for statistics and Data Pump when doing either Transportable Tablespaces or Full Transportable Export-Import (credits to Roy and Dean Gagne).
Interesting question a customer had last week during the Upgrade Workshop in Munich. He’s getting export dump files from several customers and often not much information describing the contents. So how can ge find out what’s in there, which was the source characterset etc.