Latest Contributions by MarcoBoeringa

http://forums.arcgis.com/threads/85096-Deprecation-plans-for-10.1-and-10.2 "ArcGIS 10.2 will be the last major release to include the ArcSDE application server. Esri encourages those that have deployed an ArcSDE application server to move to new database connections introduced in 10.1 as part of their next upgrade." Yes, I saw this too. Interesting, I had not yet seen this updated deprecation plan of the 7th of May including the changes expected for 10.2 and beyond and the now officially announced deprecation of the ArcSDE Application Server, ArcSDE Command Line tools and ArcSDE C/Java SDKs after 10.2. Not unexpected, but still, I wonder if there might be future extension for this deprecation... To many people may still depend on it and not yet be in a situation to make all the necessary changes in time. Just look at VBA... extended to 10.2 while initially announced deprecated at 10.1... Anyway, I am in the process of creating two updated Geodatabase Framework diagrams that will incorporate and show this deprecation to make it more understandable. One diagram will depict the situation at 10.2, the other the situation beyond (well, at least as far as my "crystal ball" in the form of this deprecation plan allows me...). ... View more

This Help page also specifically lists a restriction on using WHERE clauses to join data when using Versioned Views: "Versioned views only work with an individual versioned table or feature class. You cannot use a where clause to join multiple tables together or restrict which rows or columns are included in a versioned view." A slightly related issue is the other reported problem on the same page (see the "Note") of a potential issue with duplicate ObjectIDs with 1:N joins in ArcGIS for Desktop. I know you are only doing a 1:1 here and not using ArcMap, but still...: "If you choose to replace views created by ArcGIS by altering the view afterward, you are taking responsibility for not only the query's correctness and efficiency but also its relevance and suitability for use with ArcGIS clients. For example, creating one-to-many views involving feature classes results in duplicate ObjectIDs. This leads to unexpected behavior in applications such as ArcMap and ArcCatalog, because the ObjectID is supposed to contain unique values." ... View more

According to this 10.0 Help page, it seems to be returning either a List object in case of SQL SELECT statement, or a Boolean for fail/success when running a schema changing SQL query (DDL), or UPDATE / INSERT statement: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//000v00000057000000.htm Also see this: http://developmentfaction.blogspot.nl/2010/07/python-tip-using-arcsdesqlexecute-to.html ... View more

I am wondering if it is some kind of projection / spatial reference issue, with the stored SRID of the shapes somehow being messed up? In your first post you were slightly unclear, suggesting that in some cases, you did see shapes appearing? ("... In ArcCatalog or ArcMap it makes the views look like they are empty, or if they draw, you can't zoom in, out or pan because the features, if present disappear...") Do you, or don't you ever see shapes appearing in ArcMap / ArcCatalog? ... View more

What happens when you create a new spatial view using the options now available in the context menu of a Database Connection as described here?: Creating a database view in ArcGIS for Desktop The data shows up as a table, no spatial rendering occurs. At 10.1, it is normal for a Spatial View, or for that matter any table or database view with a spatial column, to initially show up as a table. Once you click it, ArcGIS will read the first record(s?) and determine the geometry type and show it in the catalog tree. This behavior is because ArcGIS can't "know" the feature/geometry type beforehand, as it isn't "stored" like in a table registered with an ESRI geodatabase, where such system metadata is stored in the ArcSDE Repository. But anyway, the data should render in ArcCatalog, if that isn't the case even with the standard "New\View" option, than there is a deeper issue... the issue with recreating the views is that we have many, more than 30 that would have to be recreated and we don't know that one our ETL runs again the views will work. We are still testing that. To be honest, I can't think of any reason why the ETL should influence the functioning of any database view or not. Spatial Views are like any other normal database view. They just store the SQL statement necessary to collect or process the tables and perform any joins etc. If the underlying tables change (new or deleted records), it has no consequences for the SQL statements, UNLESS there are schema changes (e.g. changes in field names, field types). This raises a question though: Can you see any changes to schema, and especialy the keyfields that perform the join between the existing spatial tables in your database and the extracted business data between the old and new setup? Maybe the join fails at 10.1? By the way, did you switch storage type (SDEBINARY to SQL Server native "Geometry")? Storage is still SDEBinary - we haven't even looked at changing it yet. It may be time to contact ESRI support... ... View more

What happens when you create a new spatial view using the options now available in the context menu of a Database Connection as described here?: Creating a database view in ArcGIS for Desktop You may also wish to use this page as a quick reference for what to do when attempting the option described in the link above: Example: Creating a spatial view in SQL Server using SQL By the way, did you switch storage type (SDEBINARY to SQL Server native "Geometry")? ... View more

