Latest Contributions by WilliamCraft

I can't find anything on how to directly register a table with the geodatabase inside a feature dataset using SDELAYER, either.  But, I also can't find anything that says Oracle Spatial object classes can't exist in feature datasets.    How about trying to register the table at the root of the geodatabase but using another data storage type (SDELOB or ST_Geometry), then try moving it into a feature dataset using ArcCatalog, and THEN changing the geometry data storage type using SDELAYER -O MIGRATE ?  In other words, you might be able to move the newly-registered table into a feature dataset if you don't initially register it as SDO_GEOMETRY.  Maybe you already tried this... and that's what you meant by "I registered the layer normally". ... View more

I've completed the testing discussed above and one thing I need to correct / mention / clarify is that ArcGIS connections to the logical can only be made if ALTER DATABASE guard none; is issued by the SYS user to the logical standby.  Otherwise, the following error is returned: [ATTACH=CONFIG]31874[/ATTACH] Doing this turns off data guard altogether, which is not favorable.  I apologize for not indicating this earlier; I know this requirement kind of defeats the purpose of data guard altogether.  So what this means is that even while log shipping is still enabled and redo logs are still configured to apply to the standby, edits that I've made (changing geometries and attributes as well as adding a feature class and adding a field) do not actually ever get applied to the standby.  The logs get shipped but never applied, despite the logical standby showing a Normal status.  Re-enabling Data Guard does not help, either.  The logical standby will be several logs behind the primary, forever.  Making the change to the EXTPROC file did not change any of the behavior, unfortunately. ... View more

Thanks for your reply and suggestion, Emad.  I went ahead and configured my EXTPROC file for 11g, making sure to point to the correct 10.2.1 st_shapelib.dll file on the database server.  When attempting to create a new logical standby, I am still seeing the same notifications from Oracle about the unsupported objects, fields, and data types: [ATTACH=CONFIG]31869[/ATTACH] I will continue with creating the logical standby to see if, after adding the exclusions, I am able to make DML and DDL changes without breaking the replication and then report back when further testing is complete.  On another note, in reference to my physical standby testing above, most of my work was with using direct connect.  I was seeing good results and behavior with the ArcSDE application service too, although I would recommend direct connect in just about any situation. ... View more

