Strange Issue

[VinodN]

We faced a strange/unusual problem with our EBS and DB. Our EBS is 12.2.10 and DB is 19.9.0.0.0
We applied db and apps CPU patches (35642926:12.2.0, 35362524:R12.IGI.C, 35736189:R12.FWK.C, 36031426: COMBO OF OJVM RU COMPONENT 19.22.0.0.240116 + DB RU 19.22.0.0.240116 & 35943157)
We faced an issue while running datapatch and raise an SR with Oracle. It was found that Spatial had become invalid and so the engineer told us to uninstall and reinstall Spatial. We took export of some objects as part of this activity and later imported them. Spatial became valid again. But not all objects were imported by datapump import from the export dump and later on we found that one or more columns were missing in some tables - seed as well as custom! We raised an SR which lead to 5 spin-offs but the problem could not be fixed and we had to restore from backup at last... What could have happened? How could columns from a custom table (which was not even part of the action plan for Spatial and not in the export/import) go missing?

[ErmanArslansOracleBlog]

Your issue is so specific. I have not enough info for solving it. A remote access is needed there, or lots of analysis and outputs are required for this.
Why you used datapump import in this task? Who told you that and what did you do? -> "that might me the cause of the current problem". -- This is the way you use for reloading spatial -> How To Reload Oracle Spatial (SDO) (Doc ID 2796890.1)

When you have such INVALIDs in the registry, you need to first check why they are so.. The verification fuction can tell you this.. Only then if needed you take those kinds of actions.. only in the last resort.. Normally you fix the specifics, you don't do radical big actions..

[VinodN]

Why you used datapump import in this task? Who told you that and what did you do? -- Oracle Support engineer told us to do that. She said we needed to reinstall Spatial and as part of that we did the export and import.

[ErmanArslansOracleBlog]

I already made my comment on this.

[VinodN]

Yesterday I ran cleanup and fs_clone. Some columns from some tables went missing after that. Could it be that cleanup dropped those columns? But why would cleanup touch RUN edition?

[ErmanArslansOracleBlog]

If you added those columns yourself, by following a manual method, not aligned with the EBS and EBR, then this might happen.. This is my comment..(if you are sure about  -> Some columns from some tables went missing after adop cleanup)

[VinodN]

Oh. So it could happen to all such columns whenever we run patching cycle..

[ErmanArslansOracleBlog]

Maybe.. You should analyze it.. A deep investigation is needed there. You should check the difference of those columns , by taking the standard once as reference and if there is an abnormal situation, you should fix it and made them look like the proper ones.