|Oracle® Warehouse Builder User's Guide
10g Release 2 (10.2.0.2)
Part Number B28223-05
For optimum performance and manageability, Transportable Modules help design the preprocessing, and ensure fast replication and loading of enterprise data. This chapter contains the following topics:
Oracle Warehouse Builder enables you to build and publish enterprise data warehouses in stages. Similar to the partitioning strategy, creating a data warehouse in stages by following a compartmentalization strategy potentially maximizes both performance and manageability.
Due to the processing overhead and network delays, Warehouse Builder mappings that access remote data through database links can run several magnitudes more slowly than if data were accessed locally. In this case, consider the following two options for speeding up the process:
Create a Warehouse Builder Transportable Module to copy remote objects (tables, views, materialized views, and so on) from a source database into a target database at very fast speed. The mappings in the target data warehouse can then access data locally.
Data can be partially processed in source database (to benefit from the local access performance), and then the preprocessed data can be copied, using a Transportable Module, from source to target database for final loading into the data warehouse.
For both strategies, a Transportable Module functions like a shipping service that moves a package of objects from one site to another at the fastest possible speed.
Note:The use of transportable modules requires the Warehouse Builder Enterprise ETL Option.
The fundamental functionality of a Transportable Module is to copy a group of related database objects from one database to another using the fastest possible mechanisms.
Using the Warehouse Builder designer, a Warehouse Builder you first create a Transportable Module, and specify the source database location and the target database location. Then you select the database objects to be included in the Transportable Module. The metadata of the selected objects are imported from the source database into the Transportable Module and stored in the Warehouse Builder design-time repository. To actually move the data and metadata from source into target, you need to configure the Transportable Module, and deploy it to the target location. At the deployment time, both data and metadata are extracted from the source database and created in the target database.
In the current release, the implementation of the data and metadata movement is accomplished through a combination of Oracle Data Pump, Transportable Tablespace, DBMS_FILE_TRANSFER, binary FTP, local file copy, and Warehouse Builder code generation and deployment. Warehouse Builder users can configure Transportable Modules to influence what implementation technologies will be invoked. As the server technology progresses, faster implementation methods will be added in future releases.
In the current release the following source objects can be added into Transportable Modules:
External Tables (including their data)
Varrying Array Types
Nested Table Types
More object types will be available as the technology advances in the future.
The Transportable Modules technology opens a new possibility for building an enterprise wide data warehouse in stages, which offers huge potentials for high performance and manageability. As shown in Figure 23-1, the traditional ETL process extracts data from remote databases through multiple remote accesses using database links.
Figure 23-1 Extraction of data from remote databases through multiple remote accesses using database links
Remote accesses using database links suffer significant performance degradation due to serial queries and serial DMLs, plus the network latencies. The performance degradation will appear more wasteful if same source tables are accessed multiple times.
The Transportable Modules technology works as shown in Figure 23-2. In this new architecture, all the source objects needed by the mappings are bundled together and moved to target through just one deployment. The OWB TM Deployment uses fast Oracle Data Pump, FTP, and Oracle TTS to achieve very high transportation performance. And this transportation absorbs the cost of the network delays just once. After that, mappings access data locally, which can easily benefit from parallel queries and parallel DMLs. And repeated accesses to the same data increase the performance benefit of Transportable Modules.
Figure 23-2 Warehouse Builder Transportable Modules Deployment
Using the Transportable Modules, data warehouse loadings become more manageable because the source database only needs to be shut down for a short period of time in order for Warehouse Builder Transportable Module to complete the deployment. Users of the source database do not have to wait until the entire data is loaded into the data warehouse. For example, if you are using the transportable tablespace implementation, Warehouse Builder Transportable Modules can copy a tablespace of 20 GB in about five minutes, resulting in a down time of five minutes in the source database.
Data copied into the target database is a snapshot of what was in the source database. This fact can be utilized to create a data versioning mechanism. More advanced Oracle users may create streams on the transported tables for capturing real-time changes from the source. The transported tables may also be exchanged into larger tables as a partition.
Finally, in a multi-departmental enterprise environment, the target database as shown in Figure 23-2 may actually be an Operational Data Store that serves some intermediate reporting and updating purposes, but is still not the final data warehouse yet. This target could in turn serve as a source to the next stage of data collection. The Transportable Modules technology can be repeatedly applied, all the way till the data is finally collected in the data warehouse.
Transportable Modules can also be used for publishing data marts. A data mart is normally a portion of a larger data warehouse for single subject or single departmental access. At times, creating a data mart amounts to copying what has already been collected and processed in the data warehouse. A Warehouse Builder Transportable Module can be created to perform this task, as shown in Figure 23-3. The figure also shows that the same Transportable Module can be used to deploy a data mart to multiple locations.
Figure 23-3 Data Marts in a Data Warehouse
Since a Warehouse Builder Transportable Module deploys a snapshot of the source database objects, the deployment time (tracked by Warehouse Builder runtime deployment service) can serve as the version of the data marts.
Transportable modules work by leveraging technology in Warehouse Builder plus technology in the Oracle Database. A transportable module replicates parts of a source database into a target database. The parts of the source database that can be replicated include tablespaces, tables, indexes, constraints, and other relational objects.
How the Oracle Database replicates the tablespace depends on the database version. When you transport between two 8i databases or between two 9i databases, the database invokes the Oracle transportable tablespaces functionality. When you transport between two Oracle 10g databases, the database invokes the Oracle data pump functionality.
In the case of 10g databases and Oracle data pump, you can transport tables without also transporting their tablespaces. For example, if your table is 100KB and its tablespace size is 10MB, you can deploy the table without deploying the entire tablespace. Furthermore, only Data Pump gives you the option to copy the entire schema. For 10g databases, you specify either data pump or transportable tablespaces during configuration as described in "Configuring a Transportable Module".
For more information about transportable tablespaces and data pump, see the Oracle Database 10g documentation.
Prior to the introduction of transportable modules, the most scalable data transportation mechanisms relied on moving flat files containing raw data. These mechanisms required that data be unloaded or exported into files from the source database, and then these files were loaded or imported into the target database. Transportable modules entirely bypass the unload and reload steps and gives you access to the Oracle server technologies Transportable Tablespaces and Data Pump.
High Performance Data Extraction
Transportable modules reduce the need for Warehouse Builder mappings to access data remotely. If you have large volumes of data on remote machines, use transportable modules to quickly replicate the sources onto the Oracle target database. Warehouse Builder mappings can then directly access a local copy of the data. Also, because the source is now part of the target, you can perform the ETL operations directly on the source data.
Distribute and Archive Datamarts
Normally a central data warehouse handles ETL processing while dependent data marts are read-only. You can use transportable modules to copy from a read-only data mart to multiple departmental databases. In this way, you can use your central data warehouse to periodically publish new datamarts and then replace old datamarts simply by dropping the old tablespace and importing a new one. This rapid duplication and distribution also enables you to publish and distribute a datamart for daily analytical or business operations.
You can set your source tablespaces to read-only mode and then export them to a target. All the data files are copied creating a consistent snapshot of the source database at a given time. This copy can then be archived. The advantage of this method is that archived data is restorable both in the source and target databases.
Before You Begin
Ensure that you can connect to source and target databases as a user with the necessary roles and privileges as described in Roles and Privileges Required for Using Transportable Modules.
Ensure that your organization has licensed the Warehouse Builder Enterprise ETL Option.
To use transportable modules in Warehouse Builder, refer to the following sections:
Note to Database Administrators: Step 1 of these instructions require some powerful database roles and privileges. And step 3 requires knowledge of schema passwords. Depending on your preference, you can allow Warehouse Builder developers to complete step 3 or restrict it to database administrators only.
Be sure to successfully test these connections before proceeding to the next step.
When creating a Transportable Module source location, the source location user must possess specific roles and/or privileges depending on the version of the source database.
If the source database is prior to Oracle Database 10g, the SYSDBA role is required of the source location user.
If the source database is Oracle Database 10g, the SYSDBA is not required, but the following must be assigned to the source location user.
ALTER TABLESPACE privilege
When creating a Transportable Module target location, the target location user must possess specific roles and/or privileges depending on the version of the target database.
If the target database is prior to Oracle Database 10g, the SYSDBA role is required of the target location user.
If the target database is Oracle Database 10g, the SYSDBA role is not required but the following must be assigned to the target location user.
CONNECT role with admin option
RESOURCE role with admin option
ALTER TABLESPACE privilege
EXECUTE_CATALOG_ROLE with admin option
CREATE MATERIALIZED VIEW privilege with admin option
CREATE ANY DIRECTORY privilege
Note:Transportable Module source and target location users need to be assigned many powerful roles and privileges in order for the Transportable Modules to read objects from the source database and for creating objects in the target database. In a production environment, if necessary, the DBA may choose to create the Transportable Module source and target locations (using the Warehouse Builder Connection Explorer) for the data warehouse developers, and conceal the passwords.
The following is a SQL script for DBA to assign source location users the required roles and privileges in the source database.
grant connect to <TM src location user>;
grant exp_full_database,alter tablespace to <TM src location user>;
The following is a SQL script for DBA to assign target location users the required roles and privileges in the target database.
grant connect,resource to <TM tgt location user> with admin option;
grant imp_full_database,alter tablespace to <TM tgt location user>;
grant execute_catalog_role to <TM tgt location user> with admin option;
grant create materialized view to <TM tgt location user> with admin option;
grant create any directory to <TM tgt location user>;
Before you create a transportable module in Warehouse Builder, first define its source and target locations in the Connection Explorer. Each transportable module can have only one source and one target location.
To specify a transportable module location:
From the Connection Explorer, expand the Locations node.
Expand the Databases node.
Right-click either the Transportable Modules Source Locations or Transportable Modules Target Locations node and select New.
Warehouse Builder displays a dialog for specifying the connection information for the source or target location.
The instructions for defining source and target locations are the same except that you do not specify optional FTP connection details for targets. Follow the instructions in "Transportable Module Source Location Information" to specify the connection information and then test the connection.
Warehouse Builder first uses this connection information to import metadata for the transportable module from your source machine into the Warehouse Builder repository. Then at deployment, Warehouse Builder uses the connection information to move data from the source to the target.
A name for the location of the source or target database.
An optional description for the location.
Warehouse Builder uses the database user name and password to retrieve the metadata of the source objects you want to include in your transportable module. Warehouse Builder also uses this information during deployment to perform transportable tablespace or data pump operations.
To access databases for use with transportable modules, ensure that the user has the necessary database roles and privileges as described in Roles and Privileges Required for Using Transportable Modules.
Host name of the machine where the database is located.
Port number of the machine.
Service name of the machine.
Choose the Oracle Database version from the list.
FTP Username/Password (optional)
Specify an FTP credential if you intend to invoke Oracle Transportable Tablespace as the mechanism for transporting data. If you do not plan to configure the Transportable Tablespace mechanism, the FTP credential is not required.
Even in the case that you will configure to use the Transportable Tablespace, but both source and target databases are located in the same machine, or both source and target machines can access shared disk volumes (which, for instance, is made possible by NFS), you can leave the FTP credential blank. Without the FTP credential, Warehouse Builder will try to perform plain copy of the source files from source directory to target directory.
Click Test Connection to validate the connection information. Warehouse Builder attempts to connect to the source database and, if applicable, to the FTP service on the source machine. Warehouse Builder displays a success message only after it validates both credentials.
To create a transportable module:
From the Project Explorer, expand the Databases node.
Right-click the Transportable Modules node and select New.
The Create Transportable Module Welcome page is displayed.
Use the wizard to complete the following tasks:
In the Name and Description page, type a name and optional description for the transportable module.
Although you can create a new source location from the wizard page, it is recommended that you define locations for transportable modules before launching the wizard as described in "Transportable Module Source Location Information"
When you select an existing location, the wizard tests the connection and does not allow you to proceed with the wizard until you specify a location with a valid connection.
Select a target location from the list at the left of the wizard page. If no target locations are displayed, click New and define a target location as described in "Transportable Module Source Location Information".
Use the Define Contents page to select tablespaces and schema objects to include in the transportable module. In the left panel, Available Database Objects lists all source tablespaces, schemas, and available schema objects. In the right panel, Selected Database Objects displays the objects after you select and shuttle them over.
Expand the tablespaces by clicking the tree node to display the schemas in each tablespace and the objects in each schema. Non-tablespace schema objects such as views and sequences are also listed under their respective schema owners, even though these objects are not stored in the tablespace. To select multiple objects at the same time, hold down the Ctrl key while selecting them. You can include the following types of objects in transportable modules:
PL/SQL Functions, Procedures, and Packages
Object Types, Varray Types, and Nested Tables Types
Select the tablespaces and schema objects from the Available Database Objects field and click the arrow buttons in the center to shuttle the objects to the Selected Database Objects field.
Because source databases typically contain multiple schemas and a large number of objects, there are several tools to assist you in finding and selecting objects. You can view the number of data files and their total size by placing your mouse over a node. The wizard displays the information in a pop up as shown in Figure 23-4.
Figure 23-4 Viewing the Number of Data files and Total Size
Double-click the flashlight icon to find source data objects by type or name. In the Object field, type a name or a letter by which to filter your search. From the Type list, indicate the object type you are searching. Check the appropriate box to perform the search by name or by description.
For example, type 'T%' in the Object field, select tablespaces from the Type field, and click Find Next. The cursor on the Available Database Objects navigation tree selects the name of the first tablespace that starts with a 'T'. If that is not the tablespace you want to select, then click Find Next to find the next tablespace. During this searching process, the navigation tree expands all the schema names and displays all the tablespaces.
As shown in Figure 23-5, you can double-click a schema node or any of the nodes in the schema to type in a filter pattern. For example, if you type T% and click OK, the navigation tree displays only those objects that start with the letter T.
Figure 23-5 Schema Node Selected on Define Contents Page
If you select items that cannot be included in a transportable module, Warehouse Builder returns a dialog describing which items cannot be included and why.
Figure 23-6 Import Filter Dialog
After Warehouse Builder creates the transportable module in your repository, you can locate it on the Project Explorer under the Transportable Modules node. Expand the tree to display the imported definitions.
Warehouse Builder creates separate modules for the separate schemas. The schema names on the Project Explorer mirror the schema names in your source database.
Since the objects contained in a transportable module mirror the source database, you cannot edit these objects using this user interface. If the source database changes, you can re-import the objects. If you want to delete objects from the transportable module, right-click the object and select Delete. This action deletes the object from the definition of the transportable module but does not affect the underlying source database.
For most use cases, you can accept the default settings for all the configuration properties with the exception of the Password setting. You must specify a password for each target schema. If the schema already exists in the target, specify an existing password. If the schema does not already exist, Warehouse Builder can create the schema with the password you provide.
Depending on your company security polices, knowledge of schema passwords may be restricted to database administrators only. In that case, the database administrator must specify the password for each schema. Alternatively, developers can define new passwords for new schemas if the target has no existing schemas that match source schemas.
Set the following runtime properties for the transportable module:
Target OS Type
Select the type of operating system type for the target. For versions prior to Oracle Database 10g, the type of operating system on the target machine must be the same as the source machine. For versions Oracle Database 10g or higher, you can deploy to any operating system from any operating system.
You should create a directory on the target machine dedicated for the deployment of transportable modules. This dedicated directory stores files generated at runtime including temporary files, scripts, log files, and transportable tablespace data files. If you do not create a dedicated directory and type its full path as the Work Directory, Warehouse Builder saves the generated files under the runtime home directory.
What to Deploy
Warehouse Builder enables you to select whether you want to deploy only the tables in your transportable module or all the related catalog objects, such as views and sequences, as well. Select TABLES_ONLY if you want to deploy only tables otherwise select ALL_OBJECTS.
Use the TABLES_ONLY option to refresh the data in a transportable module. If you previously deployed a transportable module with the ALL_OBJECTS option and want to replace only the tablespace from the same source, redeploy the transportable module with the TABLES_ONLY option. The deployment drops the existing tablespace in the target, inserts the new one, and then recompiles the previously deployed metadata.
Similarly, if you previously deployed the Transportable Module using Data Pump, then the redeployment will only modify the tables in the Transportable Module.
By default, this setting is enabled and Warehouse Builder transports the tablespaces. If you enable this setting, also specify the settings under Target DataFile Configuration Properties.
If both the source and target databases are Oracle 10g or higher, consider disabling this setting. For example, if your table is 100KB and its tablespace size is 10MB, you can deploy the table without deploying the entire tablespace. When you disable Transport Tablespace, Warehouse Builder utilizes Oracle Data Pump to deploy the table and you can set the Table Exists Action setting.
Note also that if source or target location is not Oracle Database 10g, the Transport Tablespace option is selected by default. In that case, Transportable Tablespace is the only implementation method for data movement. If both source and target locations are Oracle Database 10g, then you can deselect Transport Tablespace and therefore utilize Data Pump.
In the case that Transport Tablespace is selected, there are further restrictions, depending on the versions of the source and target locations, as described in Table 23-1. When planning for data replications, take these restrictions into consideration. In general, Oracle10g, particularly Oracle10g Release 2, is the preferred target database.
Table 23-1 Requirements for Replicating Data Between Database Versions
|Source location||Target location|
Targeting another Oracle 10g location requires both databases must have the same character set and the same national character set.
Targeting an Oracle8i or 9i location is not possible.
Targeting an Oracle9i or 10g location requires both databases must have the same character set, the same national character set, and both databases must be on the same operating system platform.
Targeting an Oracle8i or 9i location is not possible.
Targeting an Oracle8i, 9i, or 10g requires all of the following:
Both source and target databases must have the same character set.
Both source and target databases must have the same national character set.
Both source and target databases must be on the same operating system platform.
Both source and target databases must have the same block size.
Cannot change schema names during transporting tablespaces.
Cannot change tablespace names during transporting tablespaces.
Targeting another Oracle10g location requires both databases must have the same character set and the same national character set.
Targeting an Oracle8i or 9i location is not possible.
Set the following schema properties for the transportable module:
Target Schema Name
This property enables you to change the name of the source schema when it is deployed to the target. Select the DEFAULT or click the Ellipsis button to type the new name for your schema in the target and click OK. For example, you can change SCOTT to SCOTT1.
For existing schemas, type a valid password for the schema. For schemas to be created, Warehouse Builder creates the schema with the password you provide.
Specify the default tablespace to be used when Warehouse Builder creates the target schema. If you leave this setting blank, Warehouse Builder uses the default specified by the target.
Schema Exists Action
Specify what action Warehouse Builder should take if the schema already exists in the target. The default value is skip.
Schema Doesn't Exist Action
Specify what action Warehouse Builder should take if the schema does not already exist in the target. The default value is create.
Table Exists Action
When Transport Tablespace is disabled, use this property to specify what action Warehouse Builder should take if the table already exists in the target. Default value is skip.
Copy Source Schema
When you use data pump by deselecting Transport Tablespace, you can select this option to copy the entire source schema into the target.
When you use data pump by deselecting Transport Tablespace, specify the maximum number of processes for the Oracle Database to use to execute the transfer of data.
You need to set the following data file properties for the transportable module:
Indicate the directory where you want the data file to be stored on your target machine. If you leave the directory unspecified, Warehouse Builder stores the data file in the Work Directory.
Specify the name of the data file to be created in the target machine. You can use this parameter to rename the data file. Accept the DEFAULT to persist the data file name from the source database or click the Ellipsis button to type a new name for the datafile and click OK.
If this parameter is selected, Warehouse Builder overwrites the existing data file. Else, Warehouse Builder aborts the deployment if it finds an existing data file.
When you enable Transport Tablespace, set the following tablespace properties for the transportable module:
If you are using an Oracle Database version prior to 10g, then the target tablespace name must be the same as your source tablespace name. For such cases, this field is read-only. If a tablespace with the same name already exists in your target database, then the runtime operation will first drop the existing tablespace and replace it with the new one.
If you are using Oracle Database version 10g or higher, then you can change the target tablespace name.
Drop Existing Tablespace
If this setting is selected, Warehouse Builder drops and then recreates the existing tablespace in target. By default, this setting is not selected and prevents you from deleting the tablespace in the target in the event that the tablespace with the same name already exists. In this case, the deployment process stops with an error.
When you deploy a transportable module, the Control Center displays the transportable module as including all the tables while the other catalog objects such as views are displayed separately. When you select a deploy action for the transportable module, the Control Center sets the associated catalog objects to the same deploy action.
During deployment of a Transportable Module, there are two ways for users to monitor the deployment progress. The first way is by the use of the "Job Details" window, as shown in Figure 23-7. The status line is instantly refreshed with the most up-to-date status. And the message box immediately above the status line shows all the messages logged so far.
Figure 23-7 The Job Details Window
Another way of observing the progress is by watching the log file that the Transportable Module deployment process generates. The Transportable module log file is created in the "Work Directory" that the user has configured. The name of the file is always <The TM Name>.log, for example TM1.log if the name of the Transportable Module is TM1. This file is a plain text file containing the same messages that you can see in the message box in the Job Details window. Example 23-1 shows the contents of a Transportable Module log file.
Currently there are a total of 16 steps. Some steps may be skipped depending on the user configurations, and some steps may contain error messages that Transportable Module considers ignorable, such as failures in creating referential constraints due to referenced tables not found errors. This log file contains important information. It must be carefully examined during and after the Transportable Module deployment completes.
Example 23-1 Log file containing important information
step1 begin: making connection to target db ... step1 end: connected to target Target ORACLE_HOME = /data/oracle/ora1010 step2 begin: making connection to source db... step2 end: skipped. step3 begin: making source tablespaces read only... step3 end: skipped. step4 begin: exporting tts... step4 end: skipped. step 5 begin: checking for existing datafiles on target... step5 end: skipped. step 6 begin: drop existing tablespaces step6 end: skipped. step7 begin: transporting datafiles... step7 end: skipped. step8 begin: managing schemas/users ... step8 end: completed setting up target schemas step9 begin: drop non-table schema objects... step9 end: nothing to drop. step10 begin: converting datafiles... step10 end: skipped. step 11 begin: importing tts ... find or create a useable dblink to source. step11 end: importing tts is not requested by user. step 11 end: import tts is successful step 12 begin: restore source tablespaces original status ... step12 end: skipped. step13 end: skipped. step14 begin: non-tts import ... Import: Release 10.1.0.4.0 - Production on Tuesday, 04 April, 2006 10:43 Copyright (c) 2003, Oracle. All rights reserved. Username: Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - Production With the Partitioning, OLAP and Data Mining options Starting "TMTGT_U"."SYS_IMPORT_TABLE_02": TMTGTU/********@(DESCRIPTION=(ADDRESS=(HOST=LOCALHOST)(PROTOCOL=tcp)(PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=ORA1010.US.ORACLE.COM))) parfile=/home/ygong/tmdir/TM1_imptts.par Estimate in progress using BLOCKS method... Processing object type TABLE_EXPORT/TABLE/TBL_TABLE_DATA/TABLE/TABLE_DATA Total estimation using BLOCKS method: 64 KB Processing object type TABLE_EXPORT/TABLE/TABLE . . imported "TMU1"."TA" 2 rows Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT ORA-39083: Object type REF_CONSTRAINT failed to create with error: ORA-00942: table or view does not exist Failing sql is: ALTER TABLE "TMU1"."TA" ADD CONSTRAINT "TA_T1_FK" FOREIGN KEY ("C") REFERENCES "TMU1"."T1" ("C") ENABLE Job "TMTGT_U"."SYS_IMPORT_TABLE_02" completed with 1 error(s) at 10:44 step14: import has failures. step14 end: non-tts import completed with warnings step15 end: create flat file directories skipped. step16 end: transporting flat files skipped.
Once you successfully deploy a transportable module, you can use the objects in the transportable module in ETL designs. When you add source and target operator to the mapping as described in "Adding Operators that Bind to Repository Objects", you can select objects from the transportable module folder.
You can edit a transportable module by right-clicking the name of transportable module from the Warehouse Builder Project Explorer and selecting Open Editor from the pop-up menu. Warehouse Builder displays the Edit Transportable Module dialog containing four tabs.
Warehouse Builder uses this connection information to access the source machine and import the metadata into its repository. Warehouse Builder also uses this information during runtime to move the tablespace data from the source to the target.
The Source Database tab is read-only. Once you have imported tablespace definitions from a source machine, you cannot change the location information.
The Tablespaces tab displays the tablespaces to be transported and their size. This tab is read-only. You can also view the tablespace size for individual data files in a tablespace. For details, see "Viewing Tablespace Properties".
Displays the available and selected target locations. You can move a location from Available Locations to Selected Locations, or configure a new location.
You can view the properties of a tablespace by right-clicking the name of tablespace from the Warehouse Builder Project Explorer and selecting Open Editor from the pop-up menu. Warehouse Builder opens the Edit Tablespace. This property sheet displays the size of individual data files in a tablespace.
If your source data has changed since you last created a transportable module in Warehouse Builder, you can reimport the metadata to update your repository definitions. When you open the reimport dialog, Warehouse Builder remembers the source location you specified while creating the transportable module and directly displays your source objects.
To reimport transportable module definitions:
From the Warehouse Builder Project Explorer, right-click the Transportable Modules name and select Reimport.
The Recreate Transportable Module dialog is displayed.
From the Available Database Objects column, select the objects you want to reimport.
The database objects that have been previously imported into the repository are listed in bold. You can also choose to import new definitions.
Use the arrow buttons to shuttle the objects to the Selected Database Objects column and click OK.
Warehouse Builder reimports existing definitions and creates new ones. The Transportable Module reflects the changes and updates after the reimport is completed.