|
Oracle® Migration Workbench User's Guide
Release 10.1.0 for Microsoft Windows 98/2000/NT/XP and Linux x86 Part No. B15857-01 |
|
 Previous |
 Next |
|
Oracle® Migration Workbench User's Guide
Release 10.1.0 for Microsoft Windows 98/2000/NT/XP and Linux x86 Part No. B15857-01 |
|
|
Previous |
Next |
This chapter describes how to create and customize the Oracle Model. It contains the following sections:
This chapter assumes that you have already captured the source database using the procedure described in Chapter 4, "Capturing a Source Database".
Before migrating a third-party database, you must create the Oracle Model. The Oracle Model is a representation of the structure of the destination database. Migration Workbench creates the Oracle Model using the information from the Source Model. This chapter describes how to create and customize the Oracle Model. For information about loading the Source Model, see Chapter 4, "Capturing a Source Database".
To get the best results from the migrated database, you can customize the Oracle Model to use specific features of Oracle databases, such as multiple tablespaces. However, if you are not an experienced Oracle database administrator, Oracle recommends that you create the Oracle Model and proceed directly to migrating the database as described in Chapter 6, "Migrating the Database".
The following figure shows this process in the context of the overall migration process:
|
Note: If you chose to automatically create the Oracle Model while running the Capture wizard, you can skip this section. For more information about automatically creating the Oracle Model, see "Using the Capture Wizard". |
To create the Oracle Model:
From the Action menu, select Create Oracle Model.
If you have already created the Oracle Model, you are prompted to confirm that you want to create the Oracle Model again. Click Yes to continue.
Review the messages on the progress screen.
If error messages with the prefix Parse Exception are listed in the progress screen, use the procedure described in "Correcting Errors in the Oracle Model" to correct these errors.
Fix any other errors and warnings, as required and compete steps 1 to 3 again.
If error messages with the prefix Parse Exception are listed in the progress screen, the associated schema objects do not appear in the Oracle Model. To complete the Oracle Model:
Note the Source Model schema object that caused the error.
Select that schema object in the Source Model.
Inspect the properties on the schema object in the Source Model for possible causes of the error.
Modify a property of the schema object in the Source Model.
For example you might comment out one line of a stored procedure. For information about manipulating Source Model schema objects, see "Customizing the Source Model".
From the Object menu, select Parse.
|
Note: The Parse option is available only after creating the Oracle Model. |
Migration Workbench attempts to create the Oracle Model schema object from the Source Model schema object.
A progress screen appears.
If the error appears again, repeat steps 2 to 5.
If necessary, comment out all the schema object's editable properties. This ensures that a schema object is created in the Oracle Model, and therefore in the destination database. The migrated schema object will not function as expected but acts as a placeholder so that you can create an equivalent Oracle schema object with the correct functionality.
You can customize the Oracle Model to take advantage of Oracle features identified during the planning phase.
This section describes how to make the following changes to the Oracle Model:
To modify properties of a schema object in the Oracle Model:
Click on the Oracle Model tab of Migration Workbench.
The Oracle Model is displayed.
Expand the Oracle Model tree and select the schema object that you want to modify.
Modify the properties of the schema object as required.
For a detailed description about each schema object and the properties associated with that schema object, see the online help.
To change the tablespace storage property of an index or table to an existing tablespace, when that tablespace is not listed in the available tablespaces, complete the procedure described in "Using Existing Tablespaces".
An Oracle database consists of one or more logical storage units called tablespaces, which collectively store all of the database's data. For more information about tablespaces, see the Oracle Concepts guide.
If you are not satisfied with the default tablespace settings in Migration Workbench, you may want to create or rename a tablespace or reassign objects to existing tablespaces as described in this section.
Migration Workbench automatically creates a tablespace when it creates the Oracle Model. To prevent this functionality, deselect the Automatically Create Tablespaces During Oracle Model Creation option on the General page of the Options dialog box.
If you create a tablespace using Oracle Enterprise Manager, you must use the procedure described in "Using Existing Tablespaces" to populate the tablespace lists on the schema object property sheets.
To create a tablespace manually using Migration Workbench:
Select the Tablespaces node from the Oracle Model tree.
From the Object menu, select Create.
The Create Tablespace screen appears.
Enter a name for the Tablespace in the Name field.
Click Create.
Migration Workbench creates the tablespace with the following default settings:
CREATE TABLESPACE tablespace_name LOGGING DATAFILE 'tablespace_name.dbf' SIZE 100M REUSE AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITED
For more information about creating or altering tablespaces, see the Oracle SQL Reference Guide.
To rename a tablespace using Migration Workbench:
Select the Tablespace from the Oracle Model tree.
Choose Object > Rename.
Edit tablespace_name in the data definition language (DDL) statement.
Click Apply.
|
Note: When you rename a tablespace, all users, tables and indexes that use that tablespace are updated with the new tablespace name. |
For more information about altering tablespaces, see Oracle SQL Reference Guide.
To use an existing tablespace in the destination database as the default tablespace for all users and schema objects in the Oracle Model:
From the Tools menu, select Tablespace Discoverer.
When prompted, provide the following information for the destination database:
Enter the user name of a user with CONNECT and RESOURCE roles in the Username field.
Enter the password in the Password field.
Enter the appropriate values in the Host, Port, and SID fields.
For information about determining the correct values for these fields, see "Determining Connection Information for an Oracle Database".
Click Connect.
The Default Tablespace, Index Tablespace and Temporary Tablespace fields become enabled.
In the Default Tablespace field, select a default tablespace location for all users and tables in the Oracle Model from the drop-down list of available tablespaces.
In the Index Tablespace field, select a default tablespace location for all indexes in the Oracle Model from the drop-down list of available tablespaces.
In the Temporary Tablespace field, select a default location for temporary storage for all users in the Oracle Model.
Click Apply.
|
Note: You can modify the tablespace for individual schema objects, such as users, indexes, and tables, by selecting that schema object from the Oracle Model tree. |
All users in the Oracle Model are allocated the password oracle because Migration Workbench cannot decrypt passwords from source databases. If you do not change this password, the password for all users in the destination database will also be oracle. If you want to change the password for a user, select that user in the Oracle Model and change the password to the value you require in the User property sheet.
