Skip Headers
Oracle® Life Sciences Data Hub Installation Guide
Release 2.1.4
Part Number E18152-05
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

9 Upgrading to Oracle Life Sciences Data Hub Release 2.1.4

This section includes the following topics:

Supported Upgrade Paths

Upgrading to Oracle Life Sciences Data Hub (Oracle LSH) is supported from the following releases. Each section begins with information on which upgrade paths require the steps in the section.

If you have already upgraded to Oracle RDBMS 11gR2 (11.2.0.1) and Oracle Applications ATG RUP7 with Oracle LSH 2.1.3, you need to follow instructions in the following sections only:

Stop Server Processes

This step is required for all upgrade paths.

Before you begin the upgrade, stop the following servers:

Patch Oracle Applications

These steps are required if you are upgrading from:

Apply Oracle Applications 11i Rollup Patch 7

If you have not already done so, install Oracle Applications 11i ATG rollup patch (RUP) 7 (patch 6241631):

  1. Apply the patch using Autopatch (see "How to Use AutoPatch").

  2. Follow instructions in My Oracle Support article 783600.1, About Oracle Applications Technology 11i.ATG_PF.H.delta.7 (RUP 7).

Apply Oracle Applications Patches

If you have not already done so, apply the following patches using Autopatch (see "How to Use AutoPatch").

  • 4477329 to fix an issue while extracting FND lookup data

  • 7456837 required for 11gR2 JDBC driver compatibility

  • 7605820 Binder utility shows bookmarks in merged document

  • 8506761 PDFBookbinder update for XML Publisher 5.6.3

  • 9655837 to fix a problem with the Rich Text Editor that prevents manually entering Oracle LSH source code

Upgrade the Database to 11.2.0.1

This step is required if you are upgrading from:

Note:

This upgrade includes an automatic upgrade of Oracle Warehouse Builder (OWB) to 11.2.0.1, which is required for Oracle LSH 2.1.4. However, do not delete your installation of OWB 10gR2 if you use Oracle Discoverer for data visualizations.

To upgrade from Oracle Database Server 10.2.0.3 or 10.2.0.4 to Oracle Database Server 11.2.0.1:

  1. Follow instructions in My Oracle Support article 881505.1, Interoperability Notes: Oracle E-Business Suite Release 11i with Oracle Database 11g Release 2 (11.2.0). The following steps are not required for Oracle LSH:

    • Migrating Oracle Portal

    • Installing Data Mining and OLAP

      Notes:

      Be sure to install the Oracle 11gR2 Example DVD. Oracle Text is included on this DVD. It is required by Oracle Thesaurus Management System for the Oracle LSH classification system.

      Note:

      My Oracle Support article 881505.1 states that Oracle Warehouse Builder 11gR2 is not yet certified for use with EBS11i. You can disregard this statement in the context of Oracle Life Sciences Data Hub.

  2. Apply patch 6880880, the latest patch for the Universal Installer.

  3. (Optional) Apply patch 9580062. This is required for bulk loading if you are planning to use the Oracle LSH Informatica adapter to develop and execute Oracle LSH Programs of type Informatica.

Change Default Password Settings

This step is required if you are upgrading from:

Oracle 11gR2 includes new default password-related settings.

Upgrade Oracle Warehouse Builder

The 11gR2 database installation by default includes an installation of OWB 11gR2. Apply OWB patches to this OWB installation.

Note:

Do not delete your installation of OWB 10gR2. It is required for Oracle Discoverer.

  1. Download the following patches from My Oracle Support (see "Finding Patches on My Oracle Support").

    • 9472946 PSE for bug 9402928 on top of 11.2.0.1

    • 9584600 PSE for base bug 9583823 on top of 11.2.0.1

      Note:

      Set the ORACLE_HOME environment variable to point to the actual Oracle Home, not the OWB Home as currently directed in the patch readme files.

      Note:

      Do not run the post-installation steps as directed in both patch readme files. You will do this later; see Run the Migration Script.

  2. Apply the patches using instructions in the readme files.

Upgrade Oracle Thesaurus Management System to 4.6.1

This step is required if you are upgrading from:

To install TMS 4.6.1:

  1. Follow instructions in Set Up a Windows Computer for Launching the TMS Installation.

  2. Follow upgrade instructions in the Oracle Thesaurus Management System 4.6.1 Installation Guide in the following sections:

    • Section 6.3.1 "Launch the Installer"

    • Section 6.3.2 "Attend to the Installer"

      Note:

      In the Installer screen Select a product to install, be sure to select TMS Database Upgrade.

  3. Apply TMS patch 4.6.1.7, which is patch number 9728948, using instructions in the release notes.

