Release 9.2
 Home |
 Book List |
 Contents |
 Master Index |
 Feedback |
| Oracle Ultra Search Online Documentation Release 9.2 |
|
 |
Related Topics |  |
 |
 |
|
To migrate to the most recent Oracle Ultra Search, you must run the migration script and perform some manual steps.
The Ultra Search migration script first verifies the version of the current system, then upgrades the system and migrates user data. User data includes all dictionary and table data, such as information about the metadata, data sources, mappings, crawler schedules, authentication, and query statistics.
All crawler schedules and jobs created in the older version are disabled before data and system migration. When migration is complete, the system administrator should re-activate the crawling schedule to re-index the document. You do not need to reconfigure the system or re-enter any data. Users can still query documents that were crawled and indexed by the previous version.
Ultra Search with the database and Ultra Search with iAS share the same data model. If you migrate from iAS to the database, then there is no need to run the migration scripts or perform the manual steps.
There are two approaches to migrate user data: the in-place approach and the ETL (extract-transform-load) approach. With the in-place approach, the current ORACLE_HOME is used, while with the ETL approach, a new ORACLE_HOME is created.
In-Place Migration
In-place migration upgrades existing configurations and user data to the latest Ultra Search release. Upgraded files are left in place, and the source installation is modified. The benefit to this approach is that it might conserve disk space.
With the in-place approach, data migration involves the following six steps:
- Back up user data
- Uninstall previous database objects
- Install new database objects
- Re-create user instances
- Restore data
- Rebuild index
Use the SQL script wk0upgrade.sql to execute the in-place migration steps one through five, listed in the preceding section. The script is located in the %ULTRASEARCH_HOME%/admin/ directory. It requires the following input parameters:
- SYSPW: password of the user SYS
- WKSYSPW: password of the user WKSYS
- HOST: database host machine
- PORT: database port number
- ORACLE_SID: database SID
- WK_TABLESPACE: tablespace for Ultra Search
- WK_TEMPTABLESPACE: temporary tablespace
- CONN_STRING: database connect string
- ORACLE_HOME: the path of Oracle home
- JAVA_EXE_PATH: Java executable file path
- PATH_SEPARATOR: Java classpath separator; use ':' for UNIX or ';' for Windows NT
The sixth step requires the system administrator to re-activate all crawling schedules through the Ultra Search administration tool.
Note: This migration is performed based on the Ultra Search 9.0.1 system only. Before performing user data migration, the database system should be upgraded to version 9.2.
Extract-Transform-Load Migration
Extract-transform-load (ETL) migration extracts the useful subset of configuration data from the source installation, transforms necessary data, and loads or merges this data into a new installation of Ultra Search. This approach might require more disk space, but it offers the following benefits:
- No destabilization of the source installation
- Stability of target installation
- No installer integration requirement
With the ETL approach, data migration involves the following five steps:
- Install the new system (for example, 9.2) in a new ORACLE_HOME
- Re-create user instance schemas and related database objects
- Re-create user instances
- Restore data
- Rebuild index
The first two steps in the ETL approach must be done manually:
- Install Ultra Search 9.2 in a separate ORACLE_HOME, either on the same machine or on a different machine. If the new 9.2 system is installed in the same machine as the old 9.0.1 system, then the database listener port number should be configured to a different number than the old 9.0.1 database. This lets both the old and the new database run at the same time.
- Re-create all 9.0.1 user instance schemas in the 9.2 database in the new ORACLE_HOME. Also, for each table data source created in 9.0.1, if the base table is located in the local database, then you must copy the base table to the new 9.2 database. If the table data source base table is set to a remote database table, then you must to re-create the database link from the new 9.2 database to the remote database.
Use the SQL script wk0migrate.sql to run the ETL migration steps three and four. The script is located in the %ULTRASEARCH_HOME%/admin/ directory. It requires the following input parameters:
- WKSYSPW: password of the user WKSYS
- CONN_STRING: database connect string
- SRC_WKSYSPW: password of the source database (9.0.1 database) user WKSYS
- SRC_CONN_STRING: source database connect string
The fifth step requires the system administrator to re-activate all crawling schedules through the Ultra Search administration tool.
Note: The migration script does not roll back the Ultra Search system to the old version if an unexpected error occurs, such as a power failure or system failure. For in-place migration, back up the database before starting migration. For ETL migration, because all previous data is kept, you can switch back to the previous (for example, 9.0.1) system
The migration script provides log files to show which actions the migration has taken. The migration script writes the following contents to the log file:
- The current execution step
- Any error message raised from the stored procedures
- Number of data records backup
- Number of data records copied or migrated
For in-place migration, the wk0upgrade.sql script writes the execution logs to the file wk0upgrade.log in the %ULTRASEARCH_HOME%/admin/ directory.
For ETL migration, the wk0migrate.sql script writes the execution logs to the file wk0migrate.log in the %ULTRASEARCH_HOME%/admin/ directory.
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|