Latest Contributions by ApurvDanke

Hi All, I just wanted to start a discussion about data model changes. We have many instances where we need to do some or all of the following - 1. Field addition/deletion/renaming or any other field change. 2. Domain creation/modification. 3. New Feature class/Table creation. 4. New relationship class creation. 5. Enable Z-Aware or M-Aware on existing Feature Classes. 6. Unregister replica and create new replica. 7. Add/modify subtype to existing Feature Class. 8. Assign or modify privileges on feature datasets. In our case we have a database where we have datasets registered as versioned, with archiving and editor tracking enabled. We usually follow the process mentioned below to do any kind of data model change. 1. Disable editor tracking. 2. Disable archiving. 3. Unregister as versioned. 4. Do the data model changes. 5. Register as versioned. 6. Enable archiving. 7. Enable editor tracking. My query is which of the data model changes require us to disable all 3 options i.e. editor tracking, archiving and versioning and which do not? If some data model changes do not require all the options to be disabled then what is the best practice which should be followed in each instance? Regards, Apurv ... View more

Hi All, I am trying to write a stored procedure in Oracle to fetch data from a particular version, by using the sde.version_util.set_current_version function. When I run the following statement individually in SQL Developer, it works fine. EXEC sde.version_util.set_current_version('My Version Name'); It shows a message in SQL Developer as -> anonymous block completed After this I can query this version to get the data that I want. However when I try to use the same statement in a stored procedure it gives following error -> Error(12,8): PLS-00103: Encountered the symbol "SDE" when expecting one of the following: := . ( @ % ; The symbol ":=" was substituted for "SDE" to continue. If I use EXECUTE IMMEDIATE (as given below) instead of EXEC, then I get a different error. EXECUTE IMMEDIATE sde.version_util.set_current_version('My Version Name'); Error(12,21): PLS-00222: no function with name 'SET_CURRENT_VERSION' exists in this scope ArcGIS geodatabase is 10.4.1 and database which we're using is Oracle 12g. Can someone suggest how this function has to be used in a stored procedure? Once this statement gets executed, I want to select some data from versioned view in a cursor. Regards, Apurv ... View more

Hi, I am testing ArcGIS Data Reviewer 10.4.1 and I want to test the invalid geometry check against point and polygon features, which I also want to create newly in a geodatabase version. I am using Oracle 12g for the geodatabase. Also installed Data Reviewer 10.4.1 patch 6. I was able to reproduce an invalid polyline geometry which self intersects, i.e. the same feature cuts itself. However for point and polygon I'm not able create a geometry which is invalid to test against. ArcMap doesn't allow me to create any points or polygons which have invalid geometry. I think this check would be most useful for data which has been migrated from different sources, but still to test it I need to create some data in the geodatabase which is invalid.  I thought of modifying the X and Y coordinates in the SDO_Geometry field (SHAPE) for that particular feature in the A table (as I created the feature in a version); or even make the value for this field as null. However I think doing something like this from backend in SQL might corrupt the feature class. Is there any safe way to create test data for invalid geometry check for points and polygons? Regards, Apurv ... View more

Hi, Since last week or so we have started facing this issue. We're using WFM 10.4.1 and we connect to WFM using OS authentication. The database is Oracle 12c. We have provided all privileges (select, insert, update, delete) on WFM tables and Feature classes to the users who use OS authentication to connect. We have some applications which use the following code to create jobs and versions. Now earlier, the version was getting attached to the job as part of Job Information. Now it simply shows "No version". What we did is that we had to modify a particular job type's workflow, and we wanted to only deploy that patricular JXL file of this workflow. But we cannot overwrite a workflow using its updated JXL file. The only way is to import the entire WFM configuration. We did not want that approach. So to test the new approach, we deleted the existing workflow in our development environment which was attached to a particular job type. Then we imported the updated workflow JXL and gave the same name to our workflow and applied it on the job type. Since then our code stopped working. The code is creating the versions in the geodatabase, but it is not updating the job information or JTX_JOBS table with the version name. With OS authentication, the version names should appear with double quotes such as "ABCUser".VersionName. But in the JTX_JOBS table it is just showing the default "JobID:ID". We have also tried following steps. 1. Importing the entire WFM configuration JXL file from another environment, where everything is working fine. 2. We also dropped the WFM schema, and recreated the schema, and workflow database and configurations. Still the issue persists. As we tried both these options, I think the problem cannot be in the database or the JXL import. It might be - 1. Problem with Workflow Manager installation. 2. Some other configuration, which got corrupt which we're not aware of. Below is the C# code. IJTXDatabaseManager databaseMan = null; IJTXDatabase2 JTXdatabase = null; IJTXActivityType pActType = null; IJTXConfigurationProperties pConfigProps = null; IJTXJobType pJobType = null; ; IJTXJobManager pJobManager = null; IJTXJob pNewJob = null; IVersion pNewVersion = null; string jobType = string.Empty; string jobName = string.Empty; string dateFormat = string.Empty; string notesInformation = string.Empty; string vesrsionName = string.Empty; try { //binding bool isBound = ESRI.ArcGIS.RuntimeManager.Bind(ESRI.ArcGIS.ProductCode.Desktop); if (isBound) { IAoInitialize aoInitialize = new AoInitializeClass(); //check for license aoInitialize.Initialize(esriLicenseProductCode.esriLicenseProductCodeStandard); aoInitialize.CheckOutExtension(esriLicenseExtensionCode.esriLicenseExtensionCodeWorkflowManager); databaseMan = new JTXDatabaseManagerClass(); JTXdatabase = (IJTXDatabase2)databaseMan.GetActiveDatabase(false); jobType = "<Our Job Type Name>"; dateFormat = "ddMMyyyy_HHmmss"; jobName = "<Our Job Name Prefix>" + DateTime.Now.ToString(dateFormat); pJobType = JTXdatabase.ConfigurationManager.GetJobType(jobType); Console.WriteLine(pJobType.ID); pJobManager = JTXdatabase.JobManager; pNewJob = pJobManager.CreateJob(pJobType, 0, true); pNewJob.Name = jobName; pActType = JTXdatabase.ConfigurationManager.GetActivityType(Constants.ACTTYPE_CREATE_JOB); if (pActType != null) { pNewJob.LogJobAction(pActType, null, ""); } pConfigProps = (IJTXConfigurationProperties)JTXdatabase.ConfigurationManager; if (pConfigProps.PropertyExists(Constants.JTX_PROPERTY_AUTO_STATUS_ASSIGN)) { string strAutoAssign = pConfigProps.GetProperty(Constants.JTX_PROPERTY_AUTO_STATUS_ASSIGN); if (strAutoAssign == "TRUE") { pNewJob.Status = JTXdatabase.ConfigurationManager.GetStatus("Created"); } } vesrsionName = pNewJob.Name; pNewJob.VersionName = pNewJob.Name; pNewVersion = pNewJob.CreateVersion(esriVersionAccess.esriVersionAccessPublic); Console.WriteLine(pNewJob.VersionName.ToString()); pNewJob.Store(); MessageBox.Show("Success"); } } catch (Exception ex) { MessageBox.Show(ex.Message); } finally { if (databaseMan != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(databaseMan); databaseMan = null; } if (JTXdatabase != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(JTXdatabase); JTXdatabase = null; } if (pActType != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(pActType); pActType = null; } if (pConfigProps != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(pConfigProps); pConfigProps = null; } if (pJobType != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(pJobType); pJobType = null; } if (pJobManager != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(pJobManager); pJobManager = null; } if (pNewJob != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(pNewJob); pNewJob = null; } } Any help is greatly appreciated. I can provide further details if necessary. Regards, Apurv ... View more