| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.2) for hp-ux PA-RISC (64-bit), Linux x86 and Solaris Operating Environment (SPARC) Part Number B25495-07 |
|
|
View PDF |
| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.2) for hp-ux PA-RISC (64-bit), Linux x86 and Solaris Operating Environment (SPARC) Part Number B25495-07 |
|
|
View PDF |
This chapter describes the procedure for migrating Oracle Ultra Search index and configuration data from the Oracle9iAS Metadata Repository to the Oracle Collaboration Suite information storage database. In Oracle Collaboration Suite, Oracle Ultra Search is used for Web content indexes, not Oracle Collaboration Suite content indexes.
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. Oracle recommends using this procedure if you have a very large index.
If you do not perform this procedure, you can migrate only the configuration data during the middle tier upgrade. If you use the second method, Oracle Ultra Search re-creates the index in the upgraded database when the data source is recrawled. Oracle recommends using the second procedure for most cases as it is simpler. See Chapter 7 for more information on the second option.
The following sections describe how to perform the migration:
Oracle Ultra Search Instance Migration Requirements and Limitations
Exporting the Oracle Ultra Search Instance from the Oracle9iAS Metadata Repository
Importing the Oracle Ultra Search Instance to the Information Storage Database
Make sure you understand the following requirements and limitations of the migration process before proceeding with the migration:
The migration process uses the transportable tablespace feature to move the index and configuration data from the Oracle9iAS Metadata Repository database to the Information Storage database. Review the following limitations on using transportable tablespace:
The transportable set must be self-contained.
A 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.
The two databases do not have to be on the same release.
The source and target databases must be on the same type of hardware and operating-system platform.
The source and target databases must have the same database block size.
The source and target databases must have the same character set.
Materialized views, function-based indexes, scoped REFs, 8.0 compatible advanced queues with multiple-recipients, and domain indexes can't be transported in this manner.
Users with tables in the exported tablespace should exist in the target database prior to initiating the import. If the user does not already exist, you will get an error message.
The metadata exported from the target database does not contain enough information to create the user in the target database. The reason is that, if the metadata contained the user details, it might overwrite the privileges of an existing user in the target database. For example, a user with the same name may already exist in the target database.
By not maintaining the user details, we preserve the security of the database.
If the tablespace containing the Oracle Ultra Search configuration and index data does not meet the requirements, you cannot migrate your data using this procedure. The premigration script described in Section 9.2 performs some but not all of the checks.
See Oracle9i Database Administrator's Guide for more information about transportable tablespace.
One step of the migration, explained in Section 9.5, is to create a schema to hold the migrated instance. This schema cannot already hold an existing instance. If the schema does hold an existing instance, drop that instance before performing the migration.
The procedure does not support migration of the following data:
Oracle Ultra Search instances in the Oracle9iAS Metadata Repository whose tablespace name already exists in the Oracle Collaboration Suite information storage database. If a tablespace name already exists, use the instance migration procedure described in Section 7.3.3.
Remote crawler registration information. An existing schedule assigned to a remote crawler will be reassigned to a local crawler after the migration.
Table data source.
E-mail data source, unless the e-mail archive directory is accessible from the Information Storage Database
If the Oracle9iAS Metadata Repository database and the Oracle Collaboration Suite information storage database are on different systems, there may be problems with the migrated file data source unless it has the same access directory path on the Oracle Collaboration Suite information storage database system.
You must re-enter security information such as the HTTP authentication and e-mail passwords
The migrated instance is not available until the Oracle Collaboration Suite middle tier is upgraded. The middle tier upgrade process will also upgrade the migrated instance to be used in Oracle Ultra Search 10.1.0.3 environment.
The Oracle home of the Oracle Collaboration Suite Database 10g (10.1.2) contains the premigration script that prepares the system for the migration.
To run the premigration script:
Log into the Oracle9iAS Metadata Repository database as SYS. For example:
sqlplus "sys/password as sysdba"
Enter the following command:
@ORACLE_HOME/ultrasearch/admin/wkpremig.sql
where ORACLE_HOME is the location of the upgraded Oracle Collaboration Suite Database 10g (10.1.2) database
The premigration script performs the following tasks:
Sets all Oracle Ultra Search instances in the Oracle9iAS Metadata Repository to READ-ONLY mode. This mode means that:
Any executing schedule is stopped.
All schedules are disabled.
Instance data can no longer be modified.
Makes an inventory of the Oracle Ultra Search instances to be migrated from the Oracle9iAS Metadata Repository database. It displays the instance name, instance owner schema name, and the tablespace used by the schema.
Determines whether the tablespace used by the instances is self-contained by executing the transport_set_check procedure in the Oracle package DBMS_TTS.
Note that this check is a necessary but not sufficient condition for using the transportable tablespace feature. You must meet the other criteria for using transportable tablespace.
Rerunning the script toggles Ultra Search instances between UPDATABLE state and READ-ONLY state.
Review the results of the premigration script which are displayed on your standard output. The premigration script executes the transport_set_check procedure as well as the following SQL command:
select * from transport_set_violations;
If there are violations, then run wkpremig.sql again to set the instance back to UPDATABLE mode. You cannot use this procedure to migrate the your instance and index data. You can migrate your instance data only using the procedure described in Section 7.3.3.
If there are no violations, and you have verified that your instance meets the hardware compatibility and other criteria for transportable tablespace, then rerun wkpremig.sql again to set the instance back to UPDATABLE mode. Proceed with the steps in Section 9.3.1.
Before exporting the Oracle Ultra Search instances from the Oracle9iAS Metadata Repository, perform the prerequisites for using the Export utility.
To prepare to use Export:
Log into the Oracle9iAS Metadata Repository database as SYS and run the following command:
ORACLE_HOME/rdbms/admin/catexp.sql
Ensure there is sufficient disk or tape storage to write the export file
Verify that you have the required access privileges.
|
See Also: Oracle9i Database Utilities Release 1 (9.0.1) for more information on using the Export utility. |
Perform the export for each instance that can be migrated using transportable tablespace:
Set the tablespace to READ-ONLY mode by entering the following commands from the Oracle home bin directory:
sqlplus Òsys/password as sysdbaÓ alter tablespace tablespace_name read only;
Run the Export utility from the Oracle home bin directory:
exp \'sys/<password of sys user> as sysdba\' transport_tablespace=y tablespaces=list_of_transportable_tablespaces file=export_file_name
where
list_of_transportable_tablespaces is the list of names of transportable tablespaces separated by commas
export_file_name is the name of the export file (also called the structural information file)
For example, if there is one tablespace:
exp \'sys/manager as sysdba\' transport_tablespace=y tablespaces=us_data file=us_data.dmp
For another example, if there is more than one tablespace:
exp \'sys/manager as sysdba\' transport_tablespace=y tablespaces=(us_data1,us_data2) file=us_data.dmp
Before exporting the Oracle Ultra Search instances from the Oracle9iAS Metadata Repository, perform the prerequisite steps.
Copy the datafiles and the export file to a place accessible to the Information Storage database. Use any utility for copying flat files, such as FTP binary, an operating system utility or CD_ROM publishing.
Prepare the Information Storage database to use the Import utility by running the catexp.sql script as described in Section 9.3.
Create a new database schema for each Oracle Ultra Search instance to be migrated. The new schema name must be identical to the exported one. Since this schema will hold the migrated instance, it cannot already hold an existing instance. If the schema does hold an existing instance, drop that instance before performing the migration.
See Section 7.3.3 for instructions on creating schemas for Oracle Ultra Search instances.
|
Note: If a schema with the same name already exists, make sure it is permissible to import Oracle Ultra Search instance data into that schema. |
To import the transportable tablespaces into the Oracle Collaboration Suite information storage database:
Run the Import utility from the Oracle home bin directory:
imp \'sys/password as sysdba\' transport_tablespace=y file=import_file datafiles=list_of_data_files tablespaces=list_of_transportable_tablespaces tts_owners=ultrasearch_schema_name fromuser=ultrasearch_schema_name touser=ultrasearch_schema_name
For example, if you have a schema named 'adam' with a tablespace 'us_data':
imp \'sys/manager as sysdba\' transport_tablespace=y file=us_data.dmp datafiles='/info/oracle/dbs/us_data.dbf' tablespaces=us_data tts_owners=adam fromuser=adam touser=adam
Enter the following commands to set the tablespace in the Oracle9iAS Metadata Repository database back to READ-WRITE mode:
sqlplus Òsys/sys_password as sysdbaÓ alter tablespace tablespace_name read write;
There are two procedures involved in registering imported instance data with Oracle Ultra Search. These procedures are described in the following sections:
Before performing the instance data registration, you need to create a TNS alias for the Oracle9iAS Metadata Repository database in the Oracle Collaboration Suite information storage database. If a TNS alias already exists, you can reuse the alias name and skip the steps in this section.
To create a TNS name for the Oracle9iAS Metadata Repository database:
Set the ORACLE_HOME environment variable to the Oracle home of the upgraded Oracle Collaboration Suite Database.
Start the Oracle Net Configuration Assistant by entering the following command:
$ORACLE_HOME/bin/netca
Select Local Net Service Name Configuration. Click Next.
Select Add. Click Next.
Select Oracle8i or later database or service. Click Next.
In the Service Name field, enter the service name of the Oracle9iAS Metadata Repository database. Click Next.
Select TCP. Click Next.
In the Host Name field, enter the name of the system running the Oracle9iAS Metadata Repository database. Click Next.
Select Use Standard Port Number of 1521 if the Oracle9iAS Metadata Repository database listener is listening on port 1521. Otherwise select Use Another Port Number and enter the port number where the Oracle9iAS Metadata Repository database listener is listenering. Click Next.
Select Yes, perform a test to test the connection. If the connection is successful, click Next.
In the Net Service Name field, leave the default service name or enter a different name. Click Next.
On the screen with the message "Would you like to configure another net service name", select No. The message "Net Service name complete" appears. Click Next and then Finish.
You use the net service name created in step 11 during the next procedure.
To register the imported instance data with Oracle Ultra Search:
Log into the Oracle Collaboration Suite Database as SYS.
Create a public, fixed WKSYS database link to the Oracle9iAS Metadata Repository:
create public database link mrlink connect to wksys identified by wksys_password using 'mr_db_tns_name_entry';
where:
wksys_password is the WKSYS password in the Oracle9iAS Metadata Repository database
mr_db_tns_name_entry is the net access descriptor or the TNS alias specified in the tnsname.ora file. This is the same name created in Section 9.5.1.
Verify the database link by running the following query as the Oracle Collaboration Suite Database WKSYS user:
select inst_name from wk$instance@mrlink;
The query should return a list of instances in the Oracle9iAS Metadata Repository database.
For each Oracle Ultra Search instance, run the migration script on the Oracle Collaboration Suite information storage database:
@ ORACLE_HOME/ultrasearch/admin/wkreginst.sql mrlink old_inst new_inst new_inst_owner password
where:
ORACLE_HOME is the location of the Oracle Collaboration Suite Database 10g (10.1.2)
mrlink is the database link created in step 2
old_inst is the original name of the instance exported from the Oracle9iAS Metadata Repository database
new_inst is the name the instance has after the migration. You can choose the same name as the original instance or use a new name.
new_inst_owner is the name of the schema that imports the instance data
password is the password of the schema that imports the instance data
For example:
@ ORACLE_HOME/ultrasearch/admin/wkreginst.sql mrlink old_inst new_inst adam smith
Repeat step 4 for each instance you are importing.
Drop the public database link after migrating all the instances:
drop public database link mrlink;
After the migration, the upgrade is not yet complete:
All instances remain in a READ-ONLY mode. To change the instance back to UPDATABLE mode, perform the following steps:
Log in to the Oracle Ultra Search administration tool. This takes you to the Instances page.
From the Instances page, click Edit.
Select the box corresponding to UPDATABLE.
Click Apply.
|
See Also: "Instances Page" in Chapter 8 of Oracle Ultra Search Administrator's Guide. |
Performing the middle tier upgrade using the Oracle Universal Installer automatically points Oracle Ultra Search on the middle tier to the upgraded Oracle Collaboration Suite Database.
