topic Crontab, Startup scripts in Operating System - HP-UX

Crontab, Startup scripts

SAMIR SHAH_1 — Thu, 25 Jan 2001 04:23:44 GMT

1. I face one problem nowadays that the cronjobs which are scheduled by root thru SAM are automatically removed from crontab. For eg. If I have scheduled to shutdown the server at certain time and if I see cronjobs thru crontab -l, it will show that job in the file but after sometime, if I give the same command, it does not show there that particular command.

Why it happens so?

2. I want my Oracle database to startup when the server starts. So, I prepared one "test" script and put in /sbin/init.d and then created start and kill links and put them in /sbin/rc3.d and /sbin/rc0.d respectively. I gave file name as S300test.rc and K500test.
But, it has no effect when the server starts.

What should be the problem?

Pl. help.

Thanks in advance.

Samir Shah

Re: Crontab, Startup scripts

Isralyn Manalac — Thu, 25 Jan 2001 05:06:36 GMT

Hi,

On the crontab issue, please check if you have the latest cron patch.

On the startup script, I noticed that you named the SXXX script differently as compared to the KXXX script. Aside from the prefix SXXX and KXXX, both should bear the same script name, e.g., S340test.bak and K400test.bak.

Re: Crontab, Startup scripts

Carlos Fernandez Riera — Thu, 25 Jan 2001 08:59:10 GMT

The first thing you must do is read /etc/rc.log to see if your startup script was called and errors returned.

Its very usual that you need add PATH, ORACLE_SID and other variables to your script, that are set in your interactive session.

Re: Crontab, Startup scripts

Douglas Cromby_1 — Thu, 25 Jan 2001 10:18:34 GMT

Regarding the startup script, they are usually designed so that the same script is referenced on starting and stopping. For example to stop and start sendmail we do:

/sbin/init.d/sendmail start

/sbin/init.d/sendmail stop

To get it to start automatically, you configure /etc/rc.config.d/mailservs. Could there be an equivalent file there for Oracle?

Re: Crontab, Startup scripts

Victor BERRIDGE — Thu, 25 Jan 2001 10:23:09 GMT

Hi,
Here is an example of rc.oracle that you should put in /sbin/init.d:
#!/usr/bin/ksh
export ORACTI_EXPLOIT=/opt/oracle/admin/exploit
export PATH=$PATH:/usr/bin:$ORACTI_EXPLOIT/proc

case "$1" in
start_msg)
echo "Start Oracle"
;;
stop_msg)
echo "Stop Oracle"
;;
start)
$ORACTI_EXPLOIT/proc/db_start
su - oracle -c $ORACTI_EXPLOIT/proc/net_start
;;
stop)
su - oracle -c $ORACTI_EXPLOIT/proc/net_stop
$ORACTI_EXPLOIT/proc/db_shut
;;
*)
echo "usage: $0 {start|stop}"
#rval=1
;;
esac
==================
Then you will have to make the links Sxxxoracle and Kxxxoracle in the runlevel you have chosen.
You have have to adapt it to your needs...
As already mentionned by Carlos, the env has to be defined (ORACLE_HOME if you use it , PATH...)

Good luck
Victor

Re: Crontab, Startup scripts

Andreas D. Skjervold — Thu, 25 Jan 2001 13:31:55 GMT

Hi!
You might also want to edit your oratab file to read:
::Y
if your scripts is utilizing the Oracle-supplied scripts dbstart / dbshut located in $ORACLE_HOME/bin
Y in the last column starts the corresponding db at system start(assuming the rest of the scripts are set up correct).

Andreas

Re: Crontab, Startup scripts

Joseph C. Denman — Fri, 26 Jan 2001 17:00:08 GMT

As far as the cron....As stated earlier, I would check for the latest patch.

On the Oracle start/stop. I have attached a copy of my /sbin/init.d/oracle file I use to start and stop. This uses the oracle release dbshut and dbstart.

You will need to put your links in your respective rc directory. Plus you will need the file /etc/rc.config.d/oracle stating ORACLE_START=1

Re: Crontab, Startup scripts

Joseph C. Denman — Fri, 26 Jan 2001 17:11:12 GMT

Oh...The script uses oracle7 as oracle. You will need to modify it to oracle or (the oracle software owner)

Also, you need to make sure the /etc/oratab file has a Y at the end of the instances you want started and stopped.

Hope this helps.

Re: Crontab, Startup scripts

Kurtkarl — Fri, 26 Jan 2001 18:25:13 GMT

Tought it might help for your startup script.

Try to check also the actual script file mode/permission if it's executable.