Following is the scenario
1. Create Feature class using Default keyword (Storage ST_Geometry) and register as versioned - Featureclass Multiversion view not getting created.
2. Create Feature class using SDELOB keyword and register as versioned - Featureclass Multiversion view getting created.
DB - Oracle 12c
ArcGIS SDE Version 10.6.1
ArcGIS Desktop Client 10.6.1
Any thoughts why this might be happening?
Hi Iris Green. I tested the behavior and couldn't reproduce it. The versioned view created successfully using an ArcGIS Desktop 10.6.1 client against the 10.6.1 enterprise geodatabase.
Did you encounter the behavior using a newer ArcGIS Desktop client against the 10.6.1 enterprise geodatabase?
Thanks for the reply ,
ArcCatalog 10.6.1 - Details of Version : 10.6.9270
Oracle 184.108.40.206 Using Desktop Client 10.6.1 only -its ArcFM enabled .
In Addition to above -
1. Able to create multiversion view with Default Keyword - using SDE user , but not with schema owner- which has all "Oracle privileges for creating a user-schema geodatabase"
Privileges for geodatabases in Oracle—Help | Documentation .
2. Also Enable SQL Access on newly created Featureclass or old Featureclasses gives error : "Creating a View on Userschema.Featureclassname failed. UnderLying DBMS Error : ORA-00942 - table or view does not exist".
Thanks and Regards
I performed a test using a feature class in a user-schema geodatabase and the behavior wasn’t reproducible. Can you perform a test using a sample feature class that is not an ArcFM object? Is the behavior reproducible on both “production” and “test” instance? Please create a case with Esri Support to review what may be contributing to this behavior.
The following article was recently authored. However, it doesn’t seem to be applicable to your case as you are using an ArcGIS Desktop version matching the enterprise geodatabase version.
EXTPROC.ORA was not configured to communicate with ST_Geometry libraries due to which EVW was not getting created for user schema. Thanks for replies nana!!!
Hi, the same issue happens when you work with a newer Oracle client and the geodatabase is not upgraded to support this. You can use a 10.6.1 client with a 10.6.1 geodatabase and still experience this issue. Just upgrade ArcGIS Desktop with the "ArcGIS (Desktop, Engine, Server) 10.6.1 Support for Oracle 18c Patch" and "ArcGIS (Desktop, Engine, Server) Support for Oracle 19c Patch" and upgrade the geodatabase so it is patched as well.
Have you guys fixed the problem? We have two customer facing the same issue. My behavior is exactly the same as @IrisGreen described.