Questions
1. Are these any obvious problems with the steps 1-5?
[Marcelo]: the sde user must be the first one to be imported, then fix any invalid objects, only then import the data owner users.
2. Have there been any issues with invalid objects (Procedures,…) in the SDE Schema between different Oracle versions and Geodatabase Versions?
[Marcelo]: No, differenct Oracle versions will not cause invalid objects, but after you import each user you must check for invalid objects and fix any problems, if you encounter any ORA-xxxx errors during import with "dpimp" then search support.esri.com for that error.
3. Is it “better” to create an empty oracle 19.16. instance, install new (not upgrade) Geodatabase 11.0 and import data using Arcpy script?
[Marcelo]: yes, you can also perform this, create a new empty geodatabase and use ArcCatalog / Pro / DataInterop / FME / Arcpy Script / etc. to copy the data from the old geodatabase to the new geodatabase, but you will lose any traditional versions or branch versions if your geodatabase schema is registered as versioned, hence you will need to reconcile and post all versions, delete the versions and then perform a sde compress (traditonal versioning) , on the other hand with data pump export / import the geodatabase versions and the state of the data is preserved.
| Marcelo Marques | Esri Principal Product Engineer | Cloud & Database Administrator | OCP - Oracle Database Certified Professional | "In 1992, I embarked on my journey with Esri Technology, and since 1997, I have been working with ArcSDE Geodatabases, right from its initial release. Over the past 32 years, my passion for GIS has only grown stronger." | “ I do not fear computers. I fear the lack of them." Isaac Isimov |