Latest Contributions by VinceAngelo

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

A search on that message in the old forums would have produced the same information, but something has gone wrong with the new search software, and they haven't yet been able to build a clean search index (not for lack of trying, I hasten to add). - V ... View more

Have you tried specifying coordinate reference parameters (-x/-G/-P or -R)? I haven't worked much with GEOMETRY on SQL-Server 2008, but the Oracle metadata includes envelope, projection, and resolution data which allows for a better guess on coordref, before then passing the existing geometries through validation. Your invalid entiity type could be due to coordinate snapping to a single vertex (or a two-point line), or the table could just have non-polygon features which don't meet the "nil or polygon" entity flag mask. - V ... View more

populate_uuid_column doesn't repopulate the entire table, just the rows with the all-zeros placeholder, though it's more appropriate for batch operation than for onesies and twosies. - V ... View more

The application not licensed for data creation is ArcGIS Desktop.  ArcView can only read enterprise geodatabases; you need ArcEditor or ArcInfo for write access.  Use the Desktop Administrator to make this change. - V ... View more