It looks like it doesn't work on suse servers.
After 4 days in this autostartup task we finally decided to forget it
and put the task to the 24/7 support team to manually start the service
if, for some reason, the server shuts down or needs to be restarted.
The frustrating thing here is we cannot get support, Oracle told us that
it was some kind of a bug coming from Novell and now we don't have a
clue of what the problem really is.
Thank you for your time.
On Wed, 2006-10-25 at 09:38 -0400, Jayme Puza wrote:
> We did 2 things to get this to work on one of our redhat servers. First
> we had to replace the "su - oracle" in /etc/init.d/dbora to
> /sbin/runuser:
>
> #!/bin/bash
> #
> # chkconfig: 35 99 10
> # description: Starts and stops Oracle processes
> #
> # Set ORA_HOME to be equivalent to the $ORACLE_HOME
> # from which you wish to execute dbstart and dbshut;
> #
> # Set ORA_OWNER to the user id of the owner of the
> # Oracle database in ORA_HOME.
> #
> ORA_HOME=/home/app/oracle/product/10.2
> ORA_OWNER=oracle
> case "$1" in
> 'start')
> # Start the Oracle databases and the listener for all
> # databases in the oratab file:
> # The following command assumes that the oracle login
> # will not prompt the user for any values
> #/etc/init.d/init.cssd run &
> /sbin/runuser $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME"
> touch /var/lock/subsys/dbora
> ;;
> 'stop')
> # Stop the Oracle databases and the listeners for databases
> # found in the oratab file:
> # The following command assumes that the oracle login
> # will not prompt the user for any values
> /sbin/runuser $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME"
> rm -f /var/lock/subsys/dbora
> ;;
> esac
> # End of script dbora
>
> Then we changed /etc/inittab to:
>
> l0:0:wait:/etc/rc.d/rc 0
> l1:1:wait:/etc/rc.d/rc 1
> l2:2:wait:/etc/rc.d/rc 2
> h1:35:respawn:/etc/init.d/init.cssd run >/dev/null 2>&1 </dev/null
> l3:3:wait:/etc/rc.d/rc 3
> l4:4:wait:/etc/rc.d/rc 4
> l5:5:wait:/etc/rc.d/rc 5
> l6:6:wait:/etc/rc.d/rc 6
>
>
> Hopefully this will work for you too!
>
> Jayme Puza
> RemoteDBA Experts
> Unix Systems Administrator
>
> Contemporary Technologies, Inc.
> 4 Gateway Center, Suite 600
> 444 Liberty Avenue
> Pittsburgh, Pa 15222-1223
>
> work: 412-208-1679
> Cell: 412-715-4904
> Fax: 412-208-1654
> Email: jpuza@(protected)
>
> This message may contain privileged or confidential information and is
> intended only for the individuals named. If you are not a named
> addressee you should not disclose, disseminate, distribute or copy this
> e-mail. If you have received this e-mail by mistake please notify the
> sender immediately by e-mail and delete this e-mail from your system.
> You should rely on your own virus checking programs and procedures for
> checking any attachments. Any views expressed in this message are those
> of the individual sender, except where the message states otherwise and
> the sender is authorized to state them to be the views of any such
> entity.
>
>
> -----Original Message-----
> From: Alexei_Roudnev [mailto:Alexei_Roudnev@(protected)]
> Sent: Tuesday, October 24, 2006 8:51 PM
> To: Arun Singh; suse-oracle@(protected)
> Subject: Re: [suse-oracle] SLES9 SP3, Oracle 10gR2 Autostart problem
>
> No, THERE IS NOT a good location in inittab at all.
>
> Even when we put in into the proper place, it stil dont work properly,
> becasue it shut down BEFORE system complete to run all rc files.
> The only proper place is /etc/init.d/ dierctory, with a proper
> dependencies.
>
>
> ----- Original Message -----
> From: "Arun Singh" <Arun.Singh@(protected)>
> To: <suse-oracle@(protected)>
> Sent: Tuesday, October 24, 2006 10:59 AM
> Subject: Re: [suse-oracle] SLES9 SP3, Oracle 10gR2 Autostart problem
>
>
> > "Alexei_Roudnev" <Alexei_Roudnev@(protected):
> > > The only GOOD way, which I see, is to write new /etc/init.d/asm
> > module and
> > > replace inittab's record by this module.
> >
> > This sounds Oracle bug as it doesn't put inittab entry at correct
> > location.
> >
> > There is not much can be done in orarun, except loop should not be
> > infinite loop.
> >
> > >
> > > Another method (which I sometimes prefer) is
> > > - to change meaning of level3 and 5:
> > > * level3 - system without Oracle
> > > * level5 - system with oracle
> > >
> > > and then start level5 after 3 (and shutdown them in order).
> > >
> > > as a half-measure, you can try to add init.css into the levels 0,1,S
> > - sysem
> > > wil kill css during unmounting disks anyway, so _may be_ it will
> > work.
> > >
> > >
> > > ----- Original Message -----
> > > From: "Arun Singh" <Arun.Singh@(protected)>
> > > To: "Alexei_Roudnev" <Alexei_Roudnev@(protected)>;
> > > <suse-oracle@(protected)>
> > > Sent: Tuesday, October 24, 2006 9:35 AM
> > > Subject: Re: [suse-oracle] SLES9 SP3, Oracle 10gR2 Autostart problem
> > >
> > >
> > >> Alexei,
> > >>
> > >> Agree, we need to fix this section for ASM instances as I don't
> > want
> > >> server to appear hung due to this loop. It should exit after some
> > number
> > >> of tries.
> > >>
> > >> Do you mind getting better fix for this?
> > >>
> > >> Thanks,
> > >> Arun
> > >>
> > >> >>> On 10/24/2006 at 9:27 AM, in message
> > >> <03cf01c6f789$5e62c7b0$6401a8c0@(protected)>,
> > >> "Alexei_Roudnev" <Alexei_Roudnev@(protected):
> > >> > Btw, Arun - it resolves startup problem, but it can't resolve
> > >> shutdown
> > >> > problem (asm fail before database is stopped gracefully).
> > >> >
> > >> >
> > >> > ----- Original Message -----
> > >> > From: "Arun Singh" <Arun.Singh@(protected)>
> > >> > To: <suse-oracle@(protected)>
> > >> > Sent: Tuesday, October 24, 2006 8:52 AM
> > >> > Subject: Re: [suse-oracle] SLES9 SP3, Oracle 10gR2 Autostart
> > problem
> > >> >
> > >> >
> > >> >> <efren.yevale@(protected):
> > >> >> > Good day.
> > >> >> >
> > >> >> > We have a new server with SLES9 SP3 to run Oracle 10gR2
> > >> exclusively.
> > >> >> The
> > >> >> > installation was smooth starting with SP3 CD1 and the Oracle
> > >> database
> > >> >> is
> > >> >> > running great with ASM, however, we have to start the database
> > >> >> manually.
> > >> >> >
> > >> >> > A quick view at /etc/oratab showed the autostart field with
> > "N"
> > >> so
> > >> >> we
> > >> >> > changed it to "Y" expecting to see the database starting on
> > every
> > >> >> boot
> > >> >> > but something is causing the message "Waiting 20 seconds for
> > CRS
> > >> >> daemon"
> > >> >> > to fill the startup screen and the database never becomes
> > >> available.
> > >> >> >
> > >> >> > There are two instances:
> > >> >> > +ASM:/opt/oracle/product/10gR2:N
> > >> >> > entdb:/opt/oracle/product/10gR2:N
> > >> >> >
> > >> >> > We are using x86_64 versions of SLES and Oracle database, yast
> > >> was
> > >> >> used
> > >> >> > to update OS packages.
> > >> >> >
> > >> >> >
> > >> >>
> > >> >> Try following:
> > >> >>
> > >> >> 1. Comment out line # 456 to 466 in /etc/init.d/oracle - which
> > >> checks
> > >> >> about ASM status.
> > >> >>
> > >> >> 2. Edit /etc/inittab (to adjust init.cssd location)
> > >> >>
> > >> >> l2:2:wait:/etc/init.d/rc 2
> > >> >> h1:35:respawn:/etc/init.d/init.cssd run >/dev/null 2>&1
> > >> </dev/null
> > >> >> l3:3:wait:/etc/init.d/rc 3
> > >> >>
> > >> >> Hope this will help,
> > >> >> Arun
> >
> >
> > --
> > To unsubscribe, email: suse-oracle-unsubscribe@(protected)
> > For additional commands, email: suse-oracle-help@(protected)
> > Please see http://www.suse.com/oracle/ before posting
> >
> >
>
>
> --
>
>
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
