Latest Contributions by VinceAngelo

The notes section on the doc states: The SELECT ANY TABLE privilege is required if using autoregistration with Oracle Spatial. If not using autoregistration, the SELECT ANY TABLE privilege is not needed. AUTOREG is disabled by default (and shouldn't really be used), so maybe the doc shouldn't list this seldom-needed right. When it comes down to it, there are four different sets of permissions involved with ArcSDE: 1) Privs required by SDE user to CREATE or UPGRADE ArcSDE within Oracle 2) Privs required by SDE to run Application Server service 3) Privs required by read/write data owner users 4) Privs required by read-only browse users You will not get a data owner (3) account to operate correctly by assigning SDE application service (2) privs. Granting CREATE/UPGRADE privs (1) to a data owner as a workaround is bound to cause difficulties. Roles are an excellent way to manage the "standard" permissions given to different classes of users, though I admit I don't bother with an SDEUPGRADE_ROLE, and just grant DBA, upgrade, revoke DBA, the re-grant the SDESERVICE_ROLE (because revoking DBA removes overlapping privs like CREATE SESSION). The SDE user should not ever be used to create spatial data.  Instead it (and its tablespace) should be reserved for ArcSDE instance administration. - V ... View more

Visual Studio 2005 isn't supported with the File Geodatabase API.  It doesn't seem likely that Microsoft could make a debug environment forward-compatible, which is likely your problem. - V ... View more

You had two billion features pass through without ever once truncating the table? Oracle will not allow you to reset a sequence.  Before we can suggest viable options, you need to describe that table -- Is it versioned?  Part of a topology?  What operations occur?  What are the min, max, and mean objectid values?  How many features in the table? - V ... View more

If your current 10gR2 instance is at least 10.2.0.3, it's likely that ArcSDE will function with it. Virtual hosting is okay for development (well, for small teams) and test (ditto), but it is not recommended for production use with databases, ArcSDE, or ArcGIS server. - V ... View more

SELECT ANY TABLE is not ever needed by unprivileged users, and is only needed by SDE under certain conditions. You cannot revoke access from users with SELECT ANY TABLE. The god-like privileges granted to SDE are only needed during upgrade; at all other times my SDE user usually only has CONNECT. - V ... View more

There is no difference in functionality between the gsrvr process execution on the server and the dedicated thread execution on the client (it's the same code, just a different initiation mechanism).  The only real difference is in where the SQL client resources are consumed (and the licensing thereof). - V ... View more

'sdelayer' will report access to the connected user, but nothing in the ArcSDE API tracks *other* users -- You'd need to traverse the RDBMS rulebase for this information (and need administrative access to do so). - V ... View more

I wasn't recommending that you modify my 'C' source (I haven't found a customer who wanted to pay to add that functionaility), but if you can read it, you might better understand what's happening, and thereafter code your own polygon population module (I don't recommend an Esri novice get anywhere near the ArcSDE 'C' API). You seem to have captured many of the issues surrounding variability in performance; there is no one solution that will address these divergent constraints.  It you haven't already done so, you should search on "spatial fragmentation", since that is something that you may be able to control.  You can also look at the size histogram generated by 'sdestats -o size -F 0,5000,20 -f -'. Note that any number of different spatial storage algorithms might be used, depending on how you have your instance configured, so "whatever the default is" might be different from instance to instance (or might change suddenly within one instance, if the DBTUNE environment was altered). - V ... View more

First off, you need to define "spatial index". There are several different possible spatial types, and each may have a different indexing algorithm. If you restrict yourself just to Esri spatial index types, then you just need a tool to create the one, two, or [hopefully not] three level indexing scheme. Once you work out the how second and third level index indicators are bit- masked into the gx and gy values, grid population is a trivial exercise using either the SDELOB/ SDEBINARY Sx table or ST_GEOMETRY's Oracle Sn_IDX$ IOT. While the documentation details the logic used to assemble the theoretical grid (the cell size is in ground units), no such grid is ever created (just the pointers to the x,y pair values). I did some research into generating a shapefile from my se_layergrid object in se_toolkit, but never needed to implement the 'visit' operator which would have been necessary to populate a data density map. Keep in mind that such a table could be quite large (a true 16-bit raster might be a better output product). In the end, I wasn't ever able to convince myself that the benefit of adding such a feature would be worth the effort (vice completing other tasks). As a rule, the 'si_stats' report (by 'sdelayer' or se_toolkit's 'sdestats') provides enough density information to get a feel for index suitability without plotting it. Yes, spatial fragmentation usually plays a much larger role in performance than the grid size (except when the grid size is *really* wrong). - V ... View more

A search on "remote install arcsde postgresql" turned up these instructions. - V ... View more

You cannot purchase a license for ArcSDE.  Since 9.2, the ArcSDE application server is a *part* of the Enterprise ArcGIS license.  However, you must run ArcSDE on the same host as ArcGIS Server.  If you want to run ArcSDE on a different host, you must purchase an ArcGIS Server license for that host as well.  You can speak with your local Esri rep if you aren't sure what you have or what it can do. - V ... View more

Rather than posting off-topic, please create a new thread and refer to the older thread as necessary. You cannot run an application server at a release which is not the same as the configured database. If the database must be 9.2spX, then the application server release must be 9.2spX. - V ... View more

You should really take unusual install errors to Tech Support.  If you want help in these User Forums, you need to provide all the information Tech Support is going to require, including the version of ArcSDE, the service pack that has been applied, the RDBMS version and service pack, and application word sizes for the OS, RDBMS, and ArcSDE. If the GUI has failed, it's usually helpful to try the command-line post-install utilities. The SDEHOME/etc log outputs from both GUI and command-line invocation will also be necessary.  Having pulled all this information together, it's quite possible that you'll be able to figure out what has gone wrong on your own. - V ... View more

ArcObjects is the only API that can provide read-only or read-write access to file geodatabases and personal geodatabases (Note: PGDBs are now deprecated -- 10.1 will not fully support them). Only ArcGIS 10.0 can upgrade pre-10 file geodatabases to 10.0 format (via GUI, ArcObjects, or ArcPy [Python]). The file geodatabase API does not support personal geodatabases of any release level. - V ... View more

The configuration is unsupported (all configurations involving ArcSDE 9.1 are now unsupported, but no testing has ever been done with 9.1 and SQL-Server 2008) -- Any number of problems may arise. - V ... View more