User has a revision set that has 18,956 features in it. After making 3 changes he wanted to discard the results. After selecting the Discard option GM hangs. Processed is killed after 10 minutes and tried again with the features not being displayed and the same result. User installed all the GOOM utilities and made sure everything was working properly.
The solution for this is the making sure three required GM Transaction Mgr columns are included for the modified features view.
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:
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. If you have any workflow that will utilize the
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.