09-23-2019 01:26 AM
Customer is planning an upgrade from GeoMedia v 2015 to GeoMedia v 2018. The database is Oracle 12C. Since its an active production environment, they donot prefer to touch the database, unless its really necessary. Concern is regarding the metadata tables.
Solved! Go to Solution.
09-23-2019 02:43 PM
Concerning GeoMedia Desktop:
It's good that your customer is moving to a supported version of GeoMedia Desktop. The later versions of 2016 (16.0+) GeoMedia Desktop made serveral performance related changes to it's Oracle connection logic (Oracle Data Servers) that were specific to interactions with Oracle 12c.
GeoMedia is very tolerant in observing and understanding it's own metadata tables and fields even if the metadata tables were created back in version 5.0... We highly reccommend howerver that you always use Database Utilities, Create Metadata Tables command to validate and update your GDOSYS schema metadata after upgrading GeoMedia to a newer version. The metadata is not versioned by any attribute that you would find in the database.
You should also be using Database Utilities to routinely clear your modification logs.
See also Help Topic: "Using Database Utilities with the Oracle Spatial Object Model"
where it states concerning the Create Metadata Tables command in Database Utilities:
"Create Metadata Tables—Creates the GDOSYS schema and associated database objects if the schema does not already exist. If the schema already exists, this utility will update the schema to the latest version. This utility can also be used to create any metadata tables that are missing or which have been deleted accidentally. It will also update existing GDOSYS schemas to the current version."
The Help Topic on "The Default GDOSYS Schema Definition" mentions a new GFeatures view that can be used; it can help improve performance for scanning for feature names for Oracle 12c users. The NewGFeaturesView is only created if you run the delivered script (it is not created by running Database Utilities). The Help guide states:
"An alternate GFEATURES view definition is delivered in the ...\Common Files\Intergraph\GeoMedia\Scripts folder (NewGFeaturesView.sql). This view definition can improve query performance for GFEATURES, particularly for the GeoMedia Transportation products. The new view is not required. A corresponding script (RevertGFeaturesView.sql) is also provided. A user with DBA privileges is required to run these scripts."
The following statement is from the GOOM Quick Reference.pdf that is delivered with the GOOM package:
As new versions of GeoMedia applications are released, there may be changes to the GDOSYS schema definition. Basic changes are incorporated into Database Utilities which can be used to update GDOSYS as new releases come out. Whenever you get a new release of GeoMedia, you should perform the following steps:
1. Go to Start>>GeoMedia Professional>>Utilities>>
Database Utilities to access this utility.
2. Set the Database type: Oracle Object Model
3. Connect as a DBA user like SYSTEM.
4. To update the GDOSYS metadata schema, select the
Create Metadata Tables button.
5. Since GDOSYS already exists, the process will check the
existing metadata and update it if required. You will be
notified whether or not an update occurs. The same process can be used to repair GDOSYS metadata if there are missing tables. This will not repopulate any of the tables but will add them back to the structure as needed.
Note: Despite what is written in the GOOM Help, we no longer supply any UpdateGDOSYS.sql script. You should use GeoMedia's Database Utilities, Create Metadata Tables to validate and update GeoMedia GDOSYS metadata.