"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
