Creating other required database objects in the destination database

There are some types of database objects that are required for data generation but that Structural cannot create automatically in the destination database.

Before you run data generation, you must add these objects manually to the destination database.

Creating database links

Because some database links require passwords, Structural does not copy database links from the source database to the destination database.

You must create all database links manually in the destination database.

If you do not create the database links, Structural returns warnings and errors.

If Structural creates the destination schema, meaning that either:

• TONIC_ORACLE_SKIP_CREATE_DB is false

• The workspace is configured to override the setting to false

Then Structural does not remove the database links.

Creating scheduler-related objects

Structural also cannot create scheduler-related objects, such as:

• Job classes

• Server attributes, such as EMAIL_SERVER

You must create these manually in the destination database.

If these objects are not present, Structural returns errors.