listener will not start automatically at boot time

Quote:

---

Originally posted by jiong
03-DEC-2001 16:54:16 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=dino)(USER=oracle))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=LISTENER) (VERSION=135294976)) * stop * 0
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dino)(PORT=1521)))

---

This is telling you that a lsnrctl stop was issued. Check your script to make sure 'stop' and 'start' are cleanly seperated.

It could also be that you have to specify the TNS_ADMIN=$ORACLE_HOME/network/admin

To point to the correct listener.ora file path.

Sam

I switched the preceedence of the operation of database and listener in the dbora file, database startup but listener doesn't.

I droped '&' in the dbora file and it also doesn't help for my problem.

Thank you,
Jiong

Check your /etc/rc#.d files to see that the file under /etc/init.d/dbora is the one that gets called at boot time. It could also be that its calling different file from that of the dbora from the init.d.

Sam

I add TNS_ADMIN=$ORACLE_HOME/network/admin in the .profile but same thing, db startup not listener.

Jeff, what do you mean 'Check your script to make sure 'stop' and 'start' are cleanly seperated'? You mean the dbora file? What problem do you suspect based on the information from the listener.log file?

Thanks,
Jiong

Hi, Sam,

The files under /etc/rc0.d and /etc/rc2.d all link to /etc/init.d/dbora.

Jiong

Jiong,

It's a long shot, but do you have the following in your .profile for the oracle user?

"/usr/openwin/bin/openwin"


If you have please comment it out and see if it solves your problem.

Also, while you are at it, please export the env variables in your dbora script (just to be sure!).

-amar

Hi

Try this, i hope it works.

Backup your dbstart script and add the lsnrctl start line after EOF

Eg:
connect internal
startup
EOF
lsnrctl start; --- you should add this line after EOF

Thanks

Hi, Guys,

Based on suggestion from Nagesh, I add 'lsnrctl start' line after EOF in dbstart file and now both db and listener start automatically after reboot the machine. I thank you all for helping me out and covering everything. Also my appreciation goes to dbasupport.com.

Jiong

I personally would not go on with altering the default scripts. The reason was that, if I change it now, I know that it works fine now, but when I get to do the next upgrade, it will fail again. So at that time if I could remember this change, well. Otherwise it would be another long struggle like this, to find out what was different. Say another case that where you haven't documented this working procedure, then your successor would have to break his heads on finding the cause of it. I would rather spend some time with oracle to nail the problem on what is causing this trouble and fix it.

This is only an opinion.

Sam