topic Re: crontab in Operating System - HP-UX

crontab

Ahmed Ibrahim_3 — Sat, 15 Apr 2000 05:38:28 GMT

Hi,

We useing HP9000 V-class system HP-UX 11.x and hosting oracle8 release 11.

I am using a script with user x and schedule it using crontab to run over
night, but it failed the error message which i am getting is as follows : -

oracle8/oracle8/stoporacle8: MANPATH: Parameter not set.
logout
*************************************************
Cron: The previous message is the standard output
and standard error of one of your crontab commands:

/oracle8/oracle8/stoporacle8
Please help if you face such problem.

Regards

Re: crontab

Melvyn Burnard_1 — Sun, 16 Apr 2000 12:32:55 GMT

In your script, are you setting ALL the environment variables correctly?
It looks like the script is looking for the MANPATH variable, and this is not
set.
I would suggest you add this in to the script.

Re: crontab

CHRIS_ANORUO — Sat, 20 May 2000 12:14:41 GMT

Hi Ahmed,

You have to include the PATH in your oracle and root .profiles and export the PATH.

Cheers!

Re: crontab

Albert E. Whale, CISSP — Mon, 22 May 2000 18:21:26 GMT

Ahmed,

First of all, the Cron tab error indicates that your Environment is not being setup properly for the Cron Job.

You can fix this one of two ways:

1. inside the script, source your evironment manually (i.e.
. .profile)

2. Execute the application from Root's Cron with the Following command:

/bin/su - {user x} -c "Script Name and all arguments"

The later will always work, however it does not allow the User to understand that the problem is that they need to establish the environment variable which they have when they are an interactive user.

Hope that helps.

Re: crontab

David Seijo — Fri, 26 May 2000 18:38:21 GMT

Hey ...I know you posted this question long time ago..but just in case you come back one day...for some reason you remember me one of my friends...is your last last name Rashard (or rachard)?

Re: crontab

glovecar — Fri, 22 Sep 2000 01:58:47 GMT

- root user login
# crontab -l > crontest
# vi crontest
0 23 * * * /usr/bin/su - root -c "/oracle8/oracle8/stoporacle8"
# crontab crontest

Re: crontab

허용제_1 — Fri, 22 Sep 2000 08:49:06 GMT

Hi

#vi /oracle8/oracle8/stoporacle8.sh
;ORACLE ORACLE STOP
su - oracle8 <

Re: crontab

Srini_2 — Thu, 28 Jun 2001 14:28:01 GMT

My cron jobs are failing for the same reason too.
"MANPATH not set". This happens even when I source
my .profile. The problem is fixed when I added MANPATH
to my .profile. Any clues as to why the cron is sensitive
to MANPATH?

OS: hpux 11 64 bit.

Re: crontab

Alexander M. Ermes — Thu, 28 Jun 2001 15:56:53 GMT

Hi there.
Usually you have a file called oraenv. In this file all variables for Oracle should be set. This script will also be run in the .profile of the user oracle. If you want to shutdown and startup Oracle with cron, try this way :
setup user oracle ( group dba )
Use this user for shutdown and startup.
There are standard scripts from Oracle for startup and shutdown ( dbstart / dbshut ). You should read all lines in /etc/oratab and do a shutdown and startup with the Oracle SIDs as parameters.
Sample line in cron :

su - oracle -c 'dbshut_all'

su - oracle -c 'dbstart_all'

If you need samples of these scripts, pls let me know and email me at Alexander_Ermes@web.de.
Rgds
Alexander M. Ermes

Re: crontab

Bill Hassell — Thu, 28 Jun 2001 16:20:41 GMT

One of the overlooked features of cron is that is has little resemblance to a normal login. The crontab man page mentions that there is no login and virtually no environment. That means that /etc/profile and .profile are not executed when the job runs.

Some cron jobs will use the su - oracle method to run on Oracle's behalf and this will login but since cron has no terminal, tty-only commands like ttytype and tset and tabs will fail with "not a typewriter" errors.

So /etc/profile and .profile need to have tests for an interactive tty before running these commands, something like:

if tty -s
then
eval (ttytype -s)
tabs
fi

Another thing to compare: Login as the oacle user and type the commands: set and env. Then create a cronjob similar to the Oracle start/stop scripts which add set and env at the beginning so you can see the differences.