The migration script to clone the existing PEGARULES schema is creating the objects in the default tablespace for the target schema instead of using the assigned tablespaces specified in the DDL for the existing objects in the source schema. Sprint standards are to use separate tablespaces for tables, indexes and LOB's. Can the script be customized to also use the existing tablespace assignments for the PEGARULES objects being cloned?
We can have the DBA clone the source schema to the target schema; however, there is a warning in the update guide...
Note: Pegasystems strongly recommends that you use the migration script. The use of vendor tools
to manage this step is not recommended. If you do not use the migrate script to migrate the schema,
there are additional manual steps required that are not documented here.
What are the "additional manual steps required that are not documented here"?