Latest Contributions by VinceAngelo

It won't be so easy long-term, since 64-bit ArcGIS 10.1 will not support Access-based geodatabases. File geodatabases have taken the niche previously occupied by mdb files. - V ... View more

The EFLAGS bitmask values are undocumented, and change from release to release. If there was a list of constants it could be four billion values long. The information for which you appear to be looking is available elsewhere -- If a layer is ST_GEOMETRY it will be in the SDE.ST_GEOMETRY_COLUMNS table, and the SDE.GEOMETRY_COLUMNS table has a STORAGE_TYPE flag (though as a rule, it's safer to use rows instead of undocumented fields). - V ... View more

ArcSDE's SDEBINARY format is not the same as Microsoft's native GEOMETRY or GEOGRAPHY. Only when a layer is configured to use GEOMETRY/GEOGRAPHY would it be the same. The ArcSDE API can export SDEBINARY as well-known text or well-known binary, but that couldn't be done using SSMS. Your easiest solution is to start over with ArcSDE in a new database, using an owner other than 'sde' (as per best practice), with a default storage of GEOMETRY, and copy your old data into the new database. Then you can use Microsoft tools to migrate the Microsoft-formatted geometry objects. If you have more flexibilty in the way you export the data, you could write a simple 'C' or Java ArcSDE API app (or just use the 'sdequery' utility of se_toolkit) to create the needed data stream of ASCII or binary data. - V ... View more

I just bought a pair of 7200RPM 1Tb SATA drives for $104 (each).  Placing all your eggs in one network basket isn't very wise. And 600Gb still seems an order of magnitude too large for a vector dataset -- 150 DVDs? - V ... View more

You have half a terabyte in*vector* data?!  How big is the resulting file if you copy it to another directory? - V ... View more

Please do not place any part of your license key in Forums postings. The important part is the "101" -- That key is designed for 10.1, not 10.0. While valid, it won't unlock 10.0. - V ... View more

I don't believe the install docs are distributed as PDF.  But the HTML is on the install media, and if you enter "arcsde install linux" in the upper-right search window, PostgreSQL is the first link. Part of the reason what to do as each user is unclear is probably because, with the exception of editing /etc/services, it doesn't matter what user you do it as, so long as you do it with the appropriate user for any one of a few dozen possible configuration permutations.  SQL commands can only be issued as a database user; if it isn't clear which is an OS command and which is SQL, then you probably should be getting assistance from an experienced Unix admin and/or DBA. - V ... View more

You should prefix operators for ArcSDE ST types and functions with "SDE." since Oracle has reserved the synonyms for the SDO_GEOMETRY types. - V ... View more

You'd have to store that information somewhere to query it back out again. ArcSDE just tracks changes via a state tree and allows you to merge the records based on states (a "version" is just a named state). While there is some timing information in the states table, there is nothing to store who made which edit (just the open and close times).  You'd need to merge with with a database logging capability or some unsupported triggers on the SDE-owned tables to compile ownership information. - V ... View more

ArcSDE client applications need either a port number or a symbolic name for the port number. If you use the symbolic name (e.g., "esri_sde"), the application calls the getportybyname system function, which does a lookup in the services file (C:\WINDOWS\system32\drivers\etc\services or whereever your Windows release hides it).  I usually make up a master services file to distribute to all clients. Be careful that you don't try use the Catalog tools for managing Personal or Workgroup ArcSDE (SQL-Server Express) instances on an Enterprise ArcSDE instance. - V ... View more

Your error messages are inconsistent with where you state you have installed software. If your PATH doesn't point to these binaries first, they won't be used. Most Linux hosts have a nominal PostgreSQL installed by default -- I always remove this to prevent complications (if I didn't disable it during OS install). ArcSDE 10 is not compatible with PG 8.3.1, only PG 8.3.8 or 8.4.1 (8.3.8 is on the release media). I've been a professional DBA for 20+ years with six different RDBMSes on five different operating systems (if you lump all the Unix flavors and Windows flavors into one [each]). I can't recommend you follow all my tricks on your first install, but by the time you get to your tenth, you'll probably be intuiting many of them.  In the meantime, you should make sure you're working from the install guide for the correct software (ArcSDE 9 and 10 documentation might be different enough to trip you up). - V ... View more

The banner is reporting the environment in which it was compiled.  This is not a problem. Nor are a majority of the "errors" in the log, which are warnings only encountered on initial install. - V ... View more

You need to pay close attention to the application word size in both binaries and libraries. 32-bit applications will only work with 32-bit libraries; 64-bit applications will only work with 64-bit libraries. The error messages indicate you're trying to run a 32-bit application with 64-bit libraries. The 'file' utility can be used to determine the wordsize of both DLLs and applications (everything in the .../bin and .../lib of that directory tree should be the same wordsize). You really shouldn't ever run *any* installer as root (it's just about the only way you can significantly damage a Linux box). I generally install ArcSDE as the 'postgres' user, so there won't be any permission conflicts when it comes time to copy files to $PGHOME/lib.  I'm not a fan of installing PostgreSQL anywhere in /usr partition, but I'm not a fan of using RPMs either (I compile my apps from source, setting the --prefix to where I want it installed). - V ... View more

You probably want someone trained in legalese reading the documents and binding the company to abide by them. While you shouldn't take it as fact from me, in my reading of the license, the restrictions on the file geodatabase API are for *commercial redistribution* -- charging others for that which Esri has given to you without charge. You are certainly free to distribute the *run-time* DLLs with your binaries (royalty-free!), just not the include files and link libraries -- anyone who wants them must agree to the same license (this is a common characteristic of most "open" license agreements -- it levels the playing field and prevents Esri from becoming embroiled in squabbles involving third or fourth parties). It probably isn't wise to assume the license terms will change soon. If you wish to negotiate a different license (though it hardly seems necessary), you should probably take that up with your local Esri marketing office, not with the good folks here in the User Forums. If your company's legal staff has interpretation questions, then the local RO is still the best way to link them to Esri's contracts department. - V ... View more