Latest Contributions by VinceAngelo

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

What version of Oracle 9i are you using?  The minimum supported release went from 9.2.0.3 to 9.2.0.7 between 9.0sp2 and  9.2sp4. Given Oracle's retirement of 9i and imminent retirement of 10g, you probably want to start heading toward ArcGIS 9.3.1 and Oracle 11g soon. - V ... View more

You don't say which version of ArcSDE you're using, but SE_CLOB_TYPE and SE_NCLOB_TYPE columns would be the moral equivalents  of a MEMO field (STRING and NSTRING are limited to 4000 bytes, so they couldn't hold a full 64k memo).  CLOBs would be half the storage of NCLOBs if you have limited non-ASCII data in them , or they could be 2-3 times larger if you were storing all non-ASCII .  Then again, if you know the memos only contain 400 character strings, you can use the VARCHAR types. Given the Access source, ArcObjects is going to be your easiest tool for extracting the data and transferring to the business table, but you still have some work to engineer a solution to maintain the table after edit.  The ways to accomplish this  are legion, but the best method is dependent on the frequency of update, number of rows (total and changed), and whether you want this to be an automated process. - V ... View more

A pre-10 workflow for this could be to populate nominal UUID values ("{00000000-0000-0000-0000-000000000000}"), then run use "sdetable" to populate with "real" UUIDs. sdetable -o populate_uuid_column -t <table> -c <column> -u <DB_User_name>                         [-D <database>] [-p <DB_User_password>]                         [-i <service>] [-s <server_name>] [-q] My 9.3.1sp1 instance has the default value populated correctly, so you might not need to set any value. Alternatively, you can use the contrib/uuid-ossp module to populate values in the varchar(38) column. - V ... View more