Latest Contributions by rajeshc

‎03-12-2020

Thanks for the reply. Our plan is to import an existing on-premise enterprise geodatabase to AWS RDS. I guess this approach may not require AWS deployment tools. Please clarify whether there are any challenges with this approach.

‎03-12-2020

Is it possible to use ST_Geometry spatial type with Oracle RDS on AWS? On-Premise way is to copy the st_geometry dll file on to the database machine. Can we achieve it on AWS RDS for oracle? Thanks

‎08-28-2019

I was looking for a solution for exactly the same requirement as described in this thread. Though it is an old thread, it may help someone. The solution is given below. Public Sub AddCADLayer2GroupLayer(pGrpLayer As IGroupLayer, cadFolderPath As String, cadfilename As String) Dim pFeatureLayer As ESRI.ArcGIS.Carto.IFeatureLayer = Nothing Dim factory As IWorkspaceFactory = New CadWorkspaceFactory Dim pFeatureWorkspace As IFeatureWorkspace = CType(factory.OpenFromFile(cadFolderPath, 0), IFeatureWorkspace) Dim pFeatureDataset As IFeatureDataset = CType(pFeatureWorkspace.OpenFeatureDataset(cadfilename), IFeatureDataset) Dim pFeatureClassContainer As IFeatureClassContainer = CType(pFeatureDataset, IFeatureClassContainer) For i As Integer = 0 To pFeatureClassContainer.ClassCount - 1 Dim pFeatureClass As IFeatureClass = pFeatureClassContainer.Class(i) If pFeatureClass.FeatureType = esriFeatureType.esriFTAnnotation Or pFeatureClass.FeatureType = esriFeatureType.esriFTCoverageAnnotation Then pFeatureLayer = New CadAnnotationLayerClass pFeatureLayer.Name = pFeatureClass.AliasName pFeatureLayer.FeatureClass = pFeatureClass Else pFeatureLayer = New CadFeatureLayer pFeatureLayer.Name = pFeatureClass.AliasName pFeatureLayer.FeatureClass = pFeatureClass Dim iglayer As ESRI.ArcGIS.Carto.IGeoFeatureLayer = CType(pFeatureLayer, ESRI.ArcGIS.Carto.IGeoFeatureLayer) 'Here the Renderer is set Dim pUID As New UID ' create a new UID objects 'progID is "esriCartoUI.CadUniqueValuePropertyPage" pUID.Value = "esriCartoUI.CadUniqueValuePropertyPage" iglayer.RendererPropertyPageClassID = pUID End If If pFeatureLayer IsNot Nothing Then pGrpLayer.Add(pFeatureLayer) End If Next End Sub

‎06-09-2019

Greetings, We are facing an issue on GDB (ESRI) replication for our Oracle Enterprise Geodatabase. Our GIS Production (Parent) geodatabase is 10.2.1 version and the Child GDB is at 10.6.1. The synchronization is performed from the 10.6.1 ArcGIS Desktop environment. The replicas were made as parent to child full model (including the geometric netwrok). One of the replica intermittently fails to synchronize. The failing replica is of the Electric distribution Network. Mostly after re-trying 4-5 attempts it gets through, but the error comes back some days after. The failure happens at the "Re-build geometric network" step of the synchronization process. The error messages that appear at the failure are given below. Error 1 Synchronize Replica failed Table not registered [BAHRAIN.GDB_TEMP_USER_IDS] The coordinate system description is invalid [BAHRAIN.HVUGElectricLineSegment] Error 2 Synchronize Replica failed Table not registered [BAHRAIN.GDB_TEMP_USER_IDS] Invalid Table/column in SDO_GEOM_METADATA table [BAHRAIN.HVUGElectricLineSegment] Error 3 Synchronize Replica failed Table not registered [BAHRAIN.GDB_TEMP_USER_IDS] Layer not found [BAHRAIN.LVUGElectricLineSegment] Please note that the 10.6.1 child geodatabase was upgraded from version 10.2.1. Thanks

‎03-03-2019

