Latest Contributions by AsrujitSengupta

Geoff, What you are experiencing, is the expected behaviour of the software. This is something by design. Locks are of various kinds....Shared Locks, Exclusive Locks... While editing or viewing data, a Shared Lock is established.... 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. An exclusive lock is used to lock a dataset in the geodatabase from use by others to make necessary changes to it; for example, to alter the dataset's schema. Once a user with proper permissions starts to make changes to a dataset in the geodatabase, ArcGIS will automatically establish an exclusive lock on the individual attribute table, feature class table, raster table, or other dataset. 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. Mentioned in detail in the below link: Schema locking: http://resources.arcgis.com/en/help/main/10.1/index.html#//003n0000002m000000 FAQ: How are the various lock mechanisms implemented in ArcSDE and the geodatabase? http://support.esri.com/en/knowledgebase/techarticles/detail/27034 Hope this helps! ... View more

If it is not an SDE Enterprise geodatabase, then even the Non_Versioned editing won't work. You'll have to run the Enable Enterprise Geodatabase tool, connected as the "SDE" user....then reload the Feature Classes... Enabling geodatabase functionality in a DB2 database: http://resources.arcgis.com/en/help/main/10.1/index.html#//0029000000sn000000 The geodatabase administrator in DB2: http://resources.arcgis.com/en/help/main/10.1/index.html#//002900000035000000 Regards, ... View more

Ahmed, Below are some basic steps that you can consider (it may differ sightly based on environment and your need): 1. Create a complete backup of the database on current machine using datapump 2. Create a new Oracle database on a new machine 3. Copy the dump created in step 1 to the new machine. 4. Create all necessary user tablespaces. 5. Grant these two permissions to PUBLIC by logging as 'sys' user in SQLPLUS: SQL> grant execute on dbms_lock to public; SQL> grant execute on dbms_pipe to public; 6. Import the Oracle dump file into the new Oracle database. 7. Check if there are any invalid objects for SDE schema, then re-compile those invalid objects by logging as 'sys' user in SQLPLUS: SQL> select object_name,object_type from dba_objects where status='INVALID' and owner='SDE'; If you find any 'INVALID' objects, recompile then using following command; SQL> exec dbms_utility.compile_schema(schema=>'SDE'); 8. Install the correct (if required) version of ArcSDE on new machine. Hope this helps 🙂 ! ... View more

Leo, Yes, I believe the "prvc" file could be used to authorize till 10.0. The Post Installation wizard when pointed to the prvc file, would take the ECP number. But 10.1 onwards we need to provide the keycodes or the ECP file to authorize a geodatabase. Regards, ... View more

Georg, Scripting geodatabase creation in Oracle: http://resources.arcgis.com/en/help/main/10.2/index.html#//002n000000t8000000 Regards, ... View more