Latest Contributions by EugeneYang

Hi, Which entperprise DBMS do you use? Can you post your sde_setup.log file here? Thanks, Eugene ... View more

Can you double check whether this feature class is registered with geodatabase? You can find this out by right-clicking on the feature, and check whehter "Rgister with Geodatabase" is disabled or not. If it is not registered with geodatabase, register it and try edit the metadata again. See if the metadata stays after registration. Eugene ... View more

The Create Enterprise Geodatabase tool requires a ecp file. Please contact ESRI support for instructions on how to get ecp file. After you get the ecp file, there are two options, either clean up the database and re-create the geodatabase, or install ArcSDE command line tool, and then update license with admin command. ... View more

The error message you saw when connecting to a 9.2 geodatabase is misleading. It is actually a known bug. We are fixing this issue at 10.1, and it will return a simple error that this release of geodatabase is no longer supported. Thanks. ... View more

ArcGIS 10.1 can automatically figure out which direct connect driver to use, 10g or 11g, depending on which Oracle client is installed. Oracle9i is no longer supported and ArcGIS 10.1 can not connect to 9.2 geodatabase on Oracle9i. I don't think you can have both ArcGIS 9.3.x and ArcGIS 10.1 on the same machine. Therefore, the particular situation you described would not happen. If you absolutely need to have both Oracle11g and Oracle9i clients on the same machine, just make sure that Oracle11g is the first in the PATH on the ArcGIS 10.1 machine, and Oracle9i cleint is the first in the PATH on the ArcGIS 9.3.x machine. ... View more

We made a special build of 9.2 direct connect driver with 11g at ArcGIS 10. That's why you saw the difference between 9.3.1 and 10. The error message is clearly misleading. we will update the error message at 10.1 Final (NIM071374). Thanks for bringing this up to us. Eugene ... View more

Backward connection to 9.2 geodatabase from ArcGIS 10.1 is not longer supported. We support backward connection up to 3 releases (10.0, 9.3.1 and 9.3), so ArcGIS 10.1 can only connect as far back as 9.3. Thanks Eugene ... View more

Is your database SDE schema or DBO schema? User must have sysadmin role to upgrade geodatabase on SQL Server. We specifically do not allow 'sde' user to upgrade geodatabase even if the 'sde' login has sysadmin privilege. You can try again with a user, other than 'sde', who has sysadmin role, or try as 'sa' user. ... View more

Jon, �??I would like to be able to independently verify the service pack level, using SSMS to "examine the internals of the geodatabase", tables, stored procedures, functions, etc. Is that not possible?�?� Unfortunately, the answer is that it depends on the type of update that�??s being installed. To verify a major release upgrade, such as upgrade to 9.3.1 or 10, you can query the SDE_VERSION table and the GDB_ITEMS table (GDB_RELEASE before 10). These release numbers keep track of geodatabase schema table updates and reflect major release change. However, not all QFEs (which include Service Packs, Hot Fixes and Patches) involve schema table changes.  The majority of changes made in a QFE that require the upgrade to be run are fixes to stored procedures (and ST geometry type on some DBMS).  These stored procedures have their own release numbers.  While you can query the stored procedures through SQL to determine its release, interpreting the release numbers is not straightforward.  This has always been in issue, it�??s not something new at 10.0. We are working on a solution to this in 10.1, a way to query if the geodatabase is at the current release or not and have it reflect all aspects of the geodatabase state (whether there is a major upgrade or a QFE). Until then, the two options listed below are the only supported methods to verify geodatabase upgrade which guarantee that you will get the correct answer: -          Check disable/enable of the upgrade button on geodatabae property dialog -          Use IGeodatabaseRelease.CurrentRelease property in ArcObjects code Thanks Eugene ... View more

Let me start by saying that I�??d like to understand the context for your question.  What is the reason that you need to query if the geodatabase upgrade has been successful?  Is it because another process is dependent on the successful completion of the upgrade?  Is it because you�??ve done this in the past and performing this query is another confirmation the upgrade was successful?  Or, is it a different reason. Whether the Upgrade Geodatabase command and tool are enabled is based several queries, one of which is �??Does the Geodatabase need to be upgraded?�?�.   This query examines the internals of the geodatabase (the collection of tables used for persisting information and a collection of database packages, procedures, functions for executing geodatabase behavior) to determine if it needs to be upgraded.  If either of these two collections (the tables or the database packages, et al) need to be upgraded, then the Upgrade Geodatabase command and tool are enabled. This is a change in behavior at 10.0.  At previous releases we stated that the sdesetup �??o  upgrade command should always be run, whether it needed to or not, after a QFE (Service Pack, Patch or Hot Fix) were applied.  We�??ve changed this behavior to make it clear when you have to run the upgrade command and to try and simplify the upgrade process for all Geodatabases. Determining if the collection of tables makes up the Geodatabase needs to be upgraded is straightforward.  However, determining if the collection of database packages, et al need to be upgraded is not as simple, as there are multiple queries that need to be run to check whether an upgrade is necessary based on the software component updates and the values of the version table, stored procedures and/or geometry type implementation.   Determining what release of the ArcSDE technology that you have has never been a simple process.  Unfortunately, that does not change at 10.0.  As I said at the beginning, understanding what it is you�??re trying to do and why will help me in answering this question. ... View more

The blog post should have been clearer on this. When it says this about SDE verion table, "Within your ArcSDE respository is a table named �??VERSION�?� that contains the major and minor release and the build of the ArcSDE repository in which you are working. An ESRI Support Analyst can work with you to determine which release of the software you are using with the information stated above", the "release of the software" means major release. As you can see when it refers to the Patch Finder, it specifically says "releases, service packs, and patches you have installed". Sorry for the confusion. The method mentioned in my previous reply is a better way verify service pack application. ... View more

The ArcSDE release number in the VERSION table does not always get updated after applying a service pack. It is not an indicator of whether your geodatabase schema was upgraded correctly after applying a service pack. To make sure that you have apply a service pack correctly, you can verify geodatabase upgrade by following steps, 1) Run Patch Finder against your ArcGIS Desktop installation, and verify that the service pack has been applied. 2) In ArcCatalog, make a direct connect to the geodatabase, and go to the Upgrade Status section on the Database Property dialog. If the Upgrade Geodatabase button is disabled, the service pack has been applied correct in your geodatabase schema. Eugene ... View more

Hi, Paul, We need a bit more information to help you on this. 1) can you try this command and get the value of this parameter from your DBTUNE?     sdedbtune -o list -u sde -k DEFAULTS -P XML_IDX_INDEX_TEXT -P ... -i ... If you see its value like this, "TABLESPACE (any_name)", remove the config_string for the   XML_IDX_INDEX_TEXT parameter in the DEFAULTS keyword from the DBTUNE table, and try upgrade again. 2) if it is not the case, please attach your sde_setup.log. It can find it in your system TEMP directory. Thanks Eugene ... View more

Hi, There are significant changes in the implementation of 9.4 geodatabase, therefore pre-9.4 client will not be able to connect to 9.4 server, neither through application serve connection, nor direct connect. Thanks Eugene ... View more

Regarding the original question. If you installed ArcGIS 9.4 beta, you don't need to install any direct connect drivers separately. All the necessary pieces to make backward direct connect to 9.3, 9.3.1, 9.2SP6 are already included. Eugene ... View more