Tag Info

Hot answers tagged

3

Esri has two mechanisms for making database connections embedded in the ArcSDE 'C' API. The first (original) protocol uses an application server (giomgr) process, usually running on the database server, to accept network connections and then bequeaths the connection to a child (gsrvr) process to manage database interaction on behalf of the client. While ...


2

arcpy.env.workspace = r'Database Connections\adminCon.sde' arcpy.MakeFeatureLayer_management(r'Database Connections\adminCon.sde\GISADMIN.Buildings', 'fl') arcpy.ChangeVersion_management('fl', "TRANSACTIONAL", "GISADMIN.Oli") arcpy.ChangeVersion_management('fl', "TRANSACTIONAL", "sde.DEFAULT") For further information check: How to get a search cursor on a ...


2

There's no telling what actually happens behind the scenes. Maybe this thing executes one separate statement for finding the characteristics of each column of each table and forgets to close the corresponding cursors, i.e it leaks cursors. One simple test is to increase the maximum number of cursors per session. Best is to ask your DBA do to that, since it ...


2

Your configuration is not the best candidate for an in-situ upgrade. Given the distance of four major ArcGIS releases (and more than a dozen minor releases), and three major Oracle releases, plus operating system compatibility issues, your most reliable migration path would be to: Use 9.2/9.3 Desktop to convert your 9.2 geodatabase tables to file ...


2

An easier option than creating python addin would be to create a python script tool that uses various arcpy.GetParameterAsText(0) statements that relate to the Create Database Connection arguments, and then using conditional logic (if, else), is directed to open one of two map documents sourced to either test or production (already saved somewhere on your ...


1

Non-Arcpy If you don't want to go for arcpy, one solution is to create two separate Mxds. Right Click your original mxd in ArcCatalog and then click "Set Data Source...". In this way you can instantly create a new mxd file which points to your new connection file (e.g. ProductionDatabaseConnectionFile.sde). It takes about 10 seconds. If your original ...


1

I believe what you're looking for can be for found in the SDE_XML_DOC# tables stored as ArcSDE XML (CLOB in Oracle in this case). Here's an example of the workflow for a feature class called "SDE.Test": SELECT NAME, DEFINITION, DOCUMENTATION FROM SDE.GDB_ITEMS WHERE NAME = 'SDE.Test'; NAME DEFINITION DOCUMENTATION SDE.Test 61 ...


1

In my situation, the problem was the order of deploying the changes. In a previous step, the dataset containing these feature classes was registered as versioned. Then the above 'arcpy.AddIndex_management' was called. If indexes are added before enabling versioning, all the feature classes are indexed without issue. And much more quickly as well.



Only top voted, non community-wiki answers of a minimum length are eligible