Latest Contributions by VinceAngelo

The error indicates that the source shape is also NULL (or empty). Joshua asked about the shape contents, not the target fields.  You can add a "if (row[0] and row[1]):" above your row assignment to prevent the error, with an else to report trouble. - V ... View more

Please stop using ALL CAPS in your question titles. If you think it's a way to attract interest, I can assure you that it's in fact driving away potential viewers. - V ... View more

There shouldn't be much difference between running this as a 64-bit Python script (64-bit Background Geoprocessing) and running it within Pro. Given the size of the raster, and the fact that the ArcSDE API reads in tiles, not rows, constructing a cache for the tile height might have caused memory issues in 32-bit clients. Re-loading the raster with a W*2 x H/2 tile size might help for borderline cases, depending on the original tile Width & Height. Changing the tile size to be small enough to reside in-row might also result in significant performance improvement, as would using file-based storage (using rasters in databases was novel at ArcGIS 9.0, but is most of the way toward deprecated now). In the future, please include image and tile dimensions in the question, since storage doesn't provide an indication of width, height, depth, or compression algorithm. - V ... View more

Off-by-one errors cause all manner of system crashes. Differentiating between the maximum and overflow values is important, because if you test for the wrong one, you'll never reach it (overflow results in negation, so 2,147,483,647 + 1 = -2,147,483,648). I've done my best to make sure that none of the Esri documentation provides the incorrect value. I didn't remove this from the parent thread. When I do, I make note of it in both the source and target threads (even though it's much more difficult) I requested information about your exact procedure to see what could be done to address your problem. I can't tell if you should be alarmed without more information. - V ... View more

Two-way replication is a rather exotic solution which requires an exotic problem.  I'm confused by your solution, mostly because I don't understand the problem.  If you elaborate on the problem (a diagram wouldn't hurt), maybe folks here can pitch in with solutions. - V ... View more

I don't think this could work.  I'm certain that you don't want to do it this way. The problem is a lack of isolation between user-schema and SDE-schema Oracle geodatabases.  The documentation states that the source and target geodatabases must be different, and USER-schema isn't different enough to not cause nightmare-like difficulty.  Even using a two-way replica seems to be a misuse of the technology -- You'd incur a tremendous amount of overhead for little gain. - V ... View more

It's not possible to have WGS84 GCS with units of meters (geographic coordinate systems always have angular units).  Only a projected coordinate system (PCS) could have units of meters. If you don't know where you are, it will be difficult to get where you want to go. - V ... View more

You have the incorrect maximum -- It's 2^31-1 (2,147,483,647). I've processed billions of rows in various loaders (the largest at 650m rows), and have never seen the rowid grow to 20k after only 67 inserts. Please avoid thread hijack by asking a new question, providing comprehensive detail on the exact release of all software involved and the exact procedure you are using. - V ... View more

Best practice is to avoid ever registering a connection with the 'sde' USER.  The 'sde' user should only be used for instance administration, not for table creation, and certainly not for web-based table access. - V ... View more

Without the SQL it's hard to be positive, but I can't imagine how that wouldn't have the same issue as a row number. The value must be organic to the table/view, so that a query by ID returns the same row it did on a previous query.  This is why a row number doesn't work, since row 5 returned with a WHERE clause of "color = 'RED'" might return a row with "color = 'BLUE'" when queried by ID. ... View more

Please explain how you went about populating a unique number in a new column in my spatial view If you used a row number in the view, this could cause random results (and undefined behavior). - V ... View more

The FID column does not actually exist in shapefiles (and if you create one, it will be renamed so as not to conflict).  Therefore the basis for zero-based and one-based counting is entirely arbitrary, which is how ArcGIS chooses 0 and AutoCAD chooses 1. Best practice would be to avoid using record position for ANY operations.  Instead, create and populate a reliable unique identifier value, then use that. - V ... View more

Please always include errors as text.  This allows errors to be free-text searchable (and legible on all devices). This error seems to be a pure PostgreSQL issue, but it's probably worth talking to Tech Support about it. Failure to read a DLL installed in the instance might be due to anti-virus or some other application which is hosing your install. - V ... View more

The purpose of the rowid column is to tie the geometries in the map canvas to the attributes in the table view (and vice-versa). If the rowid result set values are non-unique, all manner of strange results will occur. In this context, you might be able to use a materialized view (called "indexed views" in SQL Server) to create a table with a unique ID (probably ought to preserve the source table IDs as well), or you can use relates and/or joins to teach ArcGIS the relationships between the tables (likely to be slower). - V ... View more

Please clarify how the one-to-many cardinality is being manifested -- Does the feature class honor the absolute requirement that the objectid be unique?  If it doesn't, you're in the realm of undefined behavior, where literally anything can happen (including the creation of a black hole to swallow your server). - V ... View more