Latest Contributions by VinceAngelo

Still need an answer to Q5, to see if A6 is significant, but ArcGIS 10.3 is only supported on Oracle 11.2.0.3.x and higher​ (10.4 will up that to 11.2.0.4.x). - V ... View more

We need details to understand what may be going on. Please provide: The exact version (five digits - e.g. 10.2.0.4.7) of Oracle installed on the original enterprise geodatabase The exact version (five digits) of the Oracle client installs Whether the database has been upgraded or transferred to a different server (and if so, the exact version of that database) The exact PATH variable contents Whether you have 64-bit background geoprocessing installed Whether you have the background geoprocessing opption enabled Please do not ever post passwords on the Internet (and never make the SDE user password 'sde' -- this is a huge vulnerability that threatens your entire geodatabase). - V ... View more

Please clarify what you are attempting by describing the steps preceding this error, and what command produced the error. It appears you have made changes to the database and have not reconfigured it correctly so that even a tnsping would succeeed.  If Oracle has no connectivity, there really isn't anything ArcGIS can do. - V ... View more

I've had clients with 12K feature datasets (and 150K tables), which, while not quite ideal, certainly weren't "unworkable". The time for placing rasters in databases ended at ArcGIS 9.2, when cached map services were introduced.  There really is no reason to place the rasters in a modern database, which means that this set of <5K tables would be a large, but not very large enterprise geodatabase. 16+K rasters is quite a few.  Have you tried organizing them with mosaic datasets? - V ... View more

There could be any number of problems, but insufficient information to determine which one. - V ... View more

I've always avoided both "0" and "4326" on principle, so I've never had to deal with fixing this problem.  Go with George's answer on this. FWIW: I find sub-millimeter accuracy to be an even bigger lie than sub-millimeter precision, especially in geodetic coordinates -- One skateboarder brushing concrete could invalidate the entire curbline layer! - V ... View more

Please be very careful with your spatial reference IDs.  It's almost never as simple as just changing an ID value somewhere. In the Esri realm, a "spatial reference" is much more than just a coordinate system.  Every spatial reference has a coordinate system, but it also has the false X/Y origin, and XY scale factor, and Z origin, and Z scale factor, and M origin, and M scale factor, and tolerances for all three (plus a precision flag).  Changing SRIDs is unsupported because the data itself is encoded with the contents of these parameters, so changing between two SRIDs in metadata will generate incorrect decoding of the coordinate values, causing them to shift and/or scale within the common coordinate system. Personally, I find the default XY scales chosen by both Desktop and Server to be far too precise for most data encoded in the default GCS_WGS_1984 coordsys.  Most data collected above 1:1m doesn't need sub-millimeter precision, and storing it with an XY scale that preserves such precision increases the storage requirements of linear and areal data (one customer was amazed to see they could double their layer performance just by using a reasonable precision).  I would encourage you to evaluate the benefits of using a 1,000,000 scalefactor (~11cm precision), and abandoning "0" and "4326" for 300006 (or whatever sequence-generated value is rolled up).  This will have the side-effect of freeing you from the vaguarities of "default" SRID changes. - V ... View more

In all RDBMSes except Oracle (11g and below), different "databases" are actually stored in the same instance.  The fact that this is not true in Oracle means you can't use the same techniques as recommended for other RDBMS software. It is not possible to create an index on a view.  Views always use the index on the base table, unless the view is really an Oracle database link, in which case it often won't use the index even then. What you need to do is make a decision.  You can: Establish a connection protocol that allows GIS users to access the spatial table in database1 via Query Layers Establish a process to replicate the database1 table in database2 (and then another process to maintain synchronization when changes occur in database1) Since I'm a data manipulation geek, I'm usually asked to do option 2, but it's often more complex and subject to periodic re-synchronization than most project managers realize. - V ... View more

When moving into a new community, it's always a good idea to take a look around and see how things appear to function.  Do folks sit out on their stoops after dark?  Do they leave trash cans at the curb year round? Are there burned out car chassis in the front yard?  These are all good indicators of what your neighborhood experience will be like, and should inform your own stoop-sitting, trash-tending, and chassis-junking behavior. Here in GeoNet, most questions have short, descriptive subjects, and long, fact-filled bodies (with screen-shots and code snippets).  This question stands out, and not in a good way ("help me" is actually one of the worst things you can ever place in a technical exchange forum, since it demonstrates that you don't even acknowledge the purpose of the forum, or honor the effort the volunteers are making to read your message). Since your other question was a lot closer to a reasonable title length, I'm going to second Dan's recommendation to Delete this post (fourth selection down in the Actions list to the upper right) and Edit the other one to include all the information which would be necessary to help you. I'll include a link to my What to include in a GeoNet question blog post, so you can collect the necessary pieces before editing. Good luck. - V ... View more

This question has been asked before, but the answer hasn't really changed -- It's very difficult to distinguish between the bytes used in tables and the bytes used in blocks that are assigned for use in tables, and the bytes reserved in containers because of the blocks assigned to tables, which makes determining absolute storage a much less absolute exercise.  It's possible to hunt down the information, but it requires a great deal of patience and a detailed knowledge of how the geodatabase is implemented on your database platform. - V ... View more

If you've altered the Listener, you probably used the wrong procedure.  Since 11gR2, the correct library registration procedure involves the hs/extproc.ora file. - V ... View more

There would still be the fundamental issue that each host would have its own collection of connection logs, making meaningful analysis impossible.  The only central repository of login attempts is the database, which clients can't log to, because they didn't successfully connect.  You just need to enable logging by the database (which is outside the scope of ArcGIS). - V ... View more

You should probably run a filesystem check on your install disk.  Sometimes disk content failure is due to random electromagnetic effects, but sometimes it's due to physical damage to the disk platter.  I once had a client lose 48Tb of raster data (the better part of 9 months of loading effort) due to a firmware failure in the disk array controller (they had a backup array, but that was corrupted by mirroring the production volume). Systematic backups (actually, verified systematic backups) aren't just a good idea. - V ... View more

You've left out important details from your  problem statement: Which mechanism did you use to configure the instance with the libst_shapelib.so DLL? Is the full path to that library present on each node in the cluster? - V ... View more