Moving from Pro 2.9.5 to 3.3.5 — Any significant issues to watch out for? (Enterprise 10.7.1 to 11.3.x)

[Bud]

My I.T. department is upgrading us from ArcGIS Pro 2.9.5 to 3.3.5 (Oracle 18c 10.7.1 EGDB to Oracle 19c 11.3 EGDB).

Users like me primarily use Pro for:

1. Tabular data analysis in attribute table, joins, query layers
2. Oracle EGDB feature editing and standalone table editing
3. Schema/table design changes
4. Linear referencing (no Roads & Highways)
5. Simple spatial analysis like Select By Location
6. Map exploration and producing PDF maps — lots of layers

Are there any high-priority issues or gotchas that we should look out for?

For example, in Pro 2.6.8, there was an issue where saving edits actually discarded the edits. And in Pro 2.9.12, linear referencing layers were profoundly slow; too slow too use. What about Pro 3.3.5?

[MichaelVolz]

Do you bring data in from nonSDE databases as query layers?  If so, just be careful using this type of data loading in python scripts where date fields could be upgraded to high precision date/time without the ability to disable this.  This could lead to schema mismatches that you would need to handle.