More info on SLES10 needed

Hello to everyone

 

I have been following this thread about SLES10 problems,
about RedHat
being preferred by dba's/sysadmins...

 

Could somebody give more details on problems with Suse SLES
10? We have
SLES10 deployed on number of servers, hosting 10.2 database
- both rac
and single instance. So far we haven't seen any problems.
However, after
reading some posts I became concerned so I will appreciate
if somebody
could shed some light.

 

Thank you in advance,

Vladimir 


____________________________________________________________
__________
This email has been scanned by the MessageLabs Email
Security System.
For more information please visit http://www.messagela
bs.com/email 
____________________________________________________________
__________

On Tuesday 14 August 2007 00:55, you wrote:
Just my own personal opinion, i'd rather support Suse than
Red Hat.  The 
biggest issue for me, is the ease of administration.  The
YaST user 
interface, though it isn't perfect, is a lot better than
anything that I have 
found under RedHat.  Currently I having to support some RH
4.5 servers and am 
constantly searching for YaST.

On a previous project we had SLES 9 installed, and running
without any 
problems.  I'm still waiting to get to a project that has
SLES10.

Just my .02

> Hello to everyone
>
>
>
> I have been following this thread about SLES10
problems, about RedHat
> being preferred by dba's/sysadmins...
>
>
>
> Could somebody give more details on problems with Suse
SLES 10? We have
> SLES10 deployed on number of servers, hosting 10.2
database - both rac
> and single instance. So far we haven't seen any
problems. However, after
> reading some posts I became concerned so I will
appreciate if somebody
> could shed some light.
>
>
>
> Thank you in advance,
>
> Vladimir
>
>
>
____________________________________________________________
__________
> This email has been scanned by the MessageLabs Email
Security System.
> For more information please visit http://www.messagela
bs.com/email
>
____________________________________________________________
__________

-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting

Thanks Vladmir,

You are the perfect example that there not many issue with
Oracle 10gR2/SLES10 setup. We have many customers  with same
comments. If there are any issue, Novell/Oracle will work to
iron out.

Only major problem which I would like to mention is
"Oracle 9iR2 is not supported on SLES10 due to
libthread issue mentioned earlier". 

For newer Oracle products i.e. Oracle 10g or 11g SLES10
(SP1) is better choice.

-Arun
 
>>> On 8/13/2007 at 9:55 PM, "Vladimir
Barac" <vbaracAlghanim.com> wrote:
> Hello to everyone
> 
>  
> 
> I have been following this thread about SLES10
problems, about RedHat
> being preferred by dba's/sysadmins...
> 
>  
> 
> Could somebody give more details on problems with Suse
SLES 10? We have
> SLES10 deployed on number of servers, hosting 10.2
database - both rac
> and single instance. So far we haven't seen any
problems. However, after
> reading some posts I became concerned so I will
appreciate if somebody
> could shed some light.
> 
>  
> 
> Thank you in advance,
> 
> Vladimir 
> 
> 
>
____________________________________________________________
__________
> This email has been scanned by the MessageLabs Email
Security System.
> For more information please visit http://www.messagela
bs.com/email 
>
____________________________________________________________
__________




--
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting

May be - but I run DataGuard performance test between SLES10
and RHEL4, and 
SLES10 always lost syncronization because of
async io with network. IT did not happened with SLES0 or
RHEL4.

Other hassle with SLES10 rely to update system, it became
better but still 
not 'you' server and is very slow. On the other hand, it is
compatible with 
OpenSuse so you can install a lot of (uncertified but very
good) software 
directly by yast2.



----- Original Message ----- 
From: "Arun Singh" <Arun.Singhnovell.com>
To: "Vladimir Barac" <vbaracAlghanim.com>; <suse-oraclesuse.com>
Sent: Tuesday, August 14, 2007 7:29 AM
Subject: Re: [suse-oracle] More info on SLES10 needed


Thanks Vladmir,

You are the perfect example that there not many issue with
Oracle 
10gR2/SLES10 setup. We have many customers  with same
comments. If there are 
any issue, Novell/Oracle will work to iron out.

Only major problem which I would like to mention is
"Oracle 9iR2 is not 
supported on SLES10 due to libthread issue mentioned
earlier".

For newer Oracle products i.e. Oracle 10g or 11g SLES10
(SP1) is better 
choice.