(Optional) Upgrade Informatica PowerCenter to 8.6.1, Hotfix 11

If you use Informatica PowerCenter as an integrated development environment in Oracle LSH, this step is required if you are upgrading from:

You must buy this software from Informatica.

If you are using Informatica as an integrated development environment (IDE) and processing engine, upgrade from release 8.1.1 to 8.6.1:

  1. Run the installer, selecting the option to upgrade from the previous version.

  2. Apply 8.6.1 Hotfix 11.

    Note:

    Oracle LSH has been tested ONLY with Informatica PowerCenter 8.6.1 with Hotfix 11. If more recent releases have become available, do NOT install them unless explicitly instructed to do so by an Oracle LSH-specific note or alert on My Oracle Support.

    You can get Hotfix 11 even if it has been superseded by a later version by logging a Service Request with Informatica.

  3. Create an environment file infa.env under $INFA_HOME (Informatica Installation Directory) and set the following environment variables:

    INFA_HOME=<Informatica Installation Directory>

    LANG=C

    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<Informatica Installation

    Directory>/server/bin

    On a Linux platform, add this extra line to the file:

    unset LD_ASSUME_KERNEL

(Optional) Install OBIEE 10.1.3.4.1

This step is required if you plan to use OBIEE either for visualizations or for Business Intelligence Publisher (BIP) reports and are upgrading from Oracle LSH 2.1.2. You cannot upgrade your current installation; you must reinstall the product.

The installation process uses the Oracle Universal Installer. See OBIEE 10.1.3.4.1 documentation for instructions.

If you are using OBIEE only for BIP, you can install the BI Server on either UNIX or Windows. If you are installing OBIEE for visualizations, you must install the BI Server on Windows. The Windows installation can serve both purposes. See Integrating Oracle Business Intelligence with the Oracle Life Sciences Data Hub for further information.

Migrate the Oracle Warehouse Builder Repository

This is required if you are upgrading from:

The steps in this section are required to migrate the OWB repository residing in the CDR_RTREPOS schema to the 11gR2 unified repository in the OWBSYS schema. All steps are required on the new 11gR2 OWB Home created during the database upgrade.

Create the OWBSYS Schema and Grant Privileges

Create the OWBSYS schema in the database and grant it required privileges.

Create the Schema

Note:

Running this script also creates the user OWBSYS_AUDIT. Oracle LSH does not use this account and you do not need to unlock it.

  1. Log on to the computer where Oracle LSH is installed.

  2. Change directories to <OWB_HOME>/owb/UnifiedRepos.

  3. Log in to SQL*Plus as a database user with SYSDBA privileges.

  4. Run the following script to create the OWBSYS schema:

    @cat_owb.sql

    This script creates and locks the user OWBSYS.

  5. Enter the following command to unlock the OWBSYS user:

    alter user owbsys account unlock

Note:

Oracle recommends changing the default password for this account. You will need the password later.

Grant Required Privileges

  1. Log in to SQL*Plus as the user CDR_RTREPOS. Check that you are properly logged in:

    show user;

    The system returns: CDR_RTREPOS

  2. Grant privilege to owbsys:

    grant owb_o_cdr_rtrepos to owbsys with admin option;

Point to the 11gR2 Oracle Home

  1. Log in to SQL*Plus as the OWBSYS user.

  2. Reset the OWB Home to the new 11gR2 OWB Home:

    @reset_owbcc_home;

    At the prompt, enter the full path of the 11gR2 Oracle Home. If you are installing in a Windows environment, be sure to match the case of the path exactly, including the drive letter.

Create New OWB Workspace for CDR_RTREPOS

To create a new OWB Workspace for the existing user (CDR_RTREPOS):

  1. Change directory to <OWB_HOME>/owb/bin/unix.

  2. Run the script reposinst.sh to launch the Repository Assistant.

  3. Follow instructions on screen. Enter the database connection information and then choose the Manage Warehouse Building Workspace option to create a new Warehouse Builder workspace for the existing user (CDR_RTREPOS).

Upgrade Oracle Life Sciences Data Hub

These steps are required for all upgrade paths.

Follow the instructions in the following sections of Chapter 7, "Installing the Oracle Life Sciences Data Hub."

