Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on December 22, 2025. To monitor Oracle databases, we recommend that you use PATROL for Oracle Enterprise Database.

Adding a job to the scheduler


Warning

This feature is no longer supported by any of the KM's supported versions. From version 9.7.11.01, the feature is no longer available. For more information see, 9-7-11-01-Fix-pack-1-for-PATROL-for-Oracle-Database.

To schedule a job to the Batch Scheduler, you must enter the information about the job and the schedule to use for the job.

Note

The Scheduler Admin menu command captures only the status of the last executed statement. It does not capture the return codes from the batch job itself.

  1. Choose Scheduler Admin > Schedule Jobs > Add Job from the INSTANCE menu.
  2. In the Job Name field, enter a unique name for the job, and select the category for the job from the Category menu:
    • PSL Script
    • SQL Script
    • OS Command
  3. Select a Schedule Type option to specify how often the script or command runs.
  4. Select the type of notification for PATROL to send when the job runs.
  5. Select the type of output for PATROL to use when it displays the results of the job, and select when PATROL sends the results:
    • Always --PATROL always sends the results to the output type you specified.
    • Job Succeeds --PATROL only sends the results when the job succeeds.
    • Job Fails --PATROL only sends the results when the job fails.
    • Job Completes --PATROL sends the results when the job completes, whether it succeeds or fails.

      Note

      A job is flagged as a failed job if it fails to execute. Jobs fail for several reasons: an invalid statement from the OS command; invalid PSL file permissions; compilation or process errors; or ORA- errors from the SQL statement. Because a PSL job returns no output, select the No output option, and use the Job Fails option to catch any privilege or file errors.

  6. (Optional) If the job requires certain criteria, select the number of parameters to use for this job from the Number of Parameters list. The default value is None.
     Enter the criteria for the job after you complete this screen. You can specify any criteria's that are relevant to the script or the command. PATROL does not perform any check on the job criteria's.
  7. (Optional) In Actions When Done, select whether to delete the job when it has completed.
  8. Enter the command-line instructions to use in Command Text, and if applicable, a description of the job in Description.
     If you are running a batch file on Microsoft Windows, you must place double quotation marks (") around any directories with spaces in them.
  9. Click Apply.

    Note

    You can modify a job by choosing*Scheduler Admin > Schedule Jobs > Modify Job* from the INSTANCE menu.

Where to go from here

After you have entered the job or report to run, specify the time and day that it should run. See Specifying the time the job or report should run#Specifyingthetimethejoborreportshouldrun-94403.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*