After several weeks of testing, I am finally ready to update this thread again.  Below are my findings: Physical Standby databases are, by very nature according to Oracle, read-only databases that are exact copies of their respective primary databases.  They receive information via Oracle's Redo Apply (or optionally, Real Time Apply) log shipping mechanism at the block level and are always started in Mount mode.  I have found them to be very robust; edits to geometric networks, compress operations, and rec & post operations all make it over to the standby when performed on the primary, as expected.  After switching over to the standby, the same behavior occurs the other way just as well.  In other words, transactions (all DDL and DML) are shipped the other way since switching over results in the primary and standby swapping roles.  I have been able to perform versioned editing without issue on both sides only to find that the standby redo logs are shipped and applied without issue on the opposite side.  If you want to verify that the STATES, VERSIONS, and STATE_LINEAGES tables (or any others for that matter) in the standby show the same information as the primary, you can query the standby the standby using a non-Esri application such as SQL*plus, DB Artisan, or SQL Developer.  Just make sure that Real-Time SQL (not the same as the aforementioned "Real Time Apply") is enabled on the primary database (offered at 11g and later); it then allows read-only connections.  As far as I can see, Physical Standby databases do NOT allow connections from an ArcGIS client because connecting with an ArcGIS client is actually NOT a read-only connection.  When an ArcGIS client connects, there are write operations that occur by default... it's just how the software works.  To connect to the physical standby, you MUST perform a switchover or failover which will change the role of the standby to become primary; thus starting it up in read-write mode.  Logical Standby databases are inherently different; they use Oracle's SQL Apply log shipping mechanism and are always started in read-write mode.  However, there are major issues with these databases when it comes to storing and accessing GEOdatabases.  Despite logical standby databases being "editable", they only allow DML changes, not DDL.  While it is one thing to replicate changes from primary to standby, it is another thing to replicate complex changes and it is yet another thing to allow ArcGIS client connections to the standby.  ArcGIS clients instantiate DDL when connecting with the database, so logical standby databases will yield an error; in other words, they write values to the database and they apply schema changes upon connecting.  To get around this, there are 24 exclusions that need to be inputted into the logical standby database before an ArcGIS client can connect.  Those are listed below.  When setting up a logical standby via Oracle Enterprise Manager (OEM) / Cloud Control, you are notified that certain objects in the database are not supported for replication with logical standby databases.  That is why exclusions like these need to be made; otherwise replication won't just "not work for some objects", it will actually break entirely and the standby redo logs won't get applied to the standby whatsoever.  (Note: the exclusions below can be run as the SYS user and have been tested against 10.2.1 geodatabases using the SDELOB spatial data type): EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => '%', -            object_name => 'SDE_LOGFILES'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => '%', -            object_name => 'SDE_LOGFILE_DATA'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => '%', -            object_name => 'SDE_EXCEPTIONS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => 'SDE', -          object_name => 'PROCESS_INFORMATION'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => 'SDE', -          object_name => 'PROCESS_INFORMATION'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => 'SDE', -          object_name => 'OBJECT_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => 'SDE', -          object_name => 'OBJECT_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => 'SDE', -          object_name => 'STATE_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => 'SDE', -          object_name => 'STATE_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => 'SDE', -          object_name => 'TABLE_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => 'SDE', -          object_name => 'TABLE_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => 'SDE', -          object_name => 'LAYER_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => 'SDE', -          object_name => 'LAYER_LOCKS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => '%', -            object_name => 'SDE_LOGFILE_LID_GEN'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => '%', -            object_name => 'SDE_LOGFILE_POOL'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => '%', -            object_name => 'SDE_LOGFILE_POOL'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => '%', -            object_name => 'SDE_LOGFILE_LID_GEN'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => 'SDE', -          object_name => 'CONNECTION_ID_GENERATOR'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => 'SDE', -          object_name => 'CONNECTION_ID_GENE RATOR'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => '%', -            object_name => 'SDE_LOGFILES'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => '%', -            object_name => 'SDE_LOGFILE_DATA'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => '%', -            object_name => 'SDE_EXCEPTIONS'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL', -      schema_name => '%', -            object_name => 'SDE_LOGFILE%'); EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', -      schema_name => '%', -            object_name => 'SDE_LOGFILE%'); One thing to note is that the SQL Apply mechanism of logical standby databases does not work with ST_Geometry.  Even if you are using another data type like SDELOB, you should know that the SDE.GDB_ITEMS table at 10.2.1 (actually, probably at 10.1 and later) has a SHAPE field which stores the spatial envelope of all spatial data in the geodatabase.  This SHAPE field is of ST_Geometry type, which as I mentioned does not work with logical standby replication.  It cannot be changed; I asked Esri's PSSG this question.  What I think this implies is that 10.1 and later geodatabases will not work whatsoever with logical standby technology from Oracle.  At 9.3.1 (and possibly 10.0), I believe it could work as far as updating values and geometries (just not schema changes); but because of the ST_Geometry data type introduced for the GDB_ITEMS SHAPE field, I have found that logical standby databases won't work if you have any sort of schema change because those changes touch the GDB_ITEMS table.  You'll still be able to make a connection, but DDL and DML replication will fail.  On a side note, I have found that Oracle Streams uses much of the same underlying technology as logical standby databases.  Although I did not perform exhaustive testing with Streams, I was not able to successfully get replication to behave correctly.  Instead, I saw similar results to what I saw with logical standby databases.  While Oracle replication has been announced by Esri as "officially supported", I did not hear from Esri that Oracle replication using physical standby database is unsupported either.  It is my impression that physical standby databases are more robust and behave much better with Esri technology than logical standby databases. Several Esri clients are using this configuration and have been successful with physical standby databases from a DR perspective.  Just remember that you cannot connect to the physical standby even with Real-Time SQL enabled because Oracle sets it to read-only.  To do so would mean that you would need to perform a failover or switchover.  Connecting to the physical standby would be great for reporting and query offloading purposes, and this is possible with non-Esri clients.  But for ArcGIS connections, it is not possible.  I hope this is helpful to others who have been interested in using Oracle's Active Data Guard Technology.  If and when I learn more, I will update this thread. ... View more

the create tiles on demand is only for those areas that fall outside of this AOI So you have set tiles to cache on demand for only a portion of the AOI rather than all of the AOI it sounds like.  That's not what came across in your previous posts but maybe I read too much into your statement.  The only way I could see tile rendering performance be related to the data store (e.g., changing from file GDB to enterprise GDB) is if you were going to tell me that initial tile creation is much slower than before but that once they are created no more issues exist.  If that's not the case and tiles are slow no matter how many times they're requested, then there doesn't seem to be a performance issue associated with on-demand caching and changing the type of data store.  You should probably consider opening an Esri ticket. ... View more

