Latest Contributions by RexRobichaux2

Hi Shane- Thanks for clarifying that certainly makes sense. Although you shouldn't have any issues creating new feature classes, the locking issue you are encountering when trying to add fields / make schema changes to existing feature classes would be expected (if) there are any shared locks existing at the time of the attempted change. More on this is explained here: Schema locking—ArcGIS Help | ArcGIS Desktop  "Any number of shared locks can be established on a single feature class or table at any given time. When you use ArcGIS to modify your geodatabase schema—for example, to add a field or alter rules—ArcGIS attempts to establish an exclusive lock on the data being altered. However, if a shared lock exists on that dataset, an exclusive lock cannot be established"  ..."If a user wants to make changes to a geodatabase schema, the specific datasets with which he or she is working must not be in use by others. In other words, to make changes to a dataset, a shared lock must not exist on that dataset"   What it sounds like is happening is ARCGIS is likely the ArcGIS Server / publisher user that is used for hosting published map or feature services from these feature classes. I'm guessing that there is some sort of nightly maintenance that probably restarts the services around midnight each night so that what creates the initially shared locks. If you stop all services from your ArcGIS Server admin connection do the locks drop off (they should if services are halted).   I'd recommend either stopping all published services (as well as ensure that no other users are connected in Desktop) and then check the locks / attempt a schema change. We just need to ensure there are no shared locks existing on the feature class before attempting to add a field. Disabling schema locking on the services should also work but perhaps there are multiple services referencing this feature class and some haven't been set to not allow schema locking? Hopefully this is helpful- schema changes can be tricky for highly utilized data- it's all about ensuring there are zero locks on the data (which can be challenging at times).  ... View more

Hi Shane, thanks for the additional information and screenshot. One thing I should have asked earlier- when you say you are attempting to edit feature classes- do you mean edit in the normal sense (editor toolbar, adding deleting or modifying features/attributes of features) or are you attempting to make schema changes to the feature classes themselves (add fields, edit fields, delete fields, for example)? So far I still don't see anything that would prohibit feature edits- but what you are encountering would be expected (inability to obtain an exclusive schema lock when there are shared schema locks active) if making schema changes to feature classes. Thanks! ... View more

Hello Michael,    What type DBMS is your geodatabase stored in? Also can you provide the version of geodatabase (Right click gdb admin connection < Properties)? Is this a sde or DBO (if SQL Server) owned geodatabase schema? Lastly- and just to verify- you are connected as the geodatabase administrative user when attempting to view current locks correct?  From my experience, this error can sometimes be indicative of orphaned records in the locks tables within the geodatabase. This typical workflow to diagnose and fix this issue would be to use (for a SQL Server DBMS): Take a full backup of the database (.bak for example), then disconnect all users using the ArcCatalog interface. Check the following tables and remove any remaining / orphaned entries through SQL from the geodatabase. SELECT * FROM sde.SDE_table_locks;  SELECT * FROM sde.SDE_layer_locks; SELECT * FROM sde.SDE_object_locks; SELECT * FROM sde.SDE_state_locks; SELECT * FROM sde.sde_process_information;  If you need assistance or would like further clarification I'd recommend contacting Esri Technical Support to assist with this workflow and confirm that this is what is causing the issue. I hope this is helpful! ... View more

Hello Shane,   A published hosted layer / map service shouldn't create any exclusive locks that would prohibit you from editing the underlying feature class. Therefore there is a chance the restrictive lock is coming from somewhere else. Would you be able to post a screenshot of the geodatabase admin / locks tab using the geodatabase administrative user so we can see all connections / locks?    Also what version and type DBMS is the data stored in? Thanks! ... View more

Hello Magaly,   As you are attempting to register the Oracle connection with Server as a registered data store you will also need to ensure that the machine where ArcGIS Server is installed has the ability to connect to the Oracle Database server / database as well. This will mean: Ensuring the 64 bit Oracle client is installed on the ArcGIS Server machine The 64 bit Oracle client appears first in the PATH variable on the AGS Server machine.  If Desktop is installed on the same machine where Server is running- attempt a connection from this machine through Catalog to see if connection is successful before trying to register.  Take a look at the various implementation setups and suggestions here: Register an Oracle database with ArcGIS Server—Documentation | ArcGIS Enterprise  Hope this helps! ... View more

