

The source and target databases must have the same character set.

The source and target databases must have the same database block size. The source and target databases must be on the same type of hardware and operating-system platform. The two databases do not have to be on the same release. The transportable set must be self-contained.Ī tablespace with the same name as the table space being exported from the Oracle Collaboration Suite information storage database must not already exist in the target database. Review the following limitations on using transportable tablespace: The migration process uses the transportable tablespace feature to move the index and configuration data from the Oracle9 iAS Metadata Repository database to the Information Storage database. Make sure you understand the following requirements and limitations of the migration process before proceeding with the migration:

Registering Imported Instance Data With Oracle Ultra SearchĬompleting the Oracle Ultra Search Migrationĩ.1 Oracle Ultra Search Instance Migration Requirements and Limitations Importing the Oracle Ultra Search Instance to the Information Storage Database Preparing to Migrate the Oracle Ultra Search InstanceĮxporting the Oracle Ultra Search Instance from the Oracle9 iAS Metadata Repository Oracle Ultra Search Instance Migration Requirements and Limitations The following sections describe how to perform the migration: See Chapter 7 for more information on the second option. Oracle recommends using the second procedure for most cases as it is simpler. If you use the second method, Oracle Ultra Search re-creates the index in the upgraded database when the data source is recrawled. If you do not perform this procedure, you can migrate only the configuration data during the middle tier upgrade. Oracle recommends using this procedure if you have a very large index. To migrate both index and configuration data, perform the procedures in this chapter after upgrading the Oracle Collaboration Suite information storage database and before upgrading the Oracle Collaboration Suite middle tier. In Oracle Collaboration Suite, Oracle Ultra Search is used for Web content indexes, not Oracle Collaboration Suite content indexes.

This chapter describes the procedure for migrating Oracle Ultra Search index and configuration data from the Oracle9 iAS Metadata Repository to the Oracle Collaboration Suite information storage database. 9 Migrating the Oracle Ultra Search Index
