Showing results for 
Search instead for 
Do you mean 

GeoMedia cannot discard a revision set

by Technical Evangelist on ‎02-22-2016 05:18 AM - edited on ‎04-06-2016 06:24 PM by Moderator (333 Views)


User has a revision set that has 18,956 features in it. User then made 3 changes and wanted to discard the results. When selecting the Discard option GeoMedia locks up. After 10 minutes user tries again with the features not being displayed and the same result. All GOOM utilities are installed and working properly.


Need this workflow to work.

  1. Create Revision Set
  2. Create Display LRM Query (Transportation manger)
  3. Add a route to the Display LRM query
  4. Discard all the revision set changes



The solution for this is making sure three required GM Transaction Mgr columns are included for the modified features view.  See highlighted section in solution below.


A secured feature class has four views that can be used in the GeoMedia environment. These views are optional and their visibility inside GeoMedia is determined by the database administrator.


These views are as follows:


  • Modified Features View (*_MODS)—Shows the features that have been modified.
  • Locked Features View (*_LOCK)—Shows the features that have been locked. The lock view works much the same whether or not the optional three columns are present. The biggest difference is in the query option to include deleted features. This part of the query uses a union with the _MODS view.
  • History View (*_HIST)—Shows all the current and historical features for a particular feature class.
  • Conflict Features View (*_CONF) —Shows the modified features in a revision set that are in conflict with modifications that have been committed to the LIVE state.

Note: If the feature table is secured without adding the three optional GTM columns, the _MODS view will still have LTT_STATUS and LTT_CURRENT_REVSET_ID columns, but LTT_STATUS will be an alias of the WM_OPTYPE column from the _HIST view and LTT_CURRENT_REVSET_ID will be an alias of the REVSET_ID column from the LTT_REVISION_SETS table. Also note that the mode values for LTT_STATUS will represent the mode values from the WM_OPTYPE column, that is, I-Insert, U-Update, D-Delete. GTM handles the different codes internally.  The resulting view is very slow and nearly unusable because the join for the _MODS view is on the revision set name instead of the revision set ID (where t.WM_WORKSPACE = s.REVSET_NAME). The _MODS view will also no longer include the features that are only locked by a revision set, instead it will include the view key defined instead of LTT_FEATURE_ID and the aliases for the LTT_STATUS and LTT_CURRENT_REVSET_ID columns as described above.


The Add GTM columns to table’s check box on the Options dialog box must be checked for you to specify which, if any, of the three columns will be exposed in GeoMedia.