Depending upon the way the domains / domain names were originally entered I have seen this behavior when a domain exists that has a carriage return present. This typically occurs when domain names are copied from sources like Microsoft Excel where carriage returns may be hidden and often times they are not immediately visible when viewing domain properties within ArcCatalog. There is a defect addressing this behavior for Oracle enterprise geodatabases (but it might well affect file geodatabases as well). If values have been copied / pasted opposed to manually entered for domain names- I'd consider this a high possibility: BUG-000091839: Updating or deleting a domain created with a carriage return returns the error, "Failed to update one of the domains. The domain was not found." ... View more

As Vince noted- "Communication Link Failure" notifications often indicate a break in communication between the client application and the underlying database (SQL) server which can be caused by a wide range of culprits.  See below for more information and troubleshooting tips.  Luckily, there are many tools available to begin troubleshooting these obscure issues. First, determine if whether or not a pattern exists or if this is truly intermittent behavior. A pattern would likely denote a relationship with scheduled tasks / jobs that are running at some level. Initial isolation questions should include: Is this only one machine that is affected or are other users on other machines also experiencing the issue when connecting to this database server? What version of ArcGIS desktop, what version / type DBMS, and what client (check for compatibility) What is the frequency of the connection drops? Does there appear to be a pattern? When did the connection drops begin, and what tasks in ArcGIS clients seem to cause or kick off the errors? Has there been consistent network connectivity? Wifi usage? Some troubleshooting steps can include (depending upon the context of the issue): Run infinite ping / continuous ping from a problematic ArcGIS client machine to the server machine. Monitor the ping results to watch for drops in correlation with what is experienced in ArcMap. This can be time-consuming (over days or weeks) but is important to detect patterns and prevalence of the issue. http://www.serverintellect.com/support/windowsserver/infinite-ping/ Check the database direct connect log file on the client machine located here: C:\Users\<username>\AppData\Local\Temp\sdedc_SQLServer (or sdedc_Oracle for example)- see if any additional information regarding the error has been captured in the logs. Examine the database machine's Windows task scheduler- ensure no jobs or scheduled tasks are being performed around the same time as the failures. Check the SQL Server logs in SQL Server management Studio under Management < SQL Server Logs - check around times of the errors. Verify there are no jobs running in the SQL Server Agent (not available in SQL Express) in Management Studio Check the SQL Server error log on the server machine which should be located in a location similar to the following by default:   C:\Program Files\Microsoft SQL Server\MSSQL##.MSSQLSERVER\MSSQL\Log ... View more

Hello Alberto- thank you for that confirmation. In response to this behavior which you highlighted- the following defect has been logged: BUG-000106595: ArcGIS Pro 2.0 and 10.5.1 Desktop require explicit object-level select privileges for users to view SQL Server geodatabase data in the Catalog tree.    Thanks again for bringing this behavior to light- please feel free to reach out to me if you have any questions or additional concerns! ... View more

Hi Alberto,  Thanks for bringing this behavior to light. After a quick test, it appears I can reproduce this behavior in 10.5.1 / SQL Server 2014 geodatabases. Below is the simple workflow I used to test this out- please let me know if you see any inconsistencies or differences from an equivalent workflow that you have used: Created a new test viewer database user named "tenfiveone" in a SQL Server 10.4.1 (and 10.5.1 geodatabase) Mapped this user to the 10.4.1 and 10.5.1 (testing for consistency) geodatabases in SQL Server Granted the tenfiveone user select privileges within each gdb Created a connection in ArcCatalog 10.3.1, and 10.5 for the tenfiveone user to each database- could see all feature classes visible once connected. Created a connection in ArcCatalog 10.5.1 for the tenfiveone user to each database- no feature classes were visible until select was granted explicitly by the data owner within ArcCatalog to the data.  Notes from further testing:  This doesn't appear to be reproducible in Oracle geodatabases as the privilege grants are object based by default.  As noted this behavior was reproducible in Pro 2.0 as well granting object based permissions on the DBMS side for example "grant select on [sde].[TESTFC] to tenfiveone;" opposed to "grant select to tenfiveone;" has the same effect as ArcCatalog dataset level grants, therefore, object based grants workaround the issue. Kind regards, Rex R ... View more

