B Upgrading OSM to an Oracle RAC Environment

This appendix describes how to upgrade an existing Oracle Communications Order and Service Management (OSM) system that uses a single-instance database to an environment that uses Oracle Real Application Clusters (Oracle RAC). You can perform the upgrade using one of two methods:

Upgrade OSM after converting the database to Oracle RAC
Upgrade OSM to Oracle RAC using Data Pump Import Export

Upgrading OSM After Converting the Database to Oracle RAC

Using this method, you convert your single-instance database to an Oracle RAC database first, and then run the OSM installer to upgrade the OSM database schema and configure the WebLogic Server resources.

See Oracle Real Application Clusters Installation Guide for Linux and UNIX for database conversion instructions.

See "Performing the OSM Upgrade" for detailed installation steps.

Upgrading OSM to Oracle RAC Using Data Pump Import and Export

If it is not feasible to upgrade the database instance due to circumstances in your environment, such as the presence of other applications on the instance, you can export the data from the existing database instance and import it into the new version. The recommended method for doing this is Oracle Data Pump Import and Export. After the data is imported, you can run the OSM installer.

Upgrade Overview

To upgrade OSM to Oracle RAC using Oracle Data Pump, perform the following general steps:

Shut down the OSM Server. See "Shutting Down the OSM Server."
Turn off the OSM Notification Engine. See "Turning Off the Notification Engine."
Export and then import the data from the database using Oracle Data Pump. See "Exporting and Importing the Database Data."

Note:
Step 3 should be performed by a Database Administrator. Steps 2 and 5 may need to be performed by someone with database administration experience.
Run the OSM installer to upgrade the OSM database schema and configure the WebLogic Server resources. See "Performing the OSM Upgrade" for detailed installation steps.
Restart the Notification Engine. See "Restarting the Notification Engine."
Restart the OSM Server. See "Restarting the OSM Server."

Shutting Down the OSM Server

Stop OSM according to the instructions in OSM System Administrator's Guide.

Turning Off the Notification Engine

Prior to migration, ensure that the database is not processing any jobs. You do this by manually turning off the Notification Engine.

Enter the following commands into SQL*Plus:

update om_parameter 
   set value  = 'N' 
   where mnemonic = 'run_jobs';
update om_parameter 
   set value  = '86400' 
   where mnemonic = 'job_monitor_interval';
commit;

The database will stop running new jobs.

Enter the following commands into SQL*Plus:

begin
   for i in (select job from user_jobs) loop
      dbms_job.broken(i.job, TRUE);
      dbms_job.remove(i.job);
   end loop;
   commit;
end;

The database will halt any jobs that are currently running.

Enter the following command into SQL*Plus:
```
select * from user_jobs;
```
This should return no jobs running. If there are still any jobs running, consult a DBA.

Exporting and Importing the Database Data

Export the data from the non-Oracle-RAC database and import it to the Oracle RAC database. The recommended method for exporting and importing the data from the database is to use the Oracle Data Pump Import and Export utility.

For information about how to use Oracle Data Pump, see the Oracle Database documentation. Following are a few considerations for OSM:

It is best to export and import in schema mode (the default).
Ensure that you export and import both the OSM Primary Schema and the OSM Rule Engine Schema.
By default, Data Pump Import creates the schema users and performs the necessary grants. It is a good idea to use the default, and if you do, you must ensure that users with the same names do not already exist in the new database instance.

Running the OSM Installer

See "Performing the OSM Upgrade" for detailed installation steps.

Restarting the Notification Engine

After you have migrated the OSM database to the new environment, you can restart the Notification Engine.

Log in to SQL*Plus as the primary OSM schema user (not the Rule Engine user).
Enter the following command into SQL*Plus:
```
select * from user_jobs;
```
If this command returns two running jobs, you do not have to restart the Notification Engine manually: go to "Restarting the OSM Server."

Enter the following commands into SQL*Plus:

update om_parameter 
   set value  = 'Y' 
   where mnemonic = 'run_jobs';
update om_parameter 
   set value  = '600' 
   where mnemonic = 'job_monitor_interval';
commit;

The database will start running new jobs.

Enter the following commands into SQL*Plus:

begin
   om_job_pkg.resubmit_jobs(om_const_pkg.v_rule_task_type, 1, 10, 0, 0, 0, 0);
end;

The database will start the appropriate jobs.

Restarting the OSM Server

Start OSM according to the instructions in OSM System Administrator's Guide.