Latest Contributions by AsrujitSengupta

James, It seems I hurried a bit with my response. Whether you are hitting that NIM will depend upon certain other factors. Can you please confirm whether you are using a SQL Server sde gdb or an Oracle sde gdb? If you are using an Oracle sde gdb--is it a User schema geodatabase? ... View more

No, you don't need to have ArcGIS Server installed to create sde enterprise geodatabase. You just need to have a valid ArcSDE Enterprise license to create it. ... View more

Leo, How is the data getting copied to the other layer z? ... View more

James, Its a known issue and is being looked into by the concerned team at ESRI. If you would like to get more information regarding this, I would suggest contacting the ESRI Technical Support. [ NIM100932 - Upgrade geodatabase option grayed out for the user schema geodatabase of 10.2.1 while upgrading to geodatabase 10.2.2.] ... View more

Is the editor user able to edit on the DEFAULT version? Yes. As the user is able to edit in the DEFAULT version, can you try creating a new version from the DEFAULT and try editing in that. If that still doesn't help, as the issue seems to be limited to only this Feature Dataset, can you copy the same FD in the sde geodatabase again, regrant the privileges and check if the user is able to edit now. ... View more

Log file table configuration options for geodatabases in Oracle: http://resources.arcgis.com/en/help/main/10.2/index.html#//002n00000014000000 That error is usually observed when the user doesn't have necessary privileges to create the Log File. as suggested suggested in the above link, users receive an error message the first time they create a selection set larger than the threshold size for that particular client application. The threshold here would be 100 features. You may have tried to select more than 100 features, when you receive that error. We need to confirm which kind of Log File is being used at your end and accordingly grant the permissions. Usually when a user is created using the"Create Database User" tool, the following permissions are granted in Oracle so that users don't have to be granted these from the database end: CREATE SESSION, CREATE SEQUENCE, CREATE TRIGGER, CREATE VIEW, CREATE TABLE & SELECT ON DBA_ROLES. exception: Stand-alone log files, where you also need to grant the CREATE PROCEDURE permission explicitly from the database end Try granting the above permissions from the Oracle end and check if the issue still occurs. ... View more

Is any other user, other than the newly created "editor" user facing this issue? Is the issue reproduced if the user is created from the database end? Is the editor user able to edit on the DEFAULT version? The issue could be related to permissions itself. Connect as the data_owner and grant explicit editing privileges (Select, Insert, Update, Delete) to the 'editor' user for all individual Feature classes present in that Dataset and check if that helps. Ensure that the user has privileges on all tables within the relationship classes on the dataset level. ... View more

Check the Bit level of the Oracle database. Starting from 10.1 only 64-Bit oracle databases are supported....so you cannot upgrade a 32-Bit oracle database to 10.1/10.2 or later. SQL to check the Bit level of Oracle db: Connect in SQLPLUS using a sys user and execute the below query select length(addr)*4 || '-bits' word_length from v$process where ROWNUM =1; Oracle database requirements for ArcGIS 10.2.x: http://resources.arcgis.com/en/help/system-requirements/10.2/index.html#//01510000006s000000 ... View more

Emad, Even if you are Registering your data as Versioned with "Move Edits to Base" option...the delta tables do play a role when the editing is done on any other version, other than the DEFAULT. http://resources.arcgis.com/en/help/main/10.2/index.html#//003n000000rp000000 Under the heading "Registering as versioned with the option to move edits to base" its mentioned that: If you decide to register a feature dataset, stand-alone feature class, or table as versioned with the option to move edits to base, right-click it in the Catalog tree, point to Manage, then click Register As Versioned to open the Register As Versioned dialog box. Check Register the selected objects with the option to move edits to base. Checking this option causes edits that have been saved to the DEFAULT version, whether edited directly or merged from other versions, to be saved in the base (business) tables. Edits to other versions remain in the delta tables when you save. This is why the Versioned Views are created when you Register data as Versioned with move edits to base option. ... View more

In the "Create Database User" tool...uncheck the option 'Create Operating System Authenticated User(optional)'. It will create a Database Authenticated user and can be used to test the issue. ... View more

Ellen, This is a critical issue as of now and I would suggest discussing it directly with ESRI Tech_Support. Some workarounds have been found, which the Tech Support analyst will analyse, if its applicable for you and then suggest accordingly. As for the scheduled release of ArcGIS 10.3, I don't think anyone here is in a position to confirm that for you. Again Tech-Support would be a better way to confirm that. Regards, ... View more

Was any new data added to that Feature Dataset? A feature dataset itself is not versioned or unversioned -- the feature classes inside of the feature dataset are the ones that get versioned and unversioned. So if there is any new data added to a Feature Dataset or if there is any Feature Class within the dataset which is not versioned, then the Feature Dataset will also show up as not versioned. ... View more

I would suggest creating a full backup of your geodatabase and then running the "sdegdbrepair -o diagnose_tables" to look for any orphaned records. If any orphaned records are found, you can run "sdegdbrepair -o repair_tables" to correct those records. As suggested in the second post of this thread, run the sdegdbrepair utilities and let us know if that helps! ... View more

So as Vince mentioned, the error is occurring as you have granted the login "gdbo"  sysadmin privilege. Remove sysadmin role for that user and then try to migrate the storage. ... View more