Results 1 to 2 of 2
Hi All,
I have a dbora script that i've been having fits with. Running RH EL 5.
#!/bin/sh -x
# chkconfig: 345 95 10
# description: Oracle auto start-stop script.
...
- 06-21-2011 #1Just Joined!
- Join Date
- Jun 2011
- Posts
- 4
starting Oracle database via dbora failing
Hi All,
I have a dbora script that i've been having fits with. Running RH EL 5.
#!/bin/sh -x
# chkconfig: 345 95 10
# description: Oracle auto start-stop script.
#
if [ ! -f /oracle/taxdb/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
fi
case "$1" in
'start')
# Start the Oracle databases:
# The following command assumes that the oracle login
# will not prompt the user for any values
su - oracle -c "/oracle/taxdb/bin/lsnrctl start"
su - oracle -c "/oracle/taxdb/bin/dbstart $ORACLE_HOME"
touch /var/lock/subsys/dbora
;;
'stop')
# Stop the Oracle databases:
# The following command assumes that the oracle login
# will not prompt the user for any values
su - oracle -c "/oracle/taxdb/bin/dbshut $ORACLE_HOME"
su - oracle -c "/oracle/taxdb/bin/lsnrctl stop"
rm -f /var/lock/subsys/dbora
;;
esac
When I boot the server, it comes up, BUT the only thing that has been done from the script is the lsnrctl start line. Oddly, it appears as though the only thing that was really done was "su -oracle" and the rest sent to a sub-shell or something. I do know that after a boot, what is running is:
{taxwaredev01.concur.concurtech.org} /home/oracle -> ps -ef|grep lsnr
root 6536 5807 0 13:56 pts/1 00:00:00 su - oracle -c /oracle/taxdb/bin/lsnrctl start
oracle 6537 6536 0 13:56 ? 00:00:00 -ksh -c /oracle/taxdb/bin/lsnrctl start
oracle 6554 6552 0 13:56 ? 00:00:00 grep lsnr
And when I kill these the listener actually does start and the next line in the dbora script fires off. It too does the same thing. Has anyone seen this type of behavior before?
And no...I've found nothing on Oracle's site that addresses this.
Thanks for any tips here.
- 06-22-2011 #2Just Joined!
- Join Date
- Jun 2011
- Posts
- 4
problem solved...
In oracle user's .profile, the last line was "ksh -o vi", which was creating another shell environment. I removed that and all's well now.


Reply With Quote