We use ArcGIS 10.3.1 with Oracle11g on Linux.
We can open a clean ArcMap, open an application connect to the database, drag any layer and save the MXD.
The layer is visible and looks fine.
When we close ArcMap and try to reopen the MXD (by double click or open project from ArcMap) ArcMap just crash.
The same process works when we use direct connect.
The first process worked fine until 3 days ago but the Linux and Oracle people say they change nothing (surprise…).
We know we should use direct connect but we have many old MXD's that uses application connect that we cannot even fix them.
The only thing is the logs are status 8 (Lost Client).
We know we need to start SDE with debug mode and check oracle errors but this is production server so it will take some time.
Anybody has any idea what can cause such a problem?
If migrating to Direct Connections is an option, you can create new Direct Connections to the Enterprise GDBs and then resource the MXDs to those new connections (without having to open the existing MXD). This should get you going for the time being.
I am not completely sure, but I remember an issue like this which was logged as a Defect (may have been fixed by now), however I cannot find that right now. Maybe someone else may point to that.
Thanks for you input.
We tried to fix using ArcCatalog - it crash ArcCatalog.
The MXD was created in 10.3.1 and the geodatabase is 10.1
We tried to open the MXD in 10.4 with the same results.
Any other ideas?
Do you have any plans on upgrading your geodatabase since it is 2 major releases behind your desktop software?
Does the same crashing phenomenon occur on different computers?
Does the same crashing phenomenon occur for a different user on the same machine?
It append for all computers and users.
We are now trying to find a non production database that will show the same problem, then we can run some tests, debug, oracle trace etc.
It is not simple to do any testing on production.
Upgrade the database is planed but not soon...