I do have Create tiles on demand checked but that was also checked before. The statement above implies that tiles haven't been pre-generated; instead your tiles will only generate when a user goes a particular extent for the first time.  Setting your cache to generate tiles on demand will use more of your server's resources to generate the tiles, which could hinder performance for everyone.  But once a tile is generated on demand, tiles in that area should draw much faster on subsequent requests.  I don't recommend doing this for the entire cache; instead, do this for light-traffic areas and pre-render tiles for heavy-traffic areas.  Although a bit older, this article discusses some best practice concepts for caching on demand: http://blogs.esri.com/esri/arcgis/2008/09/18/strategies-for-on-demand-caching/ it's almost as if the cache didn't finish in the AOI even though the status said it did Stepping back for a second, I believe you initially said that you were having poor performance with rendering the tiles.  The statement above suggests to me that you are having issues rendering certain tiles at all.  Is it one or the other, or both?  What does Fiddler return when you having it running during tile requests?  If everything is exactly the same in terms of your cache tile settings when creating the cache as well as in terms of your service settings, I can't think of any reason why your cache tiles would perform poorly.  I can see them taking longer to get created (since you said the AOI is now larger and your data got moved to an enterprise geodatabase), but that shouldn't affect draw time if the tiles are pre-rendered.  However, I'd like to understand more about the answer to the first question I have at the very top of this response first. Why it is slow for you at 10.2 but not at 10.1 is a mystery to me at this point in time.  However, it feels like the culprit could be the data store change rather than simply the 10.1 to 10.2 upgrade.  Data often performs slower from an enterprise geodatabase than from a file geodatabase.  This might just be your problem. ... View more

Besides the Caching tab, how about your other map service settings for the cached service(s)?  Is everything the same at 10.2 as it was in 10.1 for the Capabilities, Parameters, Pooling, and Parameters sections?  As you mentioned, the caching settings are exactly the same at 10.2 as they were in 10.1 so that shouldn't be an issue as long as you're positive this is the case. ... View more

Is ArcGIS for Server 10.2 on the same machine on which 10.1 was previously installed, or is it on a new machine entirely? ... View more

Quick question: Which version is your Flex Viewer connecting to (the parent or one of the child versions)?  If you are seeing behavior whereby edits have been reverted back to "pre-edit" as you describe, my first thought is that you should review how you are reconciling and posting from child versions up to their respective parent(s).  Make sure that when you reconcile you are doing so in favor of the correct version.  Could you provide more information about how you are doing rec/post? ... View more

If you are receiving the same error as before when trying to register the connection with ArcGIS Server, then perhaps the issue is with adding the ;MultiSubnetFailover=true;Connect Timeout=120 text to your HOSTNAME\INSTANCENAME connection string.  I do not think ArcGIS supports the passing of those parameters in the Instance field.  What happens when you try removing them and ONLY use HOSTNAME\INSTANCENAME in the Instance field? ... View more

Are you able to view the logs from ArcGIS Manager as expected?  I've heard of very similar behavior before; the thread below discusses the details of that particular case.  It doesn't contain a specific fix, but it might send you in the right direction for troubleshooting further: http://forums.arcgis.com/threads/98715-Problem-viewing-ArcServer-Log-Entries-via-the-Rest-Endpoint-Admin-interface ... View more

I'd like to know how to add data to an existing point file feature class(a part of a geodatabase and not a shapefile)from an excel spreadsheet and have those points be visible and editable in Arcmap, as well as have the corresponding data within an accessible attribute table in Arcmap Once your points appear in ArcMap from adding the XY Event Layer, right click the layer in the Table of Contents, go to the Data sub-menu, and choose Export.  From there, export your data to a feature class within a temporary or scratch geodatabase.  Next, you need to load these exported features into your existing feature class that you mentioned earlier.  To do that, navigate to your existing feature class (the one into which you want to load) from ArcCatalog, right click it and select Load.  Follow the Simple Data Loader wizard from there, which will include clicking the Add button to choose the scratch or temp feature class you just created from your ArcMap Export.  In the wizard, you will also need to match up your source and target fields; afterwards, the new features should be appended into your existing feature class. ... View more

The Server Name in your first screenshot shows GSMIDBLPRD, but the Instance value in your second screenshot shows GSMIDBPRD (missing the "L").  Which is correct?  Also, what's the name of the actual SQL Server instance?  I am guessing it is MSSQLSERVER.  For the ArcGIS connection properties window, try inputting the following syntax: HOSTNAME\INSTANCENAME which translates to GSMIDBLPRD\MSSQLSERVER or GSMIDBPRD\MSSQLSERVER depending on which hostname spelling is correct. Also, it may not matter, but I am seeing a different username for both screenshots: prd vs iprd. ... View more

Just to rule out the spatial view entirely, what is the draw-time performance if you add it to an empty map document and pan/zoom?  Is it always quick to draw or does it exhibit the same behavior as you see when it's intermittently slow in the external map service?  For the external map service containing the spatial view, what are your timeout values set to (e.g., max time client can use service and max time client waits for a service)?  Does the corresponding internal service match the external service exactly in terms of content (data layers, scale thresholds, symbology)?  You started to say something about the instances in use within your post, but I think something got cut off because your comment seems to be incomplete.  Was there more information that you wanted to share on that topic? ... View more