Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Help:stop/start OAS 4 with crontab
Dear Oracle Guru,
I use root's crontab to do cold backup every night for our server Edademo (Solaris 2.6). The backup script has been working fine with the
old environment when we had an oracle 7.3.4.3 database and OAS 3.0.1
(the two products were installed by user oracle). Two days ago, I
created an oracle4 account (belongs to dba group) to install OAS 4.0.7
(I did not de-install OAS 3.0.1 as oracle, but merely deleted the
listeners' directories created for OAS 3.0). Our application (using
7.3.4.2 rdbms on the same server) came up correctly with the new OAS
4.0.7.
Then, I started to modify the backup script and ran into problem. In
order to test, I have a script called oas40status that basically first
defines the environment variables as recorded in the
$ORAWEB_HOME/install/owsenv_bsh.sh during the install, and then check
the
status with the following statement:
su - oracle4 -c "$ORAWEB_HOME/bin/owsctl status"
What I am experiencing is when oas40status is executed as a shell script it works fine, when executed through root crontab, there are errors.
$ whoami
oracle4
$ su root [or su - root]
# cd /etc/test # ./oas40status --- no problem # crontab -l
When I examine the oas40status.log, there are error messages:
ld.so.l:
/u01/app/oracle4/product/8.0.4/ows/4.0/bin/owsctl:fatal:liborb.so: op
en failed: No such file or directory Killed
What am I missing? I could not make it work under root crontab. As a work around, I use the oracle4 crontab to stop and start the OAS processes before and after the backup job was kicked off by the root crontab. However, I'd like to know how to make it work under the root crontab.
Your reply will be very much appreciated. When reply, please also e-mail to huy_at_ncr.disa.mil so I can read it at work.
Thanks,
Ying-fen Hu Received on Tue Jul 27 1999 - 20:30:06 CDT