Latest Contributions by VinceAngelo

What does 'sdetable -o describe' report for the table? What 'sdelayer -o register' command are you using (less password)? Are you specifying an existing NOT NULL unique integer rowid column with the '-C' flag? - V ... View more

You really ought to use the same client as the server (Oracle 9.2.0.8 32-bit client with ArcSDE for Oracle 9i 9.2sp6 to connect to a 9.2.0.8 server).  If you were using an early/buggy Oracle 9.2 client (not one patched to 9.2.0.8), that would explain the memory error. - V ... View more

When using native geometry, use SQL to create the view, then 'sdelayer -o register' to make it available through ArcSDE. - V ... View more

You really don't want a 1.3 billion point table anywhere -- Even with the best possible performance, you're looking at a 30+ hour load time (and hours to do any meaningful analysis). If your points don't vary in value all that much, you might be able to map 1Kx1K pixel chunks into a multi-point table (where all the points with the same value are merged into a single feature) -- this will still be moderately unusable as tens of thousands of features with tens of thousands of verticies. Your best bet is to apply some classification scheme and convert the result into a polygon table.  Still unwieldy due to the vertex count, but better than the other options. - V ... View more

There is no direct correspondence between the release number and service pack. Releases are usually incremented during development, so that sometimes "Final" will be as high as xy003 or xy004. I always name my install directories with the release version and service pack so I can keep things straight (I usually have two or three *dozen* SDEHOMEs in my ESRI directory, so using a naming convention is not optional). You can use the service pack finder on Windows hosts to determine the actual product version. I suggested that you drop the SDE user to simplify your problem. No install should ever receive a "memory fault", so not having to work with an upgrade can sometimes isolate the actual problem. At this point you'd probably be better off contacting Tech Support to walk you through the trouble-shooting process. - V ... View more

What ArcGIS client are you using?  Only ArcGIS 10.0 clients can connect to a 10.0 ArcSDE server. - V ... View more

Those are 'sdesetup' messages, consistent with the expected output of a fresh install, not something 'gsrvr' would generate. If you used Direct Connect from ArcGIS, the error logs would be on the Desktop box, not the server. - V ... View more

No SP3 was ever released for 9.1. Is your old ArcSDE "9.1sp2 General Update 3"? Upgrading to 9.2sp6 on 9iR2 at this late date is setting yourself up for an imminent upgrade, since 9.2 is in mature status and 9iR2 isn't supported by Oracle. Heck, as of July, 10gR2 isn't supported either (you'd need ArcSDE 9.3.1 to support 11gR1). It's likely that the lack of logs indicates ArcSDE didn't really even start before the OS fataled the application (which in turn indicates an improper application configuration). What is the version of your Oracle 32-bit client install (required for 32-bit ArcSDE). If you imported all the users (including SDE) with exp/imp, then you certainly don't want the '-o install' option -- use '-o upgrade' instead (after you make sure that SDE has the required permissions). You might be better served by dropping the SDE user, working on installing 9.2sp6 cleanly, then imp-ing SDE again to do an upgrade. - V ... View more

What user starts the 'sdemon' application? One way to find out what's wrong with the environment is to replace 'gsrvr' with a shell script that dumps the environment (and possibly a ldd of the superceeded gsrvr). It's just about time to contact Tech Support on this issue.  The only time I've seen something similar was on a client's HP/UX host where the 64-bit install binaries had been corrupted by a silent disk failure. - V ... View more

Does the giomgr process user's .profile, .bash_profile or .bashrc clear the contents of PATH or LD_LIBRARY_PATH? By the time the dbinit.sde is consulted, it's too late to set the SDEHOME or LD_LIBRARY_PATH. My ArcSDE boot script executes $SDEHOME/etc/.profile to establish database-specific environment variables before executing 'sdemon -o start'. This way I only need to put the ORACLE_SID or TWO_TASK (and possibly NLS_LANG) in the dbinit.sde (and can use the same profile for all Oracle instances, regardless of ArcSDE release). My complete multi-instance Linux boot script framework is buried in the se_toolkit release tree (in all release bundles, under samples/boot/redhat_etc). - V ### $SDEHOME/etc/.profile ### ORACLE_HOME=/opt/oracle/product/10.2.0/db32 LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH NLS_LANG=AMERICAN_AMERICA.AL32UTF8 export ORACLE_HOME NLS_LANG LD_LIBRARY_PATH ### $SDEHOME/etc/dbinit.sde ### set ORACLE_SID=xxxx10g2 unset TWO_TASK ### /etc/init.d/arcsde ### Start_SDE() { ... # .. Set environment variables # SDEHOME=$2 PATH=$SDEHOME/bin:$origPATH LD_LIBRARY_PATH=$SDEHOME/lib:$origLD SDEVERBOSE=$3 export SDEHOME PATH LD_LIBRARY_PATH SDEVERBOSE # .. Retrieve password # if [ -f $SDEHOME/etc/.passwd ]; then sdepass=`cat $SDEHOME/etc/.passwd` else report_error ERROR && printf "\t--> $SDEHOME/etc/.passwd not found\n" return 1 fi # .. Execute etc/.profile (if present) # if [ -f $SDEHOME/etc/.profile -a ! -x $SDEHOME/etc/.profile ]; then report_error ERROR && printf "\t--> $SDEHOME/etc/.profile not executable\n" return 1 fi test -x $SDEHOME/etc/.profile && . $SDEHOME/etc/.profile # .. Execute command # sdemon -o start -i $1 -p $sdepass >> $logFile 2>&1 ... } ... View more

Never, never, never use LZ77 compression for a lossy source image.  If the source was MrSID or JPEG2000 use JP2 compression (otherwise you increase image size by a factor of 10-40 [yes, 1000% to 4000% storage increase], with no benefit).  NEAREST is most likely to increase "snow" since it doesn't try for a best fit (as a rule, it should only be used with colormapped rasters).  You need to experiment with BILINEAR and BICUBIC (which use weighted averages of neighbors to better blend the resampled pixels), to see which produces better pyramids with your images. - V ... View more

It is generally not recommended to use lossy-compressed image sources for loading into ArcSDE. You can do so, but you must be careful on which compression algorithm you use in the database, and which algorithm is used in the pyramid (they can be different). What algorithms are you using? With what parameters? What pyramid interpolation method did you choose? Is the image quality issue only with pyramid tiles, or at the base resolution as well. - V ... View more

Given that base64 MIME encoding is going to increase file size by 1/3, it's probably wise to always zip before e-mailing data (including .mdb files) -- this will also give you a way to detect corruption in transfer. The one file solution has a drawback as well -- File geodatabases do not have any real size limitation, while PGDB are limited to 2Gb. - V ... View more

ST_GEOMETRY doesn't have triggers like SDEBINARY and SDELOB, though I'm sure there's an equivalent within the object behavior (one that's not subject to external tampering). - V ... View more

ST_GEOMETRY does not have F or S tables, so it's not just the triggers that are missing. There is an S table analog, but the F table is implemented as a LOB object type in the business table (see the online doc for ST_GEOMETRY storage architecture details). - V ... View more