4.2.2 Starting the Dispatcher

Although multiple jobs and mantas instances can run concurrently in the application, only one dispatcher service per database per installation should run at one time.

The application provides a script to check on the status of the dispatcher automatically and restart it, if necessary. Oracle recommends this method of running the dispatcher.

To start the dispatcher, follow these steps:

1. Verify that the dispatcher is not already running by typing ps -ef | grep dispatch and pressing Enter at the system prompt.

   If the dispatcher is running, an instance of the dispatcher appears on the screen for the server. If the dispatcher is not running, proceed to Step 2.

2. Type start_chkdisp.sh <sleep time> and press Enter at the system prompt to start the dispatcher.

   The dispatcher queries the database to check for any new jobs that must be run. In between these checks, the dispatcher sleeps for the time that you specify through the <sleep time> parameter (in minutes).

   Optional parameters include the following:

   • dispatch name: Provides a unique name for each dispatcher when running multiple dispatchers on one machine.
   • JVM size: Indicates the amount of memory to allocate to Java processing.

   Note:

   For 32-bit Linux configurations, Oracle recommends running with the default JVM size (128 MB) due to 2 GB process limit.

   The script executes and ends quickly. The dispatcher starts and continues to run in the background.