Tag Info

New 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 ...


0

Have you tried the "synchronize metadata" tool from the Conversion Toolbox (Metadata Toolset)? It will populate the fields you mention (extent & spatial reference, and more! : attribute list, geometry type, number of objects, ... or number of bands, cell-size & depth for raster, to mention only a few) by reading the data structure, encoding, spatial ...


0

This can happen if you forget to raise your license level to Standard (arceditor) or Advanced (arcinfo). Also see Opening ArcGIS Desktop on specific license level?


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 ...


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 ...


0

When you edit data in SDE with versioning it doesn't get written directly to the table (feature class), edits are stored in delta tables (adds/deletes) until the database is compressed. Esri understands these delta tables and applies them transparently however the base table is not modified so direct connections will not see the edits... If you are using ...


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 ...


0

You can access the version manager via ArcMap or ArcCatalogue and note the versions available or create your own from those available. You can then access it with this code in your script version = 'SDE.version_name' for example 'SDE.DEFAULT'. I am new to python scripting in ArcGIS but i guess you can be able to access the features in the ArcSDE ...


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.


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 ...


0

Thank you @vince and @Ben S Nadler for the heads up! I added those fields manually and then created the relationship classes.


0

Postgres works fairly well as an ArcSDE GDB, but as the number of datasets increases, so does the connection time. This is not an issue with other enterprise databases. For example, we have an Oracle SDE instance with 5000 datasets which takes about 5s to connect. We also have a postgres SDE instance containing the same data and it takes about a minute. ...


0

I recently upgraded a client environment from 9.3.1 to 10.3. They had major issues with upgrading their geocoders - basically the changes were so vast that they had to completely rebuild the geocoder. Turns out with most releases, the geocoder fields change, so you just have to go through the docs and remap the fields yourself. In my client's case, the ...



Top 50 recent answers are included