8
Stopping and Starting OP

If you need to perform maintenance on the system or systems where OP resides, you should stop OP before you stop the operating system. After you perform any required maintenance, you must start OP. The procedures outlined in this chapter will ensure that you do not lose any data when you start and stop OP.

Stopping OP

Follow these steps to stop OP:

1. Stop all package builds, package deployments, and reports.

   Use the OP Administrative UI to ensure that all package builds, package deploys, and reports are stopped. If any of these are running, you can either cancel them or wait until they complete. You must also change the schedule for any builds, deploys, and reports to make sure that they do not take place while OP is stopped.

   Verify that nothing is running.

2. Stop all Recommendation Engines using the script REmaint.sh (in $ORACLE_HOME/dmt/admin).

   REmaint.sh stops (sets the status to offline) all REs known to the MOR and forces the REs to save any cached information to the MTR, using data synchronization. After the script completes, any application that attempts to use any of the stopped REs receives an RE_OFFLINE exception.

   The scripts are:

     % REmaint.sh <property filename> or
     % REmaint.sh <MOR username<MOR password><MOR JDBC connect string>

   where property file looks like:

      dbUrl=<JDBC connection string to MOR database>
   dbuserName=<MOR username>
   dbpassWord=<MOR password>

3. Stop the OP 9.0.2 scheduling engine with the following command:

      SQL> execute OP_STOP_ENGINE

   OP_STOP_ENGINE is an SQL script that resides in the MOR schema.

4. Stop the OP Save Items Archiver and OP Data Synchronization. For each RE, log in to the RE, and start SQL*Plus.
   • Issue the following command to stop the archiver:

        SQL> exec re_loader.stop_save_items_archiver_job;

   • Issue the following command to stop synchronization:

        SQL> exec re_loader.stop_data_sync_job;

At this point, you can perform any required maintenance except for changing MOR and MTR characteristics.

Starting OP

You start OP by reversing the steps that you followed to stop it:

1. Start the OP Save Items Archiver and OP Data Synchronization. For each RE, log in to the RE, and start SQL*Plus.
   • Issue the following command to start the archiver:

        SQL> exec re_loader.start_save_items_archiver_job;

   • Issue the following command to start synchronization:

        SQL> declare
      2> v_job number;
      3> begin
      4> v_job := re_loader.start_data_sync_job;
      5> end;
      6> /

2. Start the OP 9.0.2 scheduling engine with the following command:

      SQL> execute OP_START_ENGINE

   OP_START_ENGINE is an SQL script that resides in the MOR schema.

3. Start all package builds, package deployments, and reports.

   Use the OP Administrative UI to start or restart all package builds, package deploys, and reports that are stopped. You may have to change back the schedule for any builds, deploys, and reports that you changed when you stopped OP.

   Verify that all required events are running.

   After packages are deployed to them, the REs automatically start up, that is, they are no longer offline.