Integrate Oracle LSH with the 11gR2 Oracle Warehouse Builder

These steps are required if you are upgrading from:

Except for the steps in Stop the 10g OWB Service, all steps must be performed on the 11g OWB Home created during the database upgrade.

This section contains the following topics:

Follow these steps to install OWB Adapters and Operators in the new 11gR2 OWB Home. Except for the steps in Stop the 10g OWB Service, all steps must be performed on the 11gR2 OWB Home created during the database upgrade.

Set Up Your Environment

You must set up your environment as follows.

Ensure that Oracle SID and Short Global Names Match

The database short global name must be the same as the Oracle SID. If they are not the same, you must change the short global name to match the Oracle SID.

For example, if the Oracle SID is LSHX2R10, the short global name must also be set to LSHX2R10.

Edit init.ora

Check the init.ora file and add the following parameters and values if they do not already exist.

Usually located in <ORACLE_HOME>/dbs on the database tier, the file is named initOracle SID.ora, (for example, initLSHX2R10.ora where the database Oracle SID is LSHX2R10).

The required parameters and values are:

Utility File Directory The first value of the parameter utl_file_dir must match the value of the Oracle Applications variable $APPLPTMP. Otherwise the post-installation program will fail. For instructions on reading and modifying Oracle Applications variables, see Increase JVM Memory.

oa_var=s_applptmp

Global Names If you plan to set up a database link to one or more databases with a name different from the current database, set the Global Names parameter to FALSE both in the current (Oracle LSH) database and in each database to which you create a link from Oracle LSH.

global_names=FALSE

Job Queue Processes This parameter value determines the number of job queue processes that are started. The default value is 2. Oracle recommends changing this to a minimum value of 10. If you do not have enough job queues started, OWB processes may not be able to start. However, too many job queues use resources unnecessarily.

job_queue_processes = 10

Local Listener Set local listener as follows:

local_listener="(ADDRESS= (PROTOCOL=TCP)(HOST=hostname.domain)(PORT=db_port))"

For example:

local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=apx208rt.us.oracle.com)(PORT=4321))"

where the hostname is apx208rt, the domain is us.oracle.com, and the port is 4321.

Note:

It is not possible to display the above strings on one line in this document. They should not contain any hard returns.

Service Names Set service names as follows:

service_names=Oracle_SID, Oracle_SID.domain

For example:

service_names=LSHX2R10, LSHX2R10.us.oracle.com

where the Oracle SID is LSHX2R10 and the domain is us.oracle.com

Time Manager The Time Manager process is necessary to move deferred messages from WAIT state to READY state when the message has passed its delay time. Set the aq_tm_processes parameter to 1 to enable the Time Manager process.

aq_tm_processes = 1

Restart the Database and Listener

If you changed the value for any parameter in the init.ora file, you must stop and start both the database and the listener for the changes to take effect.

Test Database Connectivity

Set up the environment so that you can connect to the database using SQL*Plus for the Oracle SID. This requires having values set for the following two variables in the environment:

  • ORACLE_SID

  • ORACLE_HOME

Create Directories and Copy Files

Create directories for Oracle LSH in the OWB home directory and copy files into them.

Note:

Copy all files from the locations given in the instructions. DO NOT copy the files from your old 10g OWB installation to the 11gR2 OWB installation.

  1. Go to the <OWB_HOME> directory.

  2. Create a directory under <OWB_HOME> called cdr and run chmod 755 to grant access permissions.

  3. Copy files into the <OWB_HOME>/cdr directory as follows:

    • From $FND_TOP/secure copy the .dbc Oracle Applications database connection file.

    • From $CDR_TOP/jar copy cdr_owb_jars.zip. This zip file contains the Oracle LSH/OWB integration jar files.

    • From $CDR_TOP/admin/template copy installOwbOperator.sh and installOwbAdapter.sh and installOwbBIPAdapter.sh These shell scripts integrate Oracle LSH adapters and operators with OWB.

  4. Using a zip utility, unzip cdr_owb_jars.zip to extract the following files:

    • cdr_owb_operators.jar

    • cdr_owb_adapters.jar

    • cdr_owb_bip_adapters.jar

  5. Create a directory under <OWB_HOME>/cdr called appslibs.

  6. Copy the following files into <OWB_HOME>/cdr/appslibs from

    $JAVA_TOP/oracle/apps/fnd/jar:

    • fndsec.jar

    • fndaolj.jar

    • fndcct.jar

Disable Application Server Authentication

