Re: Listener won't start at startup

Steve,

1. "su -" resets all environment variables, and therefore unsets the ORACLE_HOME variable. You need just "su oracle -c ..." This also prevents the ".profile" from the UNIX user 'oracle' to be run, so other side effects might then occur. To test, use "env" or "export" (both without arguments) as the command after "su -c", to see the environment variable that remain.
2. You don't need the & at the end of the line since the "lsnrctl" command is not the actual listener, but only the command that starts the listenet. Once the listener is started, "lsnrctl" itself exits.

        Erwin

> > [snip]
> > su - oracle -c $ORACLE_HOME/bin/lsnrctl start &
> >
> > to my Solaris dbora startup script. The database will start, but the
> > listener fails. Not sure if it has anything to do with the fact that
> > even though the database startup call is first, the shell script
> > doesn't wait till it returns to execute the next command. I get the
> > following:
> > [snip]
> > Message 850 not found; No message file for product=network,
> > facility=NL
> > [snip]
Received on Mon Aug 28 2000 - 18:14:52 CDT