Export with Data Pump and Long Identifiers

I blogged a few days ago about Long Identifiers in Oracle Database 12.2 and accessing the objects via database links from lower database version. As this raised a few questions, I realized there may be a bit more clarification necessary. One question was about what happens during export with Data Pump and Long Identifiers. That’s a pretty good question. Export with Data Pump and Long Identifiers I’d like to demonstrate the effect with a short example. I’m doing all my tests in a fresh PDB inside an Oracle 18.1.0 CDB from out Hands-On Lab. But you can repeat it with…

What happens to PASSWORD_VERSIONS during an upgrade to Oracle 12.2?

I did blog a day ago about ORA-1017 connection issues in Oracle Database 12.2 once you would like to use the deprecated init.ora/spfile parameter SEC_CASE_SENSITIVE_LOGON=FALSE: Having some fun with SEC_CASE_SENSITIVE_LOGON and ORA-1017 But how can this change actually happen? Let’s check how the PASSWORD_VERSIONS is set in a fresh Oracle Database 12.1.0.2 database with the January 2017 Proactive Bundle Patch applied to it: SQL> select username, password_versions from dba_users order by 1; USERNAME PASSWORD_VERSIONS —————————— —————– ANONYMOUS APPQOSSYS 10G 11G 12C AUDSYS 10G 11G 12C DBSNMP 10G 11G 12C DIP 10G 11G 12C GSMADMIN_INTERNAL 10G 11G 12C GSMCATUSER 10G 11G…

How to get the Master Table from a Data Pump expdp?

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. This seems to be a simple question but it did cost me a few searches and tests to come back with some (hopefully) useful information. First attempt: $strings expdp.dmp > outexpdp.txt I bet there are better ways to do this but in my case this will give me: “APP”.”SYS_EXPORT_SCHEMA_01″ x86_64/Linux 2.4.xx WE8ISO8859P15 LBB EMB GHC JWD…