-Arun

>>> On 8/13/2007 at 9:55 PM, "Vladimir
Barac" <vbaracAlghanim.com> wrote:
> Hello to everyone
>
>
>
> I have been following this thread about SLES10
problems, about RedHat
> being preferred by dba's/sysadmins...
>
>
>
> Could somebody give more details on problems with Suse
SLES 10? We have
> SLES10 deployed on number of servers, hosting 10.2
database - both rac
> and single instance. So far we haven't seen any
problems. However, after
> reading some posts I became concerned so I will
appreciate if somebody
> could shed some light.
>
>
>
> Thank you in advance,
>
> Vladimir
>
>
>
____________________________________________________________
__________
> This email has been scanned by the MessageLabs Email
Security System.
> For more information please visit http://www.messagela
bs.com/email
>
____________________________________________________________
__________




-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting



-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting

Ok.

1) SLES10 SP1 - when running Oracle data guard in SYNC mode,
lost log 
synchronization, message is 'async io error' (on network I
think). Never 
happen with SLES9 or RHEL4.

2) SLES10 SP1 - if using iSCSI, then no any way to mount
file systems 
(_netdev not implemented but 'hotplug' don't work with
multipath);

3) New Open-iSCSI means _no multiport support, need to run
multipath_; 
poorly documented;

4) (again) iSCSI is not aliened with LVM and LVM is not
aligned with 
multipath. So you must configure everything manually.

5) Network Update - no normal (by yast) way to configure
update server.

6) Installation - when few installation sources are
configured, yast2 
install menu starts about 5 - 10 minutes because it reread
all sources. 
Getting source to DOWN state do not help.

7) No support for older thread library (it is temporary
problem, of course, 
because this library is not recommended).

8) You can't use LVM with yast if you create physical
volumes on the whole 
devices (not on the partitions).

9) Heartbeat2 - SLES9 had full support for heartbeat in
yast2; SLES10 have 
only a very primitive support there.

10) No standard way to control duplex setting on the
interfaces (but it's a 
problem of all SuSe-s).

Of course, working with RHEL is all hassle:
- bad rpm naming cause a problem in determining _what is
really installed_;
- no integrated installation and ad,ministration system,
makes support 
really guru-s task;
- software set is poor by default;
- no AppArmor (SELinix is not equivalent replacement).
- numerous 'druids', 'helpers', 'configers' makes
administrative tasks a 
really adventure (and most people roll back to 'vi' when
working with RHEL).

But it works. LVM is aligned with multipath, and both with
iSCSI, and fstab 
supports _netdev. No any problems with DataGuard streams; no
any problems 
with LVM, no any problems with async io, no forgotten
'reboot on panic' 
settings... Looks as old, iron made, very primitive but
reliable car.
I hoped that it make space for better systems few years agom
but it never 
happened, and one reason (of many) is Novell policy with new
releases.


----- Original Message ----- 
From: "Vladimir Barac" <vbaracAlghanim.com>
To: <suse-oraclesuse.com>; <Arun.Singhnovell.com>
Sent: Monday, August 13, 2007 9:55 PM
Subject: [suse-oracle] More info on SLES10 needed


Hello to everyone



I have been following this thread about SLES10 problems,
about RedHat
being preferred by dba's/sysadmins...



Could somebody give more details on problems with Suse SLES
10? We have
SLES10 deployed on number of servers, hosting 10.2 database
- both rac
and single instance. So far we haven't seen any problems.
However, after
reading some posts I became concerned so I will appreciate
if somebody
could shed some light.



Thank you in advance,

Vladimir


____________________________________________________________
__________
This email has been scanned by the MessageLabs Email
Security System.
For more information please visit http://www.messagela
bs.com/email
____________________________________________________________
__________ 


-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting

I have communicated these valuable input to SUSE Development
team to see what can be done in future (SLES10 SP2 or
SLES11).

Thanks,
Arun

Read response to #10:

.....................................
> > > 10) No standard way to control duplex setting
on the interfaces (but it's a 
> > > problem of all SuSe-s).
> 
> ethtool ethX duplex half|full
> should work on nearly all drivers now
> 
> But in general it's not recommended to force that
anymore because
> it often confuses switches. Better to trust the
autonegotiation.

and since this is in SLE-10, it's even configurable:

------------------------------------------------------------
-----------
Mon Dec 19 15:43:40 CET 2005 - zozsuse.de 

- Version 0.42.0
[...]
- New ifcfg-* variable ETHTOOL_OPTIONS: if not empty ifup
will call
  ethtool with exactly this options.
------------------------------------------------------------
-----------

.....................................

>>> On 8/14/2007 at 11:24 AM,
"Alexei_Roudnev" <Alexei_Roudnevexigengroup.com>
wrote:
> Ok.
> 
> 1) SLES10 SP1 - when running Oracle data guard in SYNC
mode, lost log 
> synchronization, message is 'async io error' (on
network I think). Never 
> happen with SLES9 or RHEL4.
> 
> 2) SLES10 SP1 - if using iSCSI, then no any way to
mount file systems 
> (_netdev not implemented but 'hotplug' don't work with
multipath);
> 
> 3) New Open-iSCSI means _no multiport support, need to
run multipath_; 
> poorly documented;
> 
> 4) (again) iSCSI is not aliened with LVM and LVM is not
aligned with 
> multipath. So you must configure everything manually.
> 
> 5) Network Update - no normal (by yast) way to
configure update server.
> 
> 6) Installation - when few installation sources are
configured, yast2 
> install menu starts about 5 - 10 minutes because it
reread all sources. 
> Getting source to DOWN state do not help.
> 
> 7) No support for older thread library (it is temporary
problem, of course, 
> because this library is not recommended).
> 
> 8) You can't use LVM with yast if you create physical
volumes on the whole 
> devices (not on the partitions).
> 
> 9) Heartbeat2 - SLES9 had full support for heartbeat in
yast2; SLES10 have 
> only a very primitive support there.
> 
> 10) No standard way to control duplex setting on the
interfaces (but it's a 
> problem of all SuSe-s).
> 
> Of course, working with RHEL is all hassle:
> - bad rpm naming cause a problem in determining _what
is really installed_;
> - no integrated installation and ad,ministration
system, makes support 
> really guru-s task;
> - software set is poor by default;
> - no AppArmor (SELinix is not equivalent replacement).
> - numerous 'druids', 'helpers', 'configers' makes
administrative tasks a 
> really adventure (and most people roll back to 'vi'
when working with RHEL).
> 
> But it works. LVM is aligned with multipath, and both
with iSCSI, and fstab 
> supports _netdev. No any problems with DataGuard
streams; no any problems 
> with LVM, no any problems with async io, no forgotten
'reboot on panic' 
> settings... Looks as old, iron made, very primitive but
reliable car.
> I hoped that it make space for better systems few years
agom but it never 
> happened, and one reason (of many) is Novell policy
with new releases.
> 
> 
> ----- Original Message ----- 
> From: "Vladimir Barac" <vbaracAlghanim.com>
> To: <suse-oraclesuse.com>;
<Arun.Singhnovell.com>
> Sent: Monday, August 13, 2007 9:55 PM
> Subject: [suse-oracle] More info on SLES10 needed
> 
> 
> Hello to everyone
> 
> 
> 
> I have been following this thread about SLES10
problems, about RedHat
> being preferred by dba's/sysadmins...
> 
> 
> 
> Could somebody give more details on problems with Suse
SLES 10? We have
> SLES10 deployed on number of servers, hosting 10.2
database - both rac
> and single instance. So far we haven't seen any
problems. However, after
> reading some posts I became concerned so I will
appreciate if somebody
> could shed some light.
> 
> 
> 
> Thank you in advance,
> 
> Vladimir
> 
> 
>
____________________________________________________________
__________
> This email has been scanned by the MessageLabs Email
Security System.
> For more information please visit http://www.messagela
bs.com/email 
>
____________________________________________________________
__________ 



--
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting

We found, that while it is always better to keep Ethernet in
'auto' mode 
when working with 1 GB switches/ports, it is almost always
unpredictable 
with older 100MB ports and switches (after we had 10 - 20
cases when 
everything worked well after set up but broke after switch
or server have 
been rebooted, or just after patch cable reconnection).

New option is fine (RHEL have it for a long time).

----- Original Message ----- 
From: "Arun Singh" <Arun.Singhnovell.com>
To: <suse-oraclesuse.com>
Sent: Wednesday, August 15, 2007 10:41 AM
Subject: Re: [suse-oracle] More info on SLES10 needed


