OraFAQ Forum: Server Administration » Listener Won't Start from Startup Script

Home » RDBMS Server » Server Administration » Listener Won't Start from Startup Script - 8.1.7.4 Solaris 8

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Listener Won't Start from Startup Script - 8.1.7.4 Solaris 8 [message #55860]

Thu, 20 February 2003 08:01

Roger
Messages: 10
Registered: September 2000

Junior Member

Alright, I have 8 instances running on 8.1.7.4 on Solaris 8, on an Ultra Ent 450. The startup script in /etc/init.d is:

#!/bin/sh
#
ORACLE_HOME=/app/oracle/product/8.1.7
ORACLE_BASE=/app/oracle
ORACLE_SID=test
PATH=$PATH:$ORACLE_HOME/bin
export ORACLE_HOME ORACLE_BASE ORACLE_SID PATH

case $1 in
start)
su - oracle -c $ORACLE_HOME/bin/dbstart
su - oracle -c "/app/oracle/product/8.1.7/bin/lsnrctl start"

exit 0
;;

stop)
su - oracle -c "$ORACLE_HOME/bin/lsnrctl stop"
su - oracle -c $ORACLE_HOME/bin/dbshut
;;

esac

If I start the listener manually, as the Oracle user, using 'lsnrctl start' the listener starts fine. But, when this script runs, (as root) it will not start, I get the following garbage:

SVRMGR runs and starts my 8 instances, and then:

# cd /
# cat oracleout &#124more

LSNRCTL for Solaris: Version 8.1.7.4.0 - Production on 20-FEB-2003 09:46:38

(c) Copyright 1998 Oracle Corporation. All rights reserved.

Message 1053 not found; No message file for product=network, facility=TNSTNS-125
41: Message 12541 not found; No message file for product=network, facility=TNS
TNS-12560: Message 12560 not found; No message file for product=network, facili
ty=TNS
TNS-00511: Message 511 not found; No message file for product=network, facilit
y=TNS
Solaris Error: 2: No such file or directory
Message 1053 not found; No message file for product=network, facility=TNSTNS-125
41: Message 12541 not found; No message file for product=network, facility=TNS
TNS-12560: Message 12560 not found; No message file for product=network, facili
ty=TNS
TNS-00511: Message 511 not found; No message file for product=network, facilit
y=TNS
Solaris Error: 146: Connection refused

I've search high and low on these error messages, but none of the instances of the error I've found have anything to do with my situation. I'm hoping the bright souls here can help! If you don't mind please e-mail me any replies. Thanks!

Report message to a moderator

Re: Listener Won't Start from Startup Script - 8.1.7.4 Solaris 8 [message #55862 is a reply to message #55860]

Thu, 20 February 2003 08:20

Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille

Senior Member
Account Moderator

use this script in init.d

#!/bin/sh

        case "$1" in
                start)
                        echo -n "Starting Oracle"
                        su - oracle -c dbstart
                        echo "."
                        ;;
                stop)
                        echo -n "Stopping Oracle"
                        su - oracle -c dbshut
                        echo "."
                        ;;
                *)
                        echo "Usage: /etc/init.d/ora_db start&#124stop"
                        exit 1
                        ;;
        esac

----------------------------------------------------------------------

now add the lsnrctl start in you dbstart and
lsnrctl shut in your dbshut (as shown in top of dbstart script)
make sure u have SET UR ORATAB

----------------------------------------------------------------------

lsnrctl start
#### added by Mahesh Rajendran..start the apache service for DMEA fink lab
/u01/app/oracle/product/appserver9i/Apache/Apache/bin/httpdsctl start
ORATAB=/var/opt/oracle/oratab

Report message to a moderator

Re: Listener Won't Start from Startup Script - 8.1.7.4 Solaris 8 [message #55880 is a reply to message #55860]

Fri, 21 February 2003 08:28

Uwe
Messages: 260
Registered: February 2003
Location: Zürich, Switzerland

Senior Member

One suggestion far from Oracle. I know that Sun served a Patch for su'ing. I did not actually know which patchport it is, but we've problems to su to one of our SUN's because there will be opened two concurrent logins. That should be a SUN-Prob

Report message to a moderator

Previous Topic:	INSERT WITH & AS FIELD VALUE FAILS
Next Topic:	oracle odbc

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Feb 14 07:21:12 CST 2025