By default when Oracle Applications 11.5.10 CU2 is installed, the application security authentication is set to ON. To enable OWB to find the JDBC connection from the DBC file during Business Area installation, set this to OFF:

  1. Open your Oracle LSH URL and log in as sysadmin.

  2. Click System Administration in the left-hand column under Navigator. The system refreshes the page and adds a column of links on the right.

  3. Under Oracle Applications Manager in the right-hand column, click Dashboard. The Applications Dashboard screen opens.

  4. Click Sitemap to go to the Sitemap tab.

  5. Under System Configuration, click AutoConfig. The AutoConfig screen opens.

  6. Under Context Files, click the Edit Parameters icon for the Application Tier. The Context File Parameters screen opens.

  7. From the Search drop-down list, select OA_VAR and click Go.

  8. In the field next to the Search drop-down list, enter the parameter name s_appserverid_authentication and click Go.

  9. In the Value field for s_appserverid_authentication, change the value to OFF.

  10. Run AutoConfig. See My Oracle Support document number 165195.1.

  11. Stop and start the Apache server for the new value to take effect.

Edit run_service.sh

Edit the run_service.sh file as follows:

  1. Go to the directory <OWB_HOME>/owb/bin/unix

  2. Back up the run_service.sh as run_service.sh.orig

  3. Open run_service.sh.

  4. Find the command starting with: $JAVAPATH/bin/java

  5. Modify this command by adding the DBC_LOCATION environment variable using the -D command line option. Enter the following string before the first existing -D parameter in the command:

    -DDBC_LOCATION="${OWB_HOME}/cdr/DBC_file_name.dbc"

    For example:

    $JAVAPATH/bin/java -Xmx768M -DDBC_LOCATION="${OWB_HOME}/cdr/XYZ.dbc" -D...

    where XYZ.dbc is the DBC file name.

In addition, ONLY if you are installing on an HP-UX PA-RISC (32-bit) system, change the following line for the HP-UX platform (as per My Oracle Support document 286656.1, Error Resource File Dcesqres Library Not Found When Creating An apps-mode EUL Using eul api):

LD_LIBRARY_PATH=${ORACLE_HOME}/lib

to:

LD_LIBRARY_PATH=${ORACLE_HOME}/lib32

Edit runtime.properties

This step does two things:

  • Character Semantics Profile. This step enables OWB to read the setting of the profile LSH: Use Character Semantics for Workarea Installation. You can then set that profile to select whether to use byte or character semantics during Work Area installation. The default setting is byte. If your data includes special characters, Oracle recommends using character semantics to help ensure that Oracle LSH stores and displays the characters correctly. See the Oracle Life Sciences Data Hub System Administrator's Guide for more information and instructions for setting the profile.

  • OWB 10g and 11gR2 Integration. This step tells OWB 11gR2, which runs internal Oracle LSH processes, where to find OWB 10g, which is required for Oracle Discoverer-related processes.

Edit the Runtime.properties file as follows:

  1. Go to the directory <OWB_HOME>/owb/bin/admin.

  2. Edit Runtime.properties by adding the following lines at the end:

    connection.init_session=apps.cdr_owb_session_setup

    property.RuntimePlatform.0.DISCO_HOME= full_path_of_owb_10g_home

Edit owb.classpath

Edit the owb.classpath file as follows:

  1. Go to the directory <OWB_HOME>/owb/bin/admin.

  2. Back up the owb.classpath as owb.classpath.orig

  3. Edit owb.classpath. After the section on "OWB external jars" add the following lines:

    $OWB_HOME/cdr/cdr_owb_operators.jar

    $OWB_HOME/cdr/cdr_owb_adapters.jar

    $OWB_HOME/cdr/appslibs/fndsec.jar

    $OWB_HOME/cdr/appslibs/fndaolj.jar

    $OWB_HOME/cdr/appslibs/fndcct.jar

    If you are using or plan to use Oracle Business Intelligence Publisher, add the following lines as well:

    $OWB_HOME/cdr/cdr_owb_bip_adapters.jar

    $OWB_HOME/owb/lib/int/rtpcommon.jar

    $OWB_HOME/owb/lib/int/rtpplatform.jar

    $OWB_HOME/lib/xmlparserv2.jar

    $OWB_HOME/lib/activation.jar

    $OWB_HOME/lib/mail.jar

    $OWB_HOME/oc4j/j2ee/home/lib/http_client.jar

    $OWB_HOME/jdev/lib/jdev-rt.jar

    $JAVA_HOME/oracle/apps/fnd/3rdparty/bc4jdomorcl.jar

    Note:

    If your database and application servers are installed on different machines, you must copy this file from the application server to the $OWB_HOME/cdr/appslibs directory on the database server and include the new path instead of the line above:

    $OWB_HOME/cdr/appslibs/bc4jdomorcl.jar

    In addition, for use with Oracle Business Intelligence Publisher, add the physical path for: ORACLE_HOME_VALUE/oc4j/webservices/lib/soap.jar.

    Note:

    The last two locations listed above are different in the 11gR2 installation than they were in the 10g installation.

Edit Shell Scripts to Match Directory Structure

Before you run the shell scripts, edit the following values in each script to reflect your environment values:

  • DB_HOST

  • DB_PORT

  • DB_SERVICE_NAME

  • DB_SID

  • OWB_HOME

  • Make sure that the <OWB_HOME> directory is set up the same way as in the file pathnames in the files installOwbOperator.sh and installOwbAdapter.sh

Run OWB Shell Scripts

Do the following:

  1. Change directory to <OWB_HOME>/cdr.

  2. Install the adapters by running the following scripts. The third script is required only if you are using the Oracle Business Intelligence Publisher (BIP) adapter (required for creating BIP Programs).

    ./installOwbOperator.sh

    ./installOwbAdapter.sh

    ./installOwbBIPAdapter.sh

    No Java exceptions should occur.

    Note:

    If you run installOwbOperator.sh more than once, you receive a unique constraint violation error. You can safely ignore this message.

    The system creates a log file for each script in <OWB_HOME>/cdr called installOwbOperator.log and installOwbAdapter.log. The log files spool out the actual Java statement that the shell script sets up.

Stop and Start the OWB Service

You must stop and start the OWB service.

Stop the OWB Service

To stop the OWB service do the following:

  1. Change directory to $OWB_HOME/owb/rtp/sql

  2. Log into SQL as OWBSYS.

  3. At the SQL prompt, enter:

    @stop_service.sql

When the system displays the words "Not Available" the service is stopped.

Start the OWB Service

To start the OWB service do the following:

  1. Change directory to $OWB_HOME/owb/rtp/sql

  2. Log into SQL as OWBSYS.

  3. At the SQL prompt, enter:

    @start_service.sql

When the system displays the word "Available" the service has been restarted.

Run the Migration Script

Run the OWB migration script to migrate the OWB repository residing in the CDR_RTREPOS schema to the unified repository in OWBSYS schema.

  1. Log in to the computer where OWB is installed.

  2. Go to the directory <OWB_HOME>/owb/rtasst.

  3. Log in to SQL*Plus as the OWBSYS user.

  4. Run the migration scripts:

    • wb_rt_upgrade_actions.pls

    • wb_rt_upgrade_actions.plb

    • wb_rt_upgrade.plb

    • wb_rti_object_catalog.plb

Export the OWB Repository Owned by User CDR_RTREPOS

Export the old OWB repository:

  1. In your 11gR2 OWB Home, change directories to <OWB_HOME>/owb/bin/unix.

  2. Run the script reposinst.sh to launch the Repository Assistant.

    1. Choose the option Upgrade Repository to Current Release of OracleWareHouseBuilder .

    2. Choose the option Export Entire Repository to File.

    3. Enter username CDR_RTREPOS and its password.

    4. Export the repository.

Stop the 10g OWB Service

You do not need the OWB service to run after upgrading to 11gR2, even if you are using Oracle Discoverer and need to keep your OWB 10g installation. Oracle Discoverer has only a file dependency on 10g OWB.

Note:

These are the only steps that you perform on your 10g OWB Home. All other OWB steps, including the Export step, are on the 11gR2 Home.

To stop the 10g OWB process:

  1. Go to 10g_OWB_HOME/owb/bin/unix.

  2. Rename run_service.sh as run_service_temp.sh.

  3. Log in to SQL*Plus as the user CDR_RTREPOS. Check that you are properly logged in:

    show user;

    The system returns: CDR_RTREPOS

  4. Run the Stop Service script:

    @OWB_HOME/owb/rtp/sql/stop_service.sql

Import the OWB Repository

