2.10 Moving the Spatial Studio Metadata Schema

You can move your Spatial Studio metadata schema from one database to another.

Perform the steps in the following sections to move your Spatial Studio metadata schema to a different database:

2.10.1 Moving or Copying the Metadata Tables

You must first move or copy the following metadata tables from your current database to the new database:

SGTECH_SYS_TYPE
SGTECH_SYS_JSON_SCHEMA
SGTECH_OBJECT
SGTECH_OBJECT_RESOURCE
SGTECH_TASK_QUEUE
SGTECH_TASK_BROKER
SGTECH_REPOCHANGELOG
SGTECH_REPOCHANGELOG_LOCK
You can use one of the following methods to move or copy the preceding Spatial Studio metadata tables:
  • Use Oracle Data Pump to transfer the metadata schema objects to a different database. See Oracle Data Pump in Oracle Database Utilities for more information.
  • Manually copy the metadata schema objects to the new database. The Database Copy feature in Oracle SQL Developer is useful for this option. See Database Copy in Oracle SQL Developer User's Guide for more information.

    When copying manually, the metadata MUST be copied in the order as shown in the preceding list.

2.10.2 Connecting Spatial Studio to the Relocated Metadata Schema

After Moving or Copying the Metadata Tables, perform the following steps to reconnect your existing Spatial Studio instance to the newly relocated metadata schema.
  1. Rename the Spatial Studio configuration file (~/.sgtech/sgtech_config.json) to sgtech_config.backup.
  2. Start Spatial Studio.
    This will generate a new Spatial Studio configuration file (default location is ~/.sgtech/sgtech_config.json).
  3. Stop Spatial Studio after confirming that the new configuration file is generated.
  4. Open sgtech_config.backup, copy the value of the tag master_seed, and paste to replace this value in the new configuration file.
  5. Start Spatial Studio.
  6. Login to Spatial Studio and provide the credentials for the metadata schema in the new database.