By deleting the promote.dat file from the Primary Server's db directory seems to solve the issue so far. Now is it safe to delete those unwanted dbxxxxx folders ? Thanks

‎02-25-2019

We have deleted the promote.dat file from the db directory on the primary server. I will update on the effect later. It is neither present on the secondary. Curious to know how the promotion will work if this file is not present.. Thanks

‎02-24-2019

Hi Jonathan, Our setup was a fresh installation and new site, there was no site import operation. The primary db directory contains a promote.dat file with zero bytes. I have added the portal log to the main post as an excel file. Thanks for the reply.

‎02-18-2019

Hi, We have a Highly available setup of Portal for ArcGIS 10.6.1 with one Primary and one Standby server each. The OS is Wiondows Server 2016. We are running into Disk space issues on the standby server due to numerous DB folders being created automatically under the portal installation path C:\arcgisportal. Sometimes every 2-3 minutes, a new db folder is created. This issue is appearing only on the standby server. Is this behavior normal for the product? Thanks, Rajesh C

‎06-26-2013

You probably already know it, but this White Paper might be of some help: Compressing ArcSDE Geodatabases That Contain Replicas -Best Practices As per the document referenced above, it almost sounds like your replication setup is Two-Way, instead of One-Way. The document describes as situation where this may result in no changes being compressed on the Child, unless the Child is synchronized with the Parent with changes being sent from Child to Parent (even if no changes were made), see page 11. Thanks for your reply. Our replication is one way parent to child. Please see the replica property screens. Moreover, the synchronize dialog shows only one option for the direction, i.e from parent to child, confirming that ours is one way parent to child replica thanks [ATTACH=CONFIG]25519[/ATTACH][ATTACH=CONFIG]25520[/ATTACH]

‎06-25-2013

Hi, Here is the situation: Environment: ArcGIS 10.1 SP1 on Win 2008 server R2, Oracle 11 G on HP Unix, SDE Geodtabase We have a production SDE geodatabase and another geodatabase used for ArcGIS Server web application. The secondary GDB is updated on a daily basis using geodatabase replica synchronization. The secondary geodatabse was created using an oracle dump re-store from the production geodatabase, and the replica were created using "register existing data" option in the Create replica wizard. The replica is a one way child replica, both the parent and child are pointing to the SDE.DEFAULT version. On the child geodatabase we do not have any other versions (other than the Synch_send** versions). The synchronization is run using a scheduled python script arcpy.SynchronizeChanges_management (***_ewagisprod_sde, "***.WebU2_WaterReplica", ***_ewagisweb_sde, "FROM_GEODATABASE1_TO_2", "IN_FAVOR_OF_GDB1", "BY_OBJECT", "TRUE") Note: The replica datasets are having geometric networks. Problem The synchronization is working perfect and all the data is being pushed to the secondary database on a daily basis. On the parent geodatabase we have a maintenance schedule wherein we delete all versions and compress the database and then we run the synchronization process and again compress the parent geodatabase. The SDE.Default version is brought to state 0, implying a full compress. On the child geodatabase there are no other versions other than SDE.Default as i mentioned earlier. We have a compress schedule on the child geodatabase that is running after the synchronization is finished. The problem we are facing is that the SDE.Default version on the child geodatabase is never brought to zero and the delta tables are growing everyday. This implies the compress process has not done any benefit to the child geodatabase. Eventually the performance on the child geodatabase is getting slower due to the huge number of records in the delta tables. Can anyone tell us where we are going wrong? Is it a right strategy to create replicas on the SDE.default versions? Thanks in advance, Rajesh Sr. GIS Specialist

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by rajeshc

Re: ST_Geometry with Oracle RDS on AWS

ST_Geometry with Oracle RDS on AWS

Re: Add .dwg file to Map using Code

Geodatabase synchronize error

Re: Highly available Portal - Standby Server DB issues

Re: Highly available Portal - Standby Server DB issues

Re: Highly available Portal - Standby Server DB issues

Highly available Portal - Standby Server DB issues

Re: Replication and Geodatabase Compress - strange behavior

Replication and Geodatabase Compress - strange behavior