Configuring whether Structural creates the destination database schema

By default, during each data generation job, Structural creates the database schema for the destination database tables, then populates the database tables based on the workspace configuration.

If you prefer to manage the destination database schema yourself, then set the environment setting TONIC_ORACLE_SKIP_CREATE_DB to true. You can add this setting manually to the Environment Settings list on Structural Settings.

You can override this setting manually in individual workspaces. For more information, go to Advanced workspace overrides.

What happens when TONIC_ORACLE_SKIP_CREATE_DB is true?

When TONIC_ORACLE_SKIP_CREATE_DB is true, or the workspace overrides the setting to true, then Structural does not create the destination database schema. Before you run data generation, you must create the destination database with the full schema.

During data generation, Structural deletes the data from the destination database tables, except in the following cases:

• Tables that use Preserve Destination mode.

• Upsert data generation.

It then populates the tables with the new destination data.

Effect on required source and destination user privileges

For the source user, if Structural does not create the destination schema, then the source user must also have EXECUTE ON privileges for the DBMS_METADATA package.

The setting also affects the required privileges for the destination user.