I have communicated these valuable input to SUSE Development
team to see 
what can be done in future (SLES10 SP2 or SLES11).

Thanks,
Arun

Read response to #10:

.....................................
> > > 10) No standard way to control duplex setting
on the interfaces (but 
> > > it's a
> > > problem of all SuSe-s).
>
> ethtool ethX duplex half|full
> should work on nearly all drivers now
>
> But in general it's not recommended to force that
anymore because
> it often confuses switches. Better to trust the
autonegotiation.

and since this is in SLE-10, it's even configurable:

------------------------------------------------------------
-----------
Mon Dec 19 15:43:40 CET 2005 - zozsuse.de

- Version 0.42.0
[...]
- New ifcfg-* variable ETHTOOL_OPTIONS: if not empty ifup
will call
  ethtool with exactly this options.
------------------------------------------------------------
-----------

.....................................

>>> On 8/14/2007 at 11:24 AM,
"Alexei_Roudnev" 
>>> <Alexei_Roudnevexigengroup.com>
wrote:
> Ok.
>
> 1) SLES10 SP1 - when running Oracle data guard in SYNC
mode, lost log
> synchronization, message is 'async io error' (on
network I think). Never
> happen with SLES9 or RHEL4.
>
> 2) SLES10 SP1 - if using iSCSI, then no any way to
mount file systems
> (_netdev not implemented but 'hotplug' don't work with
multipath);
>
> 3) New Open-iSCSI means _no multiport support, need to
run multipath_;
> poorly documented;
>
> 4) (again) iSCSI is not aliened with LVM and LVM is not
aligned with
> multipath. So you must configure everything manually.
>
> 5) Network Update - no normal (by yast) way to
configure update server.
>
> 6) Installation - when few installation sources are
configured, yast2
> install menu starts about 5 - 10 minutes because it
reread all sources.
> Getting source to DOWN state do not help.
>
> 7) No support for older thread library (it is temporary
problem, of 
> course,
> because this library is not recommended).
>
> 8) You can't use LVM with yast if you create physical
volumes on the whole
> devices (not on the partitions).
>
> 9) Heartbeat2 - SLES9 had full support for heartbeat in
yast2; SLES10 have
> only a very primitive support there.
>
> 10) No standard way to control duplex setting on the
interfaces (but it's 
> a
> problem of all SuSe-s).
>
> Of course, working with RHEL is all hassle:
> - bad rpm naming cause a problem in determining _what
is really 
> installed_;
> - no integrated installation and ad,ministration
system, makes support
> really guru-s task;
> - software set is poor by default;
> - no AppArmor (SELinix is not equivalent replacement).
> - numerous 'druids', 'helpers', 'configers' makes
administrative tasks a
> really adventure (and most people roll back to 'vi'
when working with 
> RHEL).
>
> But it works. LVM is aligned with multipath, and both
with iSCSI, and 
> fstab
> supports _netdev. No any problems with DataGuard
streams; no any problems
> with LVM, no any problems with async io, no forgotten
'reboot on panic'
> settings... Looks as old, iron made, very primitive but
reliable car.
> I hoped that it make space for better systems few years
agom but it never
> happened, and one reason (of many) is Novell policy
with new releases.
>
>
> ----- Original Message ----- 
> From: "Vladimir Barac" <vbaracAlghanim.com>
> To: <suse-oraclesuse.com>;
<Arun.Singhnovell.com>
> Sent: Monday, August 13, 2007 9:55 PM
> Subject: [suse-oracle] More info on SLES10 needed
>
>
> Hello to everyone
>
>
>
> I have been following this thread about SLES10
problems, about RedHat
> being preferred by dba's/sysadmins...
>
>
>
> Could somebody give more details on problems with Suse
SLES 10? We have
> SLES10 deployed on number of servers, hosting 10.2
database - both rac
> and single instance. So far we haven't seen any
problems. However, after
> reading some posts I became concerned so I will
appreciate if somebody
> could shed some light.
>
>
>
> Thank you in advance,
>
> Vladimir
>
>
>
____________________________________________________________
__________
> This email has been scanned by the MessageLabs Email
Security System.
> For more information please visit http://www.messagela
bs.com/email
>
____________________________________________________________
__________



-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting



-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting