> -Original Message-
> From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-
> boun...@oss.oracle.com] On Behalf Of Sunil Mushran
> Sent: Tuesday, May 04, 2010 12:30 PM
> To: Werner Flamme
> Cc: ocfs2-users@oss.oracle.com
> Subject: Re: [Ocfs2-users] com
On 05/04/2010 02:42 AM, Werner Flamme wrote:
>
> Thank you. Took a while to get this posting out of spam quarantine :-(
> We had problems here for the last weeks :-(
>
> So, on the SLES10 where I succeeded in building the packages for ocfs2
> and ocfs2-tools from source, I entered this command and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sunil Mushran [26.04.2010 19:26]:
> Werner Flamme wrote:
>> For RHEL there are readyly built packages, why would I build my own
>> packages then? The build worked fine with another SLES10.
>>
>> Yes, ocfs2 is included by SLES. Not SLES 11, of course -
Oh the joy that is SAP ... I love how you have to have a shared file system
from SAP application server to the database server. As far I know it is to put
their scripts/binaries for database maintenance (like backup) on the App
Server. I think it is a terrible hack. (I got similar thoughts about
Werner. I think you're just avoiding what people are telling you. You cannot
have a mixed OCFS2 filesystem shared between EL5 and SLES11. You are
attempting to hack around this obstacle by compiling the EL5 sources on SLES11
but the EL5 source code is not compatible with the SLES kernel. You're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Herbert van den Bergh [27.04.2010 18:23]:
>
> If you're not even in control of the RAC environment, then I doubt
> the administrator of that cluster would be happy to have your
> application servers as part of their database cluster. I don't know
> h
On Tue, 2010-04-27 at 19:08 +0200, Werner Flamme wrote:
> I'd rather
> deinstall the SLES version and switch over to the newer one, but I can't
> compile them. And, especially with SLES 11, there is no OCFS2 included
> in the media. It belongs to an add-on package, that is not yet
> available,
Am 27.04.2010 19:15, schrieb Sunil Mushran:
> Werner Flamme wrote:
>> this is what I do. But since the version on the RAC server is newer
>> than mine, I cannot mount the filesystem (I quoted the error in a
>> previous mail). That's why I try to compile the sources from Oracle.
>> I'd rather deinst
Werner Flamme wrote:
> this is what I do. But since the version on the RAC server is newer than
> mine, I cannot mount the filesystem (I quoted the error in a previous
> mail). That's why I try to compile the sources from Oracle. I'd rather
> deinstall the SLES version and switch over to the new
Am 27.04.2010 18:11, schrieb Sunil Mushran:
> Werner Flamme wrote:
>> Unfortunately, I do not run the Oracle RAC. The RAC runs with Oracle
>> Unbreakable Linux. I am sorry for that decision, but I can't change it.
>>
>> SAP does not forbid to use Oracle's version of Linux. SAP only says that
>> SAP
If you're not even in control of the RAC environment, then I doubt the
administrator of that cluster would be happy to have your application
servers as part of their database cluster. I don't know how many nodes
you have, but let's say you have a 2 node RAC cluster and 4 application
servers.
Werner Flamme wrote:
> Unfortunately, I do not run the Oracle RAC. The RAC runs with Oracle
> Unbreakable Linux. I am sorry for that decision, but I can't change it.
>
> SAP does not forbid to use Oracle's version of Linux. SAP only says that
> SAP systems are fully supported on RHEL or SLES only (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unfortunately, I do not run the Oracle RAC. The RAC runs with Oracle
Unbreakable Linux. I am sorry for that decision, but I can't change it.
SAP does not forbid to use Oracle's version of Linux. SAP only says that
SAP systems are fully supported on RH
Werner Flamme wrote:
> For RHEL there are readyly built packages, why would I build my own
> packages then? The build worked fine with another SLES10.
>
> Yes, ocfs2 is included by SLES. Not SLES 11, of course - it is in the
> separately sold "High Availability" package. But the version included in
Also, if you were to call Novell Support with an OCFS2 related issue,
they most likely would ask you to reproduce it without the EL5 nodes in
the OCFS2 cluster. And the same thing with Oracle. It's not a
supported configuration, so you're on your own.
Since the Oracle database is certified on
In order for the application servers and database servers to share an
OCFS2 filesystem, they must be members of the same cluster. Unless of
course you stop OCFS2 on one server and start it on the other. Then you
might as well just use ext3. Also, I don't think your configuration
would be su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wonder why the OCFS2 versions provided by Oracle and Novell are not
necessarily kept compatible. Some strange policy at Novell's, I guess.
Or not enough money^Wmanpower to go along with every new version.
My application servers aren't a part of RAC.
The OCFS2 versions provided by Oracle and Novell are not necessarily
kept compatible. So there is always a risk of losing access to the
filesystem when you update one or the other. Also, do you really want
to have your application servers be part of your database cluster? You
wouldn't want s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That's a bad idea. I do not like file systems that hang all clients when
the server is on reboot or unreachable. I'd rather a shared filesystem.
Regards,
Werner
Herbert van den Bergh [26.04.2010 17:13]:
>
> That's a bad idea. Use NFS instead.
>
>
That's a bad idea. Use NFS instead.
Thanks,
Herbert.
On 04/26/2010 01:48 AM, Werner Flamme wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sunil Mushran [20.04.2010 18:28]:
>
>> 1.4 tree is only meant to be build against EL5 U2+. Not SLES
>> nor any other kernel tree. SLES9/10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sunil Mushran [20.04.2010 18:28]:
> 1.4 tree is only meant to be build against EL5 U2+. Not SLES
> nor any other kernel tree. SLES9/10/11 already includes ocfs2.
For RHEL there are readyly built packages, why would I build my own
packages then? The bu
1.4 tree is only meant to be build against EL5 U2+. Not SLES
nor any other kernel tree. SLES9/10/11 already includes ocfs2.
Werner Flamme wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> next VM, next trouble :-(
>
> Now I work inside a VM with SLES 11. Configuring ocfs2-1.4.7
22 matches
Mail list logo