You don't state from what version you are upgrading (9.3? 10.0? what service pack?), and whether or not you installed SP1 with 10.1 and any applicable patches. Anyway, I do know that Multiversioned Views changed from 10.0 to 10.1. They are now not only called "Versioned Views", but the associated stored procedures and functions in the ArcSDE Repository also underwent changes. Versioned Views now are also *fully automatically* created as soon as you register a layer as versioned. These changes have to do with the introduction of the ArcGIS Spatial Data Server, and a general better possibility to use - and edit - these views programmatically and through SQL or programming. There is now a new editing option that allows you to edit the DEFAULT version through a Versioned View (actually, this last thing is not entirely new but had issues at 9.3.1 and below, and only now seems fully implemented). This 10.1 Help page talks of the need to re-create Multiversioned Views 10.1 as Versioned Views in order to be fully useable (see one of the "Note" remarks), so this change may have effected your Spatial Views (assuming they used Multiversioned Views), and they may indeed need to be re-created. I would really try and see if you can create a new test dataset and 10.1 style Versioned View by importing a layer, and registering as versioned. Than use the Query Layer option of 10.1 to add the data to ArcMap, or simply browse the database connection in ArcCatalog and add from there. If that layer with its 10.1 Versioned View still doesn't display properly, there may be a deeper underlying issue. If it does display properly, than you know it's not the database connection or Versioned View functionality by itself, but maybe something with your "legacy" Spatial Views. ... View more

Think of something like a Point and Polyline Feature Class, one representing valves, the other pipes from a pipeline. You add them to a "Geometric Network", and than start editing the network. You move the valve (original Point Feature Class), and the attached Pipes move with it. Or you determine which endpoints in the utility network will be affected by shutting down this valve. This kind of "behavior" requires all kinds of relationships and constraints in the DBMS and in ArcMap to be maintained automatically. That is "behavior" in the context of geodatabases. You don't really "set it", you create it automatically once you define and start using those special complex datatypes like Geometric Networks, Network Datasets, Parcel Fabrics and so on... ... View more

I have contacted the local ESRI dealer, and they will come to assistance today, since they are but busy... ... It seems that now everything works... I have copied everything, and all the data is now on Oracle 11g under SDE 10 SP5. Seems to me it's just going to be coffee and tea with ESRI... 😉 Anyway, may not be a bad thing to have just one last "check-up" on the finished work by someone with a fresh look on it and able to assist you directly versus "remote"... Thanks to you guys, your suggestions saved me. P.S. If I run into more troubles, I'll come back 🙂 You're welcome, and let us know the final outcome! ... View more

It seems that we think alike, Vince 🙂 I didn't give up, instead I decided to follow this manual: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Migrating_to_ArcSDE_64_bit_on_Windows_when_the_existing_DBMS_is_32_bit/002n000000q0000000/ I deleted the geodatabase, created a new one, empty, and installed ArcSDE from the scratch...created the repository, user and voila....the authorization passed without a glitch. So it wasn't the license code... Then, I created the service, started also without problems. Good to hear you finally managed to make headway and get it running! 🙂 But hey, didn't I point out that Help link before to you?!! :confused: ... ;););) Everything went well, with minor stops because of the relationship classes and extensions, privileges, roles creation etc...but now I get the error in the attach, and do not know what it is: [ATTACH=CONFIG]24308[/ATTACH] Any ideas? Tnx, M. Can you provide some more context to this. Is "UTARC" a Feature Class or Stand-alone Table in the original 9.2 geodatabase? And is there a field called "CO_C_JOINT_TYPE" in the attribute table? Is this UTARC table potentially from another business system, registered with the geodatabase but not initially created by ArcGIS? I think you mentioned this whole database involved an Utility Extension? Have you thought of installing that on the new server and client PCs, so that ArcGIS knows about specific custom objects added to the geodatabase base model? ... View more

So, as the things are going badly, this is how it is going to be: Since the ArcGIS Desktop is here used as a base form some Utillity Extension, I will create a new empty gdb, create new SDE user and repository, and use the extensions tools to export/upgrade the data and then bulk load it back to the ArcSDE. I do not see any other solution. ... I just give up, since I have an alternative...not a better one, but an usable one. Milos, Sorry to hear that, but you are probably right it is now the best way to go. I am out of ideas of helping you "remotely"... If you can solve your issues this way, than by all means go for it and don't waste any more time on the impossible "upgrade path". There is something very wrong in the way upgrades are ment to be performed, or in the software configuration that was asked from the extension manufacturer, or maybe in the position of the stars for the past two weeks that I have lost doing this. 🙂 Yeh, I guess the stars didn't align up well... 😉 Good luck with rebuilding and loading the data. Marco ... View more

Can't say if this is the issue, but you're not working on the officially supported release with 9.2.4. Higher release numbers may, or may not, work. Usually, it is best to stick with the ESRI recommended environments. See this Help page: PostgreSQL database requirements for ArcGIS 10.1 ... View more

Milo, Have you ever tried to run the post installation with the specific right-click menu option "Run as Administrator"? It may be a long shot, but sometimes, even when your logged on as Administrator, you still need "Run as Administrator" to get something to work, especially with legacy software. Marco ... View more