Maja,
I've been told multiple times by support that ArcMap/ArcCatalog handles Imports differently than Copy/Paste. So, if your shapes/geometry happen to have errors, the copy/paste will retain those errors while the import usually cleans it up. We've seen where we had errors in certain editing scenarios and when we moved to a FGDB to send to Esri Support via copy/paste, the editing errors still existed, when we did it via imports, the editing errors disappeared. This experience wasn't just a one off. So, when we move RH databases around, this is the procedure we follow.
Create Database
Import via Import Multiple Feature Classes/Tables tools
- LRS Networks (feature class)
- Events of interest (feature class)
- Minimum Schema
- Centerline (feature class)
- Calibration_Point (feature class)
- Redline (feature class)
- Centerline_Sequence (table)
- the 4 LRS_XXXX (table)
If you haven't included all the Event tables just delete those through the normal ArcCatalog tools....ALRS>LRS>Event Tables.
If you are moving RH from an Enterprise database to another Enterprise database, you will need to get the right tables versioned via the link Amit supplied.
I tried to dig up who from Esri sent me this but I couldn't find it.
brian
brian