Tablespace assignment during migration

Question

Hello all,
I've a question about migration workbench: Migration workbench gave two options at the time of repository creation. Local repository or oracle repository. Is it ok to select the local repository instead of the oracle repository? I've tested the migration process multiple times and my idea was to not recreate the repository in oracle each time I test it. I selected the local option during repository creation.
Next, I deleted the <DATABASENAME> default tablespace in oracle model as we already pre-created three tablespaces in oracle: OMWB_DATA, OMWB_INDEX, OMWB_TEMP for the purpose of migration.
I then seleced the two users <DATABASENAME> and omwb_emulation and assigned them the default and temp tablespaces. Default = OMWB_DATA. Temp = OMWB_TEMP.
I just wanted to verify if this is an acceptable way of doing the migration. Because, after the migration is complete, the <DATABASENAME> tablespace has the schema objects but the omwb_emulation tablespace is empty.

Answer 1

The repository which is created at initial launch, is used to store meta data during a migration, and as you say save the state of your "migration project" to relaunch at a later stage. There should be no difference whichever option you choose.
If you capturing the same database over and over again, you can reuse, however if you a migrating different databases, it is better to have a new repository. It doesn't take long to create.
As to choosing of tablespaces etc. By default we will create a tablespace for each database we capture. However there is an option where you can override our default choice and select tablespaces from your targeted database instance. See tools menu. You can then assign schema's to this tablespace, and remove the one we create from the Oracle model.
OMWB_EMULATION, is a schema, that just contains PL/SQL functions etc. to support your migration. You only need this once or not at all (depending on whether your code references those functions) ...
Donal