Latest Contributions by VinceAngelo

If it doesn't work on the command line, remove the final AND clause to let 'sdetable' succeed, and then apply that clause via ALTER VIEW from a SQL client (like SQLDeveloper) later. - V ... View more

Maybe it's an artifact of the posting environment, but as I read it, your WHERE clause isn't legal SQL -- did you mean "AND date = (...subselect...)"?.  Even if it is legal, you might be running into a utility parse buffer issue with the long WHERE constraint. It's not strictly supported, but you can generally add exotic options to the view after it's created (as long as it doesn't result in unsupported columns or polynomial expansion of the registered rowid column)-- but the SQL still has to pass muster with the database. - V ... View more

Nothing in the ArcSDE API measures data flow.  The closest would be using the SDEINTERCEPT environment, but then you'd need to parse a few megabytes of trace files. Your best tool for monitoring ArcSDE network traffic would probably be a network analyzer.  If you're using a Direct Connection, all the traffic is database-dependent, so you might look at a RDBMS tool. - V ... View more

There are several issues here.  The coordinate system stores projection information (PROJCS) if a projection is defined, otherwise it just stores the geographic coordinate system (GEOGCS).  It's confusing that the file is ".prj" when there might not be a projection, but that's the naming convention that has evolved since the original shapefile spec was written.  The larger problem is that the coordinate system is just a tiny part of the coordinate reference, but that is the only part which is stored with shapefiles.  Only ArcSDE requires coordinate references, so these properties are not carried in any transfer format beyond SDEEXPORT. With BASIC precision coordrefs, you couldn't define one spatial reference per coordinate system, since you only had 31 bits available.  With HIGH precision coordrefs, it is possible, but that possibility is also a trap -- needless storage precision (relative to the data precision) increases the storage and slows ArcSDE performance.  For this reason, you should not ignore the spatial reference parameters at data creation -- instead you should generate an appropriate value and use that for all objects (via SRID). If individual GP commands produce unique SRIDs as a matter of course, you should contact Tech Support to generate a defect, since the current commands should all generate the same (somewhat inefficient) SR for any one coordsys. The only exceptions are when you are using data outside the expected range for that coordsys, or when you introdce new dimensionality (M/Z), for which no real standards exist. - V ... View more

You'd probably see quicker timeouts if you remapped the unavailable hostname by updating the hosts file to an invalid network address like 127.0.0.2. 127.0.0.2     unavaliablehost - V ... View more

ArcSDE coordinate references are composed of the coordinate system, the X/Y origin and scalefactor, the Z origin and scalefactor, the M origin and scalefactor, and the precision. The "spatial domain" is implicit from a combination of X/Y origin, scalefactor, and precision, but incompatibility is measured from all eight components, which ArcGIS calls "spatial reference" (to maintain consistency with Spatial Reference ID [SRID], I assume). - V ... View more

That might be a memory leak in the database server.  Are you up-to-date with your Oracle Critical Patch Update (CPU) release? - V ... View more

What service pack do you have appied to both ArcSDE 9.2 and Oracle 9i? What geometry storage type are you using in the view's source table? Does the registered rowid column return unique row values for each query? - V ... View more

The ArcSDE build doesn't really have anything to do with the Oracle release -- you uneed to upgrade to at least 10.2.0.7, or ArcSDE will not function reliably. - V ... View more

At this point, I think you'd be better off taking this issue to Tech Support. - V ... View more

The "3" corrupted the layer definition, since your geometries are 2-D.  You should have the "-x" flag on the command line, in addition to -P and -G. - V ... View more

Try again with "-P HIGH"  -- your Y origin is too far away with BASIC precision. - V PS: You'll also need "-G  102100" for  PE_PCS_WGS_1984_WEB_MERCATOR_AUXSPHERE ... View more

Okay, I goofed -- my metadata file contained "np" eflags, which generated the error. The coordinate system (projection) doesn't matter, but the falsex/falsey/xyunits matter a great deal.  What values do they contain in SRID 54?  I used -10000000,0,10000 (with HIGH precision). Go ahead and leave your eflags at "na+", since that's not the issue. - V ... View more

What error are you receiving? Is the objectid column the SDE-set registered rowid for the table? How did you attempt to populate the new row(s)? - V ... View more

The ArcSDE 'C' API reports the same "Invalid shape type" error for that WKT. I haven't been able to parse that vertex stream without error. - V ... View more