To set your services settings:
Note: If you are running services and P6 on the same server, you should keep the defaults for the rates settings. If you want to apply the service immediately, you should set the rates low. Remember that if the server is actively applying the service, all users will experience delays in the application.
Choose false if you want the application to treat the concurrent threads of services as equal to zero. When you set to false, the values for the threads will stay the same.
The default is 10s.
Enter anything from 1s-24d20h31m23s647.
The default is 1d.
Enter anything from 1h-24d.
Once the time is met all ASAP jobs that have a status other than running or delegated will be removed from the table automatically. Running and delegated jobs will be removed if they are older than the cleanup rate or if they are older than one day, whichever is greater.
Note: Make sure that the cleanup rate is greater than your longest running job.
Enable Job Cleanup on Startup will start when the application initially launches and will check for any recurring jobs that are running. It will set the status of all running jobs to pending for all databases that have Database/Instance/Auto Start Services enabled. It also follows the Services/Enable All Services setting and will not run if Enable All Services is set to false.
Enable Job Cleanup on Startup can run on a full build or the separate job services application. If you are on a clustered environment, run this service in only one instance.
Tips
See Configuring a Separate Server for Job Services for more information on how to set these settings.
Related Topics |
Legal Notices
Copyright © 1999, 2015,
Oracle and/or its affiliates. All rights reserved.
Last Published Wednesday, July 29, 2015