Latest Contributions by VinceAngelo

The only ArcSDE 9.1 that supported 10g was the "ArcSDE 9.1 for Oracle 10g" from the online downloads. In addition to ArcSDE 9.1 being retired, Oracle 10gR2 is *also* retired. - V ... View more

Exactly.  My friends over in Tech Support aren't happy when I lead folks by hand into Unsupported Territory (and you'll notice I'm not a willing guide), but if you can find the road yourself, then you're not likely to need to call Tech Support. The supported mechanism is to establish a test server, load software there, transition your install to 10, then post it back to the production server.  But some production servers are beefy enough to support a bit more, which is how we found ourselves in this mess. Keep in mind that nothing I've posted on this topic addresses the issues surrounding licensing.  You still need to adhere to your license agreement with regard to number of server-CPUs, and the supported mechanism of using a different server to run the 'sdesetup', and not installing a service for the new instance (using only Direct Connect), is far more likely to fit in the licensing model as-is (but you'd need to speak with your local Esri office to clarify any of that). - V ... View more

I'm not really sure what you mean by clarify. I regularly need to run the same versions as my clients, so I'll have 9.2, 9.3, and 10.0 releases on the same machine. As long as the services are created correctly with the 'sdeservice' command, there's no technical reason to prevent this from happening. - V ... View more

There's no problem running multiple ArcSDE instances on the same server (I always have between three and five instances on any host), but when using Oracle, you need to create one database instance per ArcSDE server. Actually, I take that back -- There is a problem: You can't install ArcSDE 9.3 and ArcSDE 10.0 on the same server. This has been covered in this forum repeatedly. - V ... View more

I regularly load five and seven million row GeoNames tables into a number of different RDBMS instances (Oracle 10g & 11g, SQL-Server 2008 & PostgreSQL). Each of these tables uses several GB on disk.  I've never seen the behavior you are describing.  Have you tried to use a direct loader like 'shp2sde' to load the shapefile? Have you tried appending the 1m source data until it fails? Have you tried loading a gigabyte of strings into your PG instance using SQL (without any geometry at all)? Did you use the PG838 that ships with ArcSDE 10? Please open a Tech Support incident, since they're going to be your best resource for determining what's going on.  Be sure to provide all the tuning parameters and complete information about your PostgreSQL instance, since this seems to be the most likely issue. - V ... View more

'sdetable' only supports tables, not feature classes or feature datasets.  It just so happens that feature classes are modeled as tables, so 'sdetable' can be used on feature class names, but feature datasets are not modeled as tables, so you can't refer to them at all with 'sdetable'. If you fail to grant the same permissions for all the tables comprising a feature dataset, ArcGIS will only acknowledge the minimum permission held in common (logical AND), even if that means no permission at all. All in all, you'd be better off using Python (if it has the requisite hooks at 9.3.1, which it likely does; I just don't use ArcGIS all that much). - V ... View more

In theory, there is no difference between using 'sdetable' and 'sdelayer'.  I use 'sdetable' because it is the proper context (permissions are a property of a table), and because I don't need to know the geometry column name, and because it's less typing.  It is possible that using 'sdelayer' could, by design, fail to set raster support table permissions if both SE_SHAPE and SE_RASTER columns existed in a table (I would hope it wouldn't, but I only use 'sdetable', so I wouldn't know).  'sdelayer -o grant' should have been deprecated at 8.1 and eliminated by 9.0, but doing so would have broken a lot of scripts. - V ... View more

None of the ArcSDE command-line utilities will access any of the geodatabase extensions like domains or feature datasets (implemented outside the ken of ArcSDE).  You can use Python to script geodatabase management via ArcGIS (more so at 10.0 than with earlier releases), or manage the indiviual dataset member tables via 'sdetable -o grant'. - V ... View more

The compress operation eliminates states with exactly one successor state (parents of 'only' children, if you will).  Successful completion just means that compress has done the best that it can with the state tree, not that all branches have been pruned. A state 0 compression cannot occur if any state has branches (two or more children). If there are no outstanding versions or locks, it's possible that your state tree is corrupted (though it's probably only a minor issue).  I'd recommend you contact Tech Support, since they have access to diagnostic utilities to assess the contents of your state tree. - V ... View more

Does 'sdetable -o describe -t {view_name}' return the view's description?  I know this works with Oracle, PostgreSQL, and DB2, even if the table isn't registered with ArcSDE.  The error message indicates that layer registration is attempting to add or alter the rowid column, which makes me think that the column isn't NOT NULL. You really ought to specify coordinate reference parameters (-R or -x/-G) and an envelope (-E) with the register operation, instead of allowing ArcSDE to choose values which may be incompatible with your data.  If the features are ever multi-part, you'll need '-e a+'. - V ... View more

What does 'sdetable -o describe' report for the table? What 'sdelayer -o register' command are you using (less password)? Are you specifying an existing NOT NULL unique integer rowid column with the '-C' flag? - V ... View more

You really ought to use the same client as the server (Oracle 9.2.0.8 32-bit client with ArcSDE for Oracle 9i 9.2sp6 to connect to a 9.2.0.8 server).  If you were using an early/buggy Oracle 9.2 client (not one patched to 9.2.0.8), that would explain the memory error. - V ... View more

When using native geometry, use SQL to create the view, then 'sdelayer -o register' to make it available through ArcSDE. - V ... View more

You really don't want a 1.3 billion point table anywhere -- Even with the best possible performance, you're looking at a 30+ hour load time (and hours to do any meaningful analysis). If your points don't vary in value all that much, you might be able to map 1Kx1K pixel chunks into a multi-point table (where all the points with the same value are merged into a single feature) -- this will still be moderately unusable as tens of thousands of features with tens of thousands of verticies. Your best bet is to apply some classification scheme and convert the result into a polygon table.  Still unwieldy due to the vertex count, but better than the other options. - V ... View more

There is no direct correspondence between the release number and service pack. Releases are usually incremented during development, so that sometimes "Final" will be as high as xy003 or xy004. I always name my install directories with the release version and service pack so I can keep things straight (I usually have two or three *dozen* SDEHOMEs in my ESRI directory, so using a naming convention is not optional). You can use the service pack finder on Windows hosts to determine the actual product version. I suggested that you drop the SDE user to simplify your problem. No install should ever receive a "memory fault", so not having to work with an upgrade can sometimes isolate the actual problem. At this point you'd probably be better off contacting Tech Support to walk you through the trouble-shooting process. - V ... View more