Import the old OWB repository to the new unified repository:

  1. In <OWB_HOME>/owb/bin/unix, run the script reposinst.sh to launch the Repository Assistant.

    1. Choose the option Upgrade Repository to Current Release of OracleWareHouseBuilder .

    2. Choose the option Import Entire Repository to file.

    3. Enter username OWBSYS and its password.

    4. Specify the export dump file created in Export the OWB Repository Owned by User CDR_RTREPOS and import the file.

  2. The system displays a message that the import is successful or not.

If the import is not successful:

  1. Log in to SQL*Plus as a database user with SYSDBA privileges.

  2. Change directories to <OWB_HOME>/owb/UnifiedRepos.

  3. Run the script clean_owbsys.sql.

  4. Repeat all the steps beginning with running cat_owb.sql in Create the OWBSYS Schema and Grant Privileges.

Migrate the Oracle Warehouse Builder Stores

These steps are required if you are upgrading from:

Migrate the Store Passwords and Audit Task ID

No input is required to migrate the Audit Task ID.

  1. Log in to the database as CDR_RTREPOS.

  2. Run the script $CDR_TOP/patch/115/sql/cdrowbstoreupdate.sql.

    The script prompts you for the passwords to the following accounts:

    • OWBSYS

    • APPS

Upgrade the Workflow Store

Start the OWB Browser Listener

  1. Log in to the computer where OWB is installed.

  2. Go to the directory <OWB_HOME>/owb/bin/unix.

  3. Run the script startOwbbInst.sh.

    At the prompt, enter the oc4j password.

Upgrade the Workflow Store

  1. Launch the OWB repository through its URL:

    https://<DB_Host_Name>.<domain>:<port>/owbb/RABLogin.uix?mode=runtime

    For example:

    https://rws60008rems.us.oracle.com:8999/owbb/RABLogin.uix?mode=runtime

  2. In the Login screen, enter:

    • User name CDR_RTREPOS and its password

    • The Host, Port, and Service Name of the database

  3. Select the Control Center radio button and click Login.

  4. For Workspace, select CDR_RTREPOS.CDR_RTREPOS and click Go.

  5. Click Locations Report.

  6. On the Location screen, order by store name.

  7. Click on the hyperlink in the Validation column (the rightmost column) for the APPS_MODULE_LOCATION1 store.

  8. Update the Netservice name to null and click Update.

  9. Check that the host, port and SID of the store are the same as that of the control center which is displayed at the top of the screen.

  10. Enter the APPS schema password and click Get Status.

  11. Enter the APPS schema password and click Upgrade.

  12. Observe that the store status changes to Valid.

  13. Repeat Steps 10 to 15 for the APPS store.

  14. Close the browser.

Stop the OWB Browser Listener

  1. Log in to the computer where OWB is installed.

  2. Go to the directory <OWB_HOME>/owb/bin/unix.

  3. Run the script stopOwbbInst.sh.

    At the prompt, enter the oc4j password.

Upgrade Other OWB Stores

To upgrade other OWB stores:

  1. Go to the directory <OWB_HOME>/owb/bin/unix.

  2. Run upgradeLoc.sh by specifying the following parameters:

    sh upgradeLoc.sh <host>.<domain> <port> <service> <wks_owner_name> <wks_owner_pswd> <workspace_owner.workspace_name>

    For example:

    sh upgradeloc.sh rws60160rems.us.oracle.com  1557 ildv214  CDR_RTREPOS  CDR_RTREPOS  CDR_RTREPOS.CDR_RTREPOS

  3. Check the log file upgradeLoc.log which is created in the same directory and confirm that there are no errors.

Edit listener_ifile.ora

If you have not already done so, configure the database listener to allow OWB to communicate with the database by editing your listener_ifile.ora file; see Edit listener_ifile.ora.

Upgrade the Distributed Processing Server

This step is required for all upgrade paths.

Upgrade the Oracle LSH DP Server on every computer where it is installed:

  1. Go to the lib directory in the DP Server Home directory on each computer where the DP Server resides.

  2. Copy DPServer.zip from $CDR_TOP/jar to the lib directory.

  3. Using GNU zip or another utility, unzip the DPServer.jar from the zip file into the lib directory. This extracts DPServer.jar.

  4. Copy aqapi.jar from $IAS_ORACLE_HOME/rdbms/jlib to the DP Server Home lib directory. Overwrite the existing aqapi.jar file.

  5. On each computer where you install the DP Server, set the NSL_LANG environment variable to UTF8.

Do the Remaining Post-Installation Tasks

These steps are required for all upgrade paths.

Follow the instructions in the following sections:

Start Server Processes

This step is required if you are upgrading from:

Start the following servers:

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us