Latest Contributions by MelissaJarman

‎10-16-2015

Like Freddie said there are some defects that are logged regarding this behavior. In order to be associated with one you will need a reproducible workflow to present to support starting with a new map document. Keep us posted if you submit a support case! Esri Support

‎10-15-2015

Tobias - How were the layers removed from the map document? Manually in the TOC or did you at one time use a tool such as set data source(s). ?

‎09-04-2015

Your post was from quite some time ago, but I am finding that the SetLogHistory (false) is working as expected in arcpy. I am not finding any additional XML inserted into my GDB_ITEMS documentation column for the workspace after executing a compress after arcpy.SetLogHistory(False). Let Support Services know if you are encountering this as an issue. >>> arcpy.SetLogHistory(False) >>> arcpy.Compress_management(r'Database Connections\sqlserver - blakley - 10.3.sde') <Result 'Database Connections\\sqlserver - blakley - 10.3.sde'> >>>

‎06-26-2015

Paul - What you are thinking seems correct that since you are at 10.0 sp2 or higher that this should work without setting the version first - you also shouldn't have to call edit_version. Have you tried to just execute the sql directly without calling edit_version or setting the version? Take a look at this KB 39112 - Cannot edit the DEFAULT version in STANDARD transaction mode What type of geometry is the feature class? Editing the DEFAULT version You could edit the DEFAULT version with SQL through versioned views if one or more of the following are true at your site: The edits to be made are short transactions. Your site requires that the edits made through a versioned view be available to other users immediately. If editing feature classes, the feature classes use SQL spatial types, not binary geometry storage. The table or feature class to be edited is not registered as versioned with the option to move edits to base.

‎06-04-2015

Here is the URL to the presentation: Accessing Your Enterprise Geodatabase using Python | Esri Video

‎05-11-2015

Brad - There are a few ideas out there that discuss some of the workflows of creating sde registered views or registering native geometry type tables with the sde commandline. This applies for spatial tables and database views. These workflows have been replaced with the use of query layers. I am assuming that is where you are mentioning the 'inability to set the unique identifier'? Are you able to utility registration with the geodatabase? At 10.3 for spatial tables you have the option of registering the table with the geodatabase as Lance mentioned or using the query layer functionality. Since the SDE command line tools have never been geodatabase aware I do not foresee a 100% equivalent replacement to the command line tools. Check this idea out: ArcGIS Idea - Create Views In ArcCatalog Like In SDE Command Line

‎05-05-2015

Mike - I just checked and this defect did not make it into the 10.3.1 release as it was originally slotted for and it is still being investigated. Asrujit stated that you need to contact support and give them your workflow and symptoms. The analyst will then make the determination if your symptoms match this defect and then link you. After this point you can review the status of this defect.

Re: user based schema geodatabase · ‎05-04-2015

I have seen this error before from there being orphaned instance_name listings within the sde.instances table. From the query that Christian had you get the output from I would check to see the specified schemas actually exist in the geodatabase. Partially created user schema geodatabases could be caused from dropping users within the database that own user schema geodatabases leaving orphans entries within the SDE.Instances table. I have also seen this occur from invalid database objects in the SDE user schema prior to using the 'Create Enterprise Geodatabase' tool which causes issues creating new user schemas.... ORA-29900, ORA-06540, and ORA-06553 errors can be associated with this related cause - more detail can be found in KB 37915 in solution section. ----------------------------------------- It is also possible that additional attempts to create new user schema geodatabases will fail but create additional partial/corrupt user schema geodatabases. Are there user schemas that were recently attempted to be created with error or perhaps user schemas in the database that were dropped??

‎04-10-2015

Hi Sean - That KB article (KB40009) has been pulled from external web because it does not apply to all software versions or types of views (depending upon how created) and was not a recommended workflow for database views to be registered with the geodatabase. If you create a view via command line it is no longer possible to register that view with the geodatabase starting at 10.3 (NIM101805). Previous releases would allow this if the view was created via the command line tools. Views that are created using the 'Create database view' tool also cannot be registered with the geodatabase. There are enhancements and Ideas out there on this topic for the ability to be able to register views with the geodatabase in future releases. Please check these out! http://ideas.arcgis.com/ideaView?id=087E00000005A9tIAE ---------------------- Registering a table with the geodatabase – 10.3 http://desktop.arcgis.com/en/desktop/latest/manage-data/geodatabases/registering-a-table-with-the-geodatabase.htm ENH-000086635 - Add functionality to register database views with the geodatabase Note within this link there is a statement about views: Because ArcGIS cannot add an ObjectID field to a view or update the values in an existing ObjectID field in a view, you cannot register a view with the geodatabase.

‎02-27-2015

The patch for 10.1 sp1 that Sean mentions can be found below or 10.2.1 or newer release can be used that includes this fix. ArcGIS 10.1 SP1 for (Desktop, Engine, Server) Quality Improvement Patch | Samples and Utilities

‎02-11-2015

You’ve just updated your client and geodatabases to ArcGIS 10.3, and you want to ensure you are using the most up-to-date ArcSDE command line tools and application server install. So where is the install for ArcSDE 10.3? For the last several releases, we incorporated more functionality into the user interface of the ArcGIS client. For upgrading the geodatabase repository at 10.0, the Upgrade Geodatabase tool replaced the ArcSDE Post Installation wizard. At 10.1, the Create and Enable Enterprise Geodatabase tools allowed for the deprecation of the ArcSDE Post Installation wizard all together. The application server and command line tools have been an optional install since 10.1, and the database connection dialog box was reworked to allow a direct connect for the default method of working with database connections. Overall, these upgrades prepare us for the deprecation of the command line tools and the application server. With the release of ArcGIS 10.3 comes the end of support for the ArcSDE service and the application server connections (three-tier). Additionally, ArcSDE command line tools have been replaced by geoprocessing tools in the ArcGIS clients. Therefore… There is no install for ArcSDE 10.3. You can connect to all of your databases in ArcGIS for Desktop 10.3 using direct connections by adding a database connection in ArcCatalog. You can also use existing SDE files created from application server connections and create application server connections to services from previous versions. Since ArcGIS 10.2.2 is the last release to include the ArcSDE application server, we encourage you to use direct connections moving forward. If you’re wondering what to do about the ArcSDE command line tools no longer being available, geoprocessing tools have been added to the Geodatabase Administration toolset to help you with any administrative needs. So rejoice! There is one less step in the installation process of upgrading to the newest versions of ArcGIS products. For more information, check out our documentation linked below: ArcGIS for Desktop Help: What’s new for Geodatabases in ArcGIS 10.3? ArcGIS for Desktop Help: Client and Geodatabase Compatibility in 10.3 ArcGIS for Desktop Help: Database servers in 10.3 ArcGIS for Desktop Help: Database connections in ArcGIS for Desktop ArcGIS for Desktop Help: Migrate from ArcSDE administration commands Originally posted on the Support Service Blog: Where is the install for ArcSDE 10.3? | Support Services Blog

‎02-09-2015

Nate - To answer part of your post - the 3rd bullet: This bug for the unique identifier prompt has been brought up as a high priority for a fix and is planned for the 10.3.1 currently. This is a major usability defect that many users have been asking for. If you have an association to this defect then please keep track of this and verify when the release date is closer, but I am pretty sure it will make it into the 10.3.1 release. UPDATE to this: This fix did not make it into the 10.3.1 release. NIM085661 - ArcGIS does not set the first not-null field it finds as the unique identifier for a database view.

‎11-18-2014

Thanh - Why are you having issues using the sdeconfig commands at 10.2? Are you having issues with the syntax for this? A note about 10.3: In previous releases of the enterprise geodatabase, the default number of connections allowed was 64. This limit helped prevent overloading the server when all or most connections to the geodatabase were made through an application server running on the same server as the geodatabase. Beginning with 10.3, there is no limitation imposed on the number of connections to new 10.3 geodatabases or geodatabases upgraded to the 10.3 release.

‎10-28-2014

Nate - I am not aware of a method to take database views and register with the geodatabase at 10.3. I do not believe that database views were intentionally allowed to register with the geodatabase. It seems that there is somewhat of a loop hole that allows for this if the view is created with the SDE commandline tools or registered with the commandline (sdelayer -o register) first and then register with geodatabase is available in the client UI. What is your intention or need for the database view to be registered with the geodatabase? The administration reference you are sharing states 'table' and not view. I did find a reference in the 10.0 help regarding registering views with the geodatabase. There is a note within the help document about registering views with the geodatabase ‘Registering a table with the geodatabase’ version 10.0 “Note: Because ArcGIS cannot add an object ID field to a view or update the values in an existing object ID field in a view, you cannot register a view with the geodatabase.” NOTE that registering with the commandline does not also register with the geodatabase as the commandline tools are not geodatabase aware.

‎10-21-2014

Support is investigating some of these cases, so I would recommend you contact Esri Support Services as well as Oracle Support in parallel. Are you able to connect in sqlplus to Oracle and it is just Esri products where you can't connect to Oracle with? Also, is the issue specific to a certain user(s)? eg: Admin and non-admin

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by MelissaJarman

Re: Why could .mxd with no layers store SDE database connections?

Re: Why could .mxd with no layers store SDE database connections?

Re: Turning on/off geoprocessing history via arcpy?

Re: Updating multiversioned view fails

Re: Accessing Your Enterprise Geodatabase Using Python

Re: Life without SDE Command Line

Re: Alternatives to using SDE command line tools - Blog Discussion

Re: user based schema geodatabase

Re: Spatial view metadata

Re: workspace suddenly becomes read-only

Where is the install for ArcSDE 10.3?

Re: Alternatives to using SDE command line tools - Blog Discussion

Re: Alternatives to using SDE command line tools - Blog Discussion

Re: Alternatives to using SDE command line tools - Blog Discussion

Re: Oracle Critical Patch Update - Oct 2014

View properties of database sequences

Re: branch versioning historical moment

UC 2022: Branch Versioning (resources)

Re: REGISTER AS VERSIONED = EDITS TO BASE (GREYED ...

Re: Feature services vs Direct database connection...