Latest Contributions by VinceAngelo

There's nothing wrong with accessing an ArcSDE server across a VPN link -- I do it all the time with 'C' API apps. If the Windows client version is at least as high as the server (10.0/10.0sp1), then it should just work (the apparent CR-LF in the coordsys string may be the issue). If it doesn't, please file a bug report so the problem can be fixed. - V ... View more

If you're really using Oracle 10.2.0.1, then that's the problem.  ArcSDE 9.3.1 requires at least 10.2.0.3, and functions best with the terminal CPU applied. 10.2.0.1 had a number of quirks that made it very difficult to use reliably. - V ... View more

The list of packages is slightly different for every OS install (available versions change) but ArcSDE requires, in addition to the Oracle requirements: libstdc++, f2c, and openmotif, which are dependent on libXp, libXm, libX11, g2c and several compatibility packages for older compilers and X11.  If you execute 'ldd $SDEHOME/bin/sdesetup' it will tell you which libraries are missing. Running rpm on the packages that provide those libraries will report their dependencies. A previous forums posting gives the exact package names for an earlier RedHat. - V ... View more

If it does return, make a snapshot of the database; I'm sure Tech Support would want a crack at making sure it wouldn't happen a third time. - V ... View more

CLOB support was relatively immature at 9.2, especially before the first few service packs. You probably want to try using a modern client (ideally, 9.3.1sp2) with the older server, just to see if the Java API works with CLOBs at all (if not try again with a 9.3 instance). I load CLOBs in 9.3.1 servers all the time with the 'C' API, but don't have much reason to use Java. - V ... View more

States map to a 32-bit integer (2.14 billion maximum).  You'd run into other issues long before the number of states became an issue. - V ... View more

What version and service pack are using for ArcSDE Server, ArcGIS Desktop, and the ArcSDE API? A SE_CLOB_TYPE is just a larger-than-VARCHAR string type.  Does a subset of your string properly encode in a SE_STRING_TYPE column?  If not, then you'll need to work through character set issues first.  I only use AL32UTF8 character set, just in case I need to store non-ASCII7 data. - V ... View more

You cannot create a spatial view (use 'sdetable -o create_view') to generate a UNION ALL query, and you cannot UNION ALL layers with SDEBINARY storage, but you may be able to register such a view on GEOMETRY or GEOGRAPHY storage with 'sdelayer -o register' or simply access it with query layers, but only if the geometries share a single topology class and the id columns are unique across the joined tables. Generally speaking, if all the features share the same attributes, topology, and coordinate system, they belong in the same table.  Views can then used to efficiently extract logical subsets. - V ... View more

This may be possible, if you have the right combination of client, database, storage method, topology, and indexing parameters, but it's not likely to be very efficient. What is your environment like? How are your tables & layer defined? Are any of the tables versioned? What would your ideal view look like? - V ... View more

I can't recall ever having an 'init' fail due to an ArcIMS or AGS app running. Of course, I disable auto-locking when I create my layers (-L OFF) and don't regularly run IMS or AGS against my database development servers. It's probably wise to shut down services during wholesale replacement of database contents, just to prevent inconsistency. From that respect, both tables could be truncated and reloaded in less than the time it's taking to execute either DELETE. When I have regular updates that contain changes, and a desire to make those changes without a scheduled outage, I'm likely to use a change detection algortihm against the source, splitting the replacement job into a smaller set of insert, update, and delete operations. Then every once in a while I'll need to export the whole table out in optimized order, then reload to preserve system efficiency. - V ... View more

If your purpose is to delete all features, then why not use TRUNCATE, which will complete in seconds? C:\>asc2sde -o init -l trunc_ex,shape -C trunc_ex.ctl -# 70000 -vI 30000 ASCII to ArcSDE 9.3 Loader Utility       Thu Jan 13 09:37:56 2011 ------------------------------------------------------------------------   30000 source records read...   60000 source records read...   70000 source records read... Results:      Records read: 70000      Rows created: 70000       Insert time: 26.47 secs (2644.60 TPS)      Elapsed time: 34.42 secs C:\>sdesql ArcSDE 9.3 SQL Query Tool                Thu Jan 13 09:38:37 2011 ------------------------------------------------------------------------ 1> delete from trunc_ex where 1=1; Execution complete in 29.94 secs 1> quit       1 command completed in 00:00:48.4 C:\>asc2sde -o init -l trunc_ex,shape -C trunc_ex.ctl -# 70000 -vI 30000 ASCII to ArcSDE 9.3 Loader Utility       Thu Jan 13 09:39:31 2011 ------------------------------------------------------------------------   30000 source records read...   60000 source records read...   70000 source records read... Results:      Records read: 70000      Rows created: 70000       Insert time: 24.73 secs (2830.11 TPS)      Elapsed time: 31.86 secs C:\>sdesql ArcSDE 9.3 SQL Query Tool                Thu Jan 13 09:40:07 2011 ------------------------------------------------------------------------ 1> truncate table trunc_ex; Execution complete in 688.00 ms 1> exit       1 command completed in 00:00:24.8 The 'init' option of ArcSDE import utilities use SE_table_truncate to prepare the target table for repopulation; the 9.3.1 version even re-initializes the registered rowid column's sequence to start at 1. C:\>asc2sde -o create -l trunc_ex,shape -k ST_GEOMETRY -g 2 -C trunc_ex.ctl -v ASCII to ArcSDE 9.3 Loader Utility       Thu Jan 13 09:30:33 2011 ------------------------------------------------------------------------ Creating table 'trunc_ex'... Array-insert mode enabled... Loading data:     100 source records read... Changing layer to NORMAL I/O mode... Results:      Records read: 100      Rows created: 100       Insert time: 46.00 ms (2173.91 TPS)      Elapsed time: 672.00 ms C:\>sdesql ArcSDE 9.3 SQL Query Tool                Thu Jan 13 09:30:44 2011 ------------------------------------------------------------------------ 1> truncate table trunc_ex; Execution complete in 172.00 ms 1> quit       1 command completed in 00:00:16.4 C:\>asc2sde -o append -l trunc_ex,shape -C trunc_ex.ctl -v ASCII to ArcSDE 9.3 Loader Utility       Thu Jan 13 09:31:18 2011 ------------------------------------------------------------------------ Array-insert mode enabled... Loading data:     100 source records read... Results:      Records read: 100      Rows created: 100       Insert time: 454.00 ms (220.26 TPS)      Elapsed time: 735.00 ms C:\>sdesql ArcSDE 9.3 SQL Query Tool                Thu Jan 13 09:31:21 2011 ------------------------------------------------------------------------ 1> select min(objectid),max(objectid) from trunc_ex;       1     MIN(OBJECTID): 101.0000000000     MAX(OBJECTID): 200.0000000000       1 row found in 15.00 ms 1> truncate table trunc_ex; Execution complete in 94.00 ms 1> quit       2 command completed in 00:00:32.6 C:\>asc2sde -o init -l trunc_ex,shape -C trunc_ex.ctl -v ASCII to ArcSDE 9.3 Loader Utility       Thu Jan 13 09:33:15 2011 ------------------------------------------------------------------------ Truncating table 'trunc_ex'... Changing layer to LOAD_ONLY I/O mode... Array-insert mode enabled... Loading data:     100 source records read... Changing layer to NORMAL I/O mode... Results:      Records read: 100      Rows created: 100       Insert time: 63.00 ms (1587.30 TPS)      Elapsed time: 610.00 ms C:\>sdesql ArcSDE 9.3 SQL Query Tool                Thu Jan 13 09:33:22 2011 ------------------------------------------------------------------------ 1> select min(objectid),max(objectid) from trunc_ex;       1     MIN(OBJECTID): 1.0000000000     MAX(OBJECTID): 100.0000000000       1 row found in 0 secs I don't see any obvious references to table truncation in the gp tools, though. - V ... View more

Does the query "SELECT char_prop_value FROM sde.server_config WHERE prop_name = 'AUTH_KEY'" return any rows in the instance? (If so, please don't give it here.) If not, and either a custom setup GUI to authorize the database or manual 'sdesetup -o update_key -d ORACLE10G -l {path_to_saved.ecp} -u sde -p {password}' doesn't install the license, please contact Tech Support for assistance. - V ... View more

The part that is likely causing the issue is the first segment, which has a length [assuming meters] of 2.67 microns (smaller than the radius of a red blood cell [as per Wikipedia]). I was able to parse this WKT with an XY coordref of -200000,-200000,100000 (10 micron precision), because the first vertex rounds north to {-97505.19298,-105143.43197} while the second vertex rounds south to {-97505.19298, -105143.43196}. - V ... View more

Working through two tech support queues probably isn't the fastest way to access my time, but it may help with the SE_stream_set_invalidshape_mode issue. I won't post my e-mail address on the web, but the ArcScripts Contact Author page works. - V ... View more

This is the same issue as a recent thread in this forum. What it comes down to is the coordinate resolution used to describe the shapes -- When the table containing an existing geometry column is registered with ArcSDE, a precision is defined for the X/Y dimension (and Z and M dimensions, if appropriate). ArcSDE uses this precision to convert coordinate vales to internal representation. If the geometry cannot be represented, then an error is raised on the query stream, using the first transfer buffer available when the error was encountered (if the error occurred on feature 100, it's still possible that only 70 shapes could have been returned at the time the draw request failed). If you use the ArcGIS Desktop standard of ~1mm precision, then you'd need to lop seven places off the WKT strings (assuming the coordinate system unit is meters) to evaluate them for possible conflict within ArcSDE's internal SE_SHAPE representation (even still, other implementations aren't guaranteed to handle shapes identically). If the layer was defined without an explicit coordinate reference, it may have used the ArcSDE default coordref of "0,0,1" ({0,0} origin, 1 meter/foot/degree precision), which should generally be avoided (especially when working with geographic coordinate systems).  You can determine the precision registered with ArcSDE by using the command 'sdelayer -o describe_long -l {table},{geomcol} -u ...' (look for "Offset" and "System Units"). If you want to preserve the (assumed) 10 nanometer precision in the WKT strings, then the layer registration command would need to be altered to match that precision (using the third parameter of the '-x' switch), with a scale value of 100000000 (multiplicitive inverse of 0.000000001) -- though this may impact the range of coordinates accepted within geometries (you only have 53 bits of precision available). Please see the Understanding Coordinate Management in the Geodatabase white paper for more information on how coordinate systems are constructed and managed within ArcSDE. - V ... View more