Hello Oleysa,  Can you check to see if there is any supplemental information contained within the replica logs located here by default: Location: C:\Users\<username>\AppData\Local\ESRI (File name ReplicaLog.dat)?   Also- you mention that you get this error whenever you try to create a replica regardless of which order the layers are in- is that correct (and the new first layer's table is referenced in the error)?  I might suggest reaching out to Esri Support Services if possible to look into this issue further with you.  Best, Rex R https://community.esri.com/groups/geodatabase‌ ... View more

It appears as though you have some invalid geometries within your Oracle enterprise feature classes. Ordinarily, this would be fixed by exporting to shapefile of fgdb feature class and then run the check or repair geometry GP tools. However- as this seems to be problematic (at least for shapefile)- I would try the following to identify the invalid polygon geometries: 1) Try exporting to file geodatabase feature class instead of shapefile.  2) If this still fails- perhaps try a copy / paste from the Oracle gdb to a file geodatabase in order to migrate the data or even export / import XML.  3) Hopefully, one of these methods will work, and you can then run the check and / or repair geometry tools. 4) If all else fails, you might have to analyze the data manually for issues- is this a large polygon feature class with many features? 5) Since self-intersections seem to be an issue- could you try creating a topology with a must not intersect rule- validate, and see if this detects an issue? Not sure if this would work or not as it's ideally meant to check relationships between features- but might be worth a try.  ArcGIS Desktop Help 9.2 - check geometry (data management)  Hopefully, this is helpful if you are still encountering these issues.  Best, Rex R ... View more

Hello Filippo,  Is this the workflow you followed to check and advance the sequence? Error: Underlying DBMS error (ORA-00001: Unique constraint (SDE.GDB_OC_PKC) violated)  Alternatively, can you try creating a dummy table in Oracle through SQL Plus with the same user / schema that you are attempting to use to create a new feature class in ArcMap / Catalog? Just something simple like: CREATE TABLE <your_feature_class_name>(id int); Then, refresh your connection in Catalog and see if this new table appears in the gdb table of contents. If it does, delete it through Catalog- then re-try creating the feature class in Catalog. I'm wondering if there was once a FC with this name and it has become orphaned in some of the gdb repository system tables. I hope this helps! Best, Rex R   ... View more

Hi Gideon,   It is possible to perform administrative tasks such as adding users, adjusting dataset level privileges, etc. using database connections. This can easily be done through Geoprocessing tools such as the Create Database User tool, Change Privileges tool, Create Role (if necessary), etc., and then referencing the proper level connection in the input of the tool. Alternatively, database users and permissions can also be managed through the DBMS (SQL Server Management Studio).    You will want to create various connections- one for your database administrative user (SA / sysadmin level user), a geodatabase (sde or dbo) administrator user connection, and then subsequent database connections for data owners/creators, editors, etc.   Once you have a connection made for the database admin user (sa / sysadmin) this connection can be referenced as inputs for these tools. You can also adjust dataset level privileges using data owner connections (adjust which users have select, insert, update, delete, etc.) permissions on feature classes and feature datasets by right clicking the objects and going to Manage < Privileges. Privileges for users in SQL Server geodatabases: Privileges for geodatabases in SQL Server—Help | ArcGIS Desktop  Create Database User: Create Database User—Help | ArcGIS Desktop  Change Privileges: Change Privileges—Help | ArcGIS Desktop  I hope this is helpful! Best, Rex R ... View more