Use the runjob
command to control how a job is executed. The command enables you to start a job in the following ways:
Immediately
In an order different from that of the scheduler
On a specific device or a device from which the job was previously restricted
See Also:
"Job Commands" for related commandsIf you are attempting to control the execution of another user's jobs, then you must have the right to modify any job, regardless of its owner. If you are attempting to control the execution of your own jobs, then you must have the right to modify any jobs owned by user.
run•job { --asap/-a | --now/-n | { --priority/-p schedule-priority } } [ --device/-d device-name ] [ --quiet/-q | --verbose/-v ] job-id ...
Starts the job as soon a possible by raising it to priority 1.
Starts the job now. If unable to start the job, Oracle Secure Backup generates an error message.
Resets the job priority to schedule-priority.The default priority is 100. Refer to "schedule-priority" for a description of the schedule-priority placeholder.
Runs the job on the device specified by device-name, ignoring job requirements.
Runs the job in quiet mode. --quiet
directs obtool
to suppress status messages it would normally write to stdout
. Note that Oracle Secure Backup never suppresses error messages.
Displays output when running the job.
Specifies the identification number of the job you want to run. Execute the lsjob command to display job IDs.
Example 2-147 lists a pending job and runs it immediately.
Example 2-147 Running a Job Now
ob> lsjob --pending Job ID Sched time Contents State ---------------- ----------- ------------------------------ ---------------------- sbt/23 03/22.21:00 dataset workdata.ds future work ob> runjob --device tape1 --now sbt/23 ob> lsjob --all sbt/23 Job ID Sched time Contents State ---------------- ----------- ------------------------------ ---------------------- sbt/23 03/22.21:00 dataset workdata.ds completed successfully at 2005/03/22.18:09