Latest Contributions by VinceAngelo

Instant Client will be enough at a future release (10.1), but I've never gotten it to work with 9.x or 10.0. - V ... View more

Login 'qcuser', user 'qcuser', schema 'qcuser'. - V ... View more

Do you have a 32-bit Oracle client library on the ArcGIS Desktop host? (The LoadLibrary function returns "not found" if it is found, but not the right wordsize). - V ... View more

*User* 'sa' does not own the table, *login* 'sa' does (as user 'dbo'). This is not one of the most compelling reasons not to use 'sa' for table creation, but it is a critical problem in your workflow. The documentation also recommends creation of data ownership accounts, and provides the guidance that login must match user must match schema. Registration will function if you follow this guidance. - V ... View more

Keep in mind that the ArcObjects file geodatabase code is written in C++. This is what has been ported into the FileGDB API. Esri has no plan to re-write the file geodatabase API in 'C'. - V ... View more

It's a *really* bad idea to do any table creation in a database as the administrative user (sa, SYSTEM, root,...).  The same goes for using 'sde' or any other internal management account.  Instead, create ownership accounts and roles and manage access to the created objects through roles. In this particular case, the problem is that the login does not match the user and schema, since 'sa' maps to 'dbo'. - V ... View more

Your quoted link just says that tables with potentially corrupt geometries will be scanned for validity with each query (with a performance cost). It does not say that corrupt geometries will be processed or rendered, only that an attempt at correction will be made. If both Oracle tools and 'sdelayer -o feature_info' report a geometry as invalid, it's invalid. The ArcSDE *API* has a function to allow clients to (reluctantly) accept invalid shapes in a stream (as opposed to failing with a database error at the start of the first transfer buffer that would have transferred the first invalid shape), but it then needs to test for that case and do something about it (using this also has a performance cost). No layer flag is going to change a client to incorporate SE_stream_invalid_shape_mode code if it is not already present. There is a third issue here: If ArcGIS sees a CAD object, it's going to use that over the invalid geometry. It's very likely that the "it works" state is not due to ArcSDE permitting operations on invalid geometries (it won't), but to ArcGIS ignoring the invalid shapes in preference to CAD entities. Unfortunately, there is no way you can generate those CAD objects externally (much less via SQL). Altering the undocumented (and continually evolving) EFLAGS mask column is not recommended; you probably shouldn't do this outside of close coordination with Tech Support. - V ... View more

There is no way around enforcement of Clementini topology rules. You can talk with Tech Support, but vertical polygons are not supported by ArcSDE (they can only be stored as Lines ["-e s+"]). The fact that it worked at 9.2 must have been a bug. - V ... View more

You'd probably get a quicker response over in ArcGIS Server - Rest API, since this isn't really an ArcSDE- or geodatabase-specific issue. - V ... View more

What database are your using (including version)? What version of ArcSDE and ArcGIS are in use? What language are you using to execute this constraint? - V ... View more

Was this instance operating previously?  Does the table in question exist (as seen from pgAdmin III)? The easiest way to fix registration issues is to create a nominal table via SQL, then use the highest level where it was registered (probably ArcGIS) to delete it.  Then you should be able to rebuild from scratch (providing your schema is the same as the login user, etc...). - V ... View more

None of the information you have provided indicates that any error has occurred (status 0 is "Success", not an error).  You really ought to contact Tech Support with information about the "cannot read" error.  It's possible that they'll recommend you install 9.3.1 SP2 (released a year ago). - V ... View more

Three processors is exceedingly strange. I'm amazed the OS will recognize that configuration. VMware recommends against 4-CPU VMs on a system with VMs with fewer than that because the system must block until a larger set of CPUs is available, placing the 4-CPU host in contention with *all* the 2-CPU hosts. I didn't see a significant performance benefit of a 4-CPU VM over a a 2-CPU VM when simulating load for 16 simultaneous ArcGIS connections, and both were blown out of the water by an 8-CPU physical host (900 v 800 v 72 seconds). A second 4-CPU VM did a bit better (600 seconds), but still not twice the 2-CPU VM. Linux VMs were often slghtly faster than Windows VMs, and not subject to the simultaneous user limitation of ~72-76 connections. I never measured a benefit to using 64-bit ArcSDE over 32-bit on Windows hosts, though there was a slight benefit (10-15%) on Linux. It would be interesting to see what your performance was like with a Direct Connect client -- it's possible that the bottleneck also involves Oracle (my testing was just ArcSDE application server on VMs, with 2 and 4 node Oracle RAC on physical hosts). - V ... View more

Thus spake Wikipedia: A segmentation fault (often shortened to segfault), bus error or access violation is generally an attempt to access memory that the CPU cannot physically address. I can't think of a single reason why a functional Linux operating system would return a SEGV on the execution of 'ldd'.  You'll need to work this issue with the system administrator. - V ... View more

If you're getting SEGVs from 'ldd', you've got way more problems than inability to setup ArcSDE. I can't really help you stabilize your OS, but you're going to need that before you're likely to make progress on the ArcSDE install. - V ... View more