Latest Contributions by VinceAngelo

ArcSDE isn't just "application software" -- it's also a database application extension package. If you don't configure and deploy the application server, it's *only* a database extension. - V ... View more

While it's true that you don't need a full install of ArcSDE to run ArcSDE commands, I would strongly encourage you to go through the install (and cancel the post-install), so that your release is populated in the system registry.  This will permit you to apply patches and service packs to keep your command-line tools in sync with your database.  Going "registry commando" is usually only an advanced technique since, while it lets you run multiple versions of ArcSDE, it also deprives you of Start Menu access to documentation and GUI tools for ArcSDE management. - V ... View more

I'm with Travis on this.  Even if you don't want to install "application software" on the database machine, you really ought to have a full install of the database extension package on the database server (if nothing else, you can be sure to patch the DLLs with a single installer, rather than having to keep track of what was been copied where).   The proper place for DLLs on Linux is in a "lib" directory.  You should use the ldd utility to confirm that the libst_geometry.so can resolve all dependencies (if your Oracle is 64-bt, your ArcSDE lib must also be 64-bit, or even though it's in the path, it won't be resolved). If you follow the Linux listener configuration instructions, you should get the listener enabled for ST_GEOMETRY, but that's only *most* of the battle -- You also need to configure the SQL*Net on the ArcGIS client (with the same or higher Oracle rev as  the server) so that ArcGIS can find the ST_GEOMETRY listener extproc. Even if your database does have ST_GEOMETRY (which doesn't apply to your situation), it's not strictly necessary for the ST_GEOMETRY listener to be set up correctly for ArcGIS to interact with the geometries. - V ... View more

That's an unusual error.  Did you change the structure of the table after it was registered with ArcSDE? You *REALLY* shouldn't create or edit any table as the SDE user.  SDE should be treated as a privileged account like SYSTEM or MDSYS, and only used for ArcSDE administration.  Best practice is to create one or more tablespaces to contain your data, and one or more data management users to own and manipulate the data.  You are infinitely more likely to damage your instance when you use the SDE user for non-administrative purposes. - V ... View more

It's perfectly valid for a compress to complete without reaching zero rows in the A & D tables. Keep in mind that ArcSDE versioning uses a tree model to represent potential changes to the base table -- compress will only reach zero if there are no branches. You need to examine the tree to see is any states are locked; once the "tree" is a "linked list" all deltas will be transferred to the base tables by the next compress. Looking from your Oracle client, identify the table, then look at its indexes; this is one way (of many) to determine the numeric suffix on the A&D tables. - V ... View more

It the table has compressed sucessfuly, there will be zero rows in both the A and D table, and the base table will contain all edits.  You can use any SQL tool to view these tables (including an ODBC connection through ArcGIS). The "s{char}{old_pattern}{char}{new_pattern}{char} " syntax is from 'vi' (which got it from 'ed', as did 'sed').  's' is substitute and 'g' is "global" -- You can interpret it as "substitute all occurances of old_pattern with new_pattern". - V ... View more

Doh!  s/reconcile & post/reconcile, post and compress/g The parts about table contents and MV views were right, though. - V ... View more

How are you doing these edits?  If you're using versioning, then the changes aren't really in the tables until after reconcile & post.  If you want the view to reflect other than the base table contents, you'd need to use multi-version views. - V ... View more

I only use "and" in my SQL code: sdetable -o create_view -T MySpatView ^ -t "myfeatclass,mytab1 a,mytab2 b" ^ -c myfeatclass.objectid,a.col1,b.col2,myfeatclass.shape ^ -w "myfeatclass.col1 = a.col1 and myfeatclass.col2 = b.col2" ^ -u myuserid -p ... [Caret ("^") is the Windows line continuation character; it's backslash ("\") in Unix] Once you start using ST_GEOMETRY you can use standard "JOIN" clauses via SQL, then register the result once the view is stable. - V ... View more

It has always worked. At 9.1, 9.2, 9.3.1, and 10.0. It's rare that I *don't* have more than two constraints, and it has never not worked. - V ... View more

There isn't anything I can do to help.  This syntax has always worked for me, so it likely has something to do with your configuration.  Make sure you have SP6 with the 3-4 post-SP6 patches and that your Oracle release is patched in conformance with the minimum supported configuration, and if it still doesn't work, contact Tech Support for assistance. - V ... View more

I do this all the time, but you have to keep a few key facts in mind: 1) If you have native geometry (GEOMETRY/SDO_GEOMETRY/ST_GEOGRAPHY), you should use SQL to construct your view, and register the resulting layer with 'sdelayer' (create_view is only for SDEBINARY/SDELOB layers). 2) If you intend to use the resulting layer in ArcGIS, you *MUST* include an OBJECTID column in your column list (it must map to SE_INT32_TYPE, be NOT NULL, and contain DISTINCT, positive, non-zero, and repeatable values). 3) 'sdetable -o create_view' will use table aliases (-t "mytab1 a, mytab2 b"), but you cannot alias the geometry column (it won't know what type to use) 4) Beware of polynomial expansion with one-to-many joins and multiple tables You didn't say what version and service pack of ArcSDE you're using, or even which Oracle release is under it, so it's hard to reproduce your issue. An "identifier too long" message is generated if a column name exceeds 30 characters -- this has nothing to do with Esri software (it's an Oracle limitation). -V ... View more

What does "MID()" do?  You need to use the equivalent Oracle SQL function. - V ... View more

If the table is effectively read-only, then the tolerance that is only managed by ArcSDE for the use of ArcGIS is of no consequence.  You can, of course, set the tolerance, either by using the -R parameter to reference an SRID which has one, or by providing a fourth parameter on the '-x' flag (you should *ALWAYS* specify an '-x' or '-R' when using 'sdelayer -o register').  [At least, I think that was supported as a fourth parameter on the '-x' flag way back at 9.2; it certainly is supported in recent releases.] - V ... View more

That link is to a discussion about SQL-Server.  There is a great deal of difference between single vs. multi-database administration in SQL-Server and user geodatabases in Oracle. Mostly the difference is between the way the RDBMSes are architected, allowing true independence between SQL-Server databases in a single server, and the false sense of independence fostered by user geodatabases in Oracle.  If I want independence with Oracle, I set up multiple SIDs.  This allows me to have different versions of ArcSDE in different instances, simplifies the backup/restore situation, and allows easier control of the resources allocated to the different databases. - V ... View more