Latest Contributions by VinceAngelo

The direction of quotes is vitally important in Unix -- Backquotes execute the contents, so "ldd `which sdesetup`" is equivalent to pasting the output of "which sdesetup" as the parameter(s) to the ldd command.  The output of 'which' indicates that you have not followed my example -- "~/bin/sdesetup" indicates that you have not provided a fully qualified path to the PATH and LD_LIBRARY_PATH variables, rendering them useless.  You should not ever make the SDEHOME directory the home directory of the software owner. The hosts I administer *average* 15 ArcSDE installs -- all owned by the same user, and the $HOME of that user is unlikely to be on the same filesystem as the $SDEHOME installations. - V ... View more

Please review the documentation on Esri database support policies.  In short, they say that Esri can only support versions which have been certified; later service packs are "assumed to work" (sort-of supported if they do work, and unsupported if they don't).  Most of the Esri software baseline has shifted to 64-bit at 10.1, so the majority of the testing (and therefore certification) has been done with 64-bit. "Direct Connect" does not mean "Query Layer" -- these are very different technologies. "Backward compatible" on that page refers to support for ArcGIS 9.3.x servers from 10.0 clients, not across database releases (which I know do not work, because a minor release changed the default bitsize of date types somewhen between 8.3 and 8.3.8). If you connected to a 32-bit 9.05 PostgreSQL with PostGIS 1.5.1 from a 32-bit or 64-bit ArcGIS client, then yes, it is supported.  Higher releases fall in "assumed to work"; lower releases are "unsupported" (but may work [for now]). In general, it's best to make a snapshot of PostgreSQL and PostGIS binaries 3-6 months before a new version of ArcGIS is scheduled to be released, so that you can be sure to find compatible binaries when ArcGIS finishes certification and is ready to ship. - V ... View more

It's not generally practical to do certification testing on a new database with old application software.  It's not at all possible to certify old application software with an unreleased database application. With release imminent, you might want to try 10.0 SP4 with the final shipped former- Denali, but even if it were to be certified, it probably wouldn't be until 10.0 SP5. A Tech Support incident might be a better way to obtain this information, since the the set of folks who post here frequently doesn't intersect the set of folks who are empowered to make future-looking commitments. - V ... View more

The '-9' error code is SE_INVALID_USER (with meaning "CANNOT VALIDATE THE SPECIFIED USER AND PASSWORD"). I suggest you make sure the 'sde' server login corresponds to an 'sde' schema user in the target database. - V ... View more

That's unlikely to be a safe assumption.  Even Query Layers needs to be compiled against a reference release.  If a minor revision breaks reverse client compatibilty, then all versions at that level and higher will shift from "assumed to work" to "unsupported". - V ... View more

Dynamic link libraries are resolved by the use of the LD_LIBRARY_PATH variable. You must populate it with the colon-delimited list of directories where desired shared libraries reside; the ArcSDE libraries must be in this list.  How you do this is a shell-specific issue, but using Bourne, Korn, and BASH shells, something like the following will work: SDEHOME=/opt/esri/sdeexe100_pg32-sp4 PATH=$SDEHOME/bin:$PATH LD_LIBRARY_PATH=/opt/postgres/pg-8.3.8/lib:$SDEHOME/lib:/usr/X11R6/LessTif/Motif2.0/lib:/usr/X11R6/lib:/usr/local/lib:/usr/lib export SDEHOME PATH LD_LIBRARY_PATH You can locate any missing shared libraries by using the `ldd` command: $ which sdesetup /opt/esri/sdeexe100_pg32-sp2/bin/sdesetup $ ldd `which sdesetup`         linux-gate.so.1 =>  (0x00123000)         libsdesetup.so => /opt/esri/sdeexe100_pg32-sp2/lib/libsdesetup.so (0x00cd0000)         libsde.so => /opt/postgres/pg-8.3.8/lib/libsde.so (0x00212000)         libsg.so => /opt/postgres/pg-8.3.8/lib/libsg.so (0x00e04000)         libpe.so => /opt/postgres/pg-8.3.8/lib/libpe.so (0x0064f000)         libXm.so.3 => /usr/lib/libXm.so.3 (0x00e64000)         libXmu.so.6 => /usr/lib/libXmu.so.6 (0x00c45000)         libXp.so.6 => /usr/lib/libXp.so.6 (0x00a3d000)         libXt.so.6 => /usr/lib/libXt.so.6 (0x06621000)         libSM.so.6 => /usr/lib/libSM.so.6 (0x00110000)         libICE.so.6 => /usr/lib/libICE.so.6 (0x00124000)         libXext.so.6 => /usr/lib/libXext.so.6 (0x00dce000)         libX11.so.6 => /usr/lib/libX11.so.6 (0x00ace000)         libg2c.so.0 => /usr/lib/libg2c.so.0 (0x0013e000)         libpthread.so.0 => /lib/libpthread.so.0 (0x0015c000)         libdl.so.2 => /lib/libdl.so.2 (0x00c3f000)         libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x06188000)         libm.so.6 => /lib/libm.so.6 (0x00c16000)         libc.so.6 => /lib/libc.so.6 (0x01cc6000)         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00173000)         libXau.so.6 => /usr/lib/libXau.so.6 (0x00119000)         libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x0011c000)         /lib/ld-linux.so.2 (0x00ab2000) - V ... View more

If you have a new topic, please post it only in a new thread  (as you have here), but please do not double-post (it makes finding answers more difficult). - V ... View more

ArcSDE doesn't directly support multipatch geometries -- the SE_SHAPE geometry model doesn't support them.  ArcGIS uses the CAD object, and hides multipatches from ArcSDE.  However, only ArcGIS can access them there.  So, there's no special requirements, but it's NOT just another type of vector data. - V ... View more

The analyze tool should detect the native layer type and either grey-out or at least ignore the 'F' table analysis option, which would prevent this issue from arising.  Please contact Tech Support with a screenshot so a NIM can be created. - V ... View more

There's a huge number of variables that go into raster loading performance.  Some of them are under your control (like the Oracle tuning and compression options) some not (like the performance of the 9.2 raster processing libraries).  There have been three significant changes with recent (10.x) ArcGIS products: Incorporation of the GDAL raster libraries, the use of ArcGIS Server caches, and the use 9.2 Image Server technology into the ArcGIS product base.  Each of these weakened the use of rasters within database; taken together, they have effectively eliminated the need to load raster data into databases at all.  While you probably have some room for database tuning (which would require starting the load over again), I can't help but wonder if you should reevaluate the long-term effectiveness of your task. - V ... View more

You'll need to provide more information about your development environment, since the product you're using will make a large difference in the details of which kind of connection you need to make.  Every initial post should include the exact version and service pack level of your entire software stack (OS, database, ArcSDE, and ArcGIS client). It also helps if you post the code which is giving you problems, along with the exact error messages. Please note that most of the development environments (ArcObjects, MapObjects, etc.) have their own forums specifically for API questions.  It's generally considered "poor 'netiquette" to post the same message in multiple locations, since you're essentially asking folks to take the time out to help you, then immediately turning your back to them to look elsewhere (meanwhile, it's now harder for others to search on the same topic in the search engine, because there's a clutter of possibly conflicting answers). Since you've already posted this over in ArcObjects, it's probably best for all followups to go there. - V ... View more

That's usually a result of bad database hygiene -- Tables registered with ArcSDE should be deleted with ArcSDE or ArcGIS tools; tables registered with the geodatabase should be deleted only with ArcGIS. The best work-around is to create a trivial table via SQL with the same name, then follow correct removal procedure (you don't generally need to recreate the ArcSDE-managed tables).  I don't recommend hacking the registry tables (very unsupported unless on the phone with Tech Support, and 9.1 is so retired that 9.2 will be retired soon, so this isn't an option). - V ... View more

Esri can't fix it if they don't know it's broke.  Please contact Tech Support to start an incident. This is also the best way to get a supported work-around. - V ... View more

According to the documentation, ArcSDE supports varchar(MAX) as an SE_CLOB_TYPE column, but if you're using ArcGIS to access through OLE DB, there might be other limitations on the supported types. - V ... View more