[Ocfs2-users] OCFS2 upgrade question
Herbert van den Bergh
herbert.van.den.bergh at oracle.com
Thu Nov 1 17:00:13 PDT 2012
It looks like this was fixed in 11.2.0.2, so yes, 10.2.0.4 and older
needed the datavolume option.
Thanks,
Herbert.
On 11/01/2012 04:55 PM, Pravin K Patil wrote:
> So does this mean, this option was required for 10g (10.2.0.4) only?
> Just collecting more points for discussion on this point.
>
> Regards,
> Pravin
>
> On Wed, Oct 31, 2012 at 6:17 PM, Herbert van den Bergh
> <herbert.van.den.bergh at oracle.com
> <mailto:herbert.van.den.bergh at oracle.com>> wrote:
>
> Pravin,
>
> With that database version you do not need the datavolume option
> in 1.4 or 1.6.
>
> Thanks,
> Herbert.
>
>
> On 10/31/12 3:16 PM, Pravin K Patil wrote:
>> yes, we use OCFS2 to store Oracle database files and Oracle
>> database version is 11.2.0.2 and we are upgrading it to 11.2.0.3
>> before we are ready to switch from OCFS2 1.4 to 1.6
>>
>> Regards,
>> Pravin
>>
>> On Wed, Oct 31, 2012 at 3:16 PM, Herbert van den Bergh
>> <herbert.van.den.bergh at oracle.com
>> <mailto:herbert.van.den.bergh at oracle.com>> wrote:
>>
>> Pravin,
>>
>> Are you using OCFS2 to store Oracle database files? What
>> database version do you use?
>>
>> Thanks,
>> Herbert.
>>
>>
>> On 10/31/12 11:45 AM, Pravin K Patil wrote:
>>> Just attaching the guide which is by Sunil, refer to page 43
>>> and it says to use the datavolume option but the man page of
>>> mount.ocfs2 says that its depricated parameter. below is
>>> details form man page of mount .ocfs2
>>>
>>> datavolume
>>>
>>> This mount option has been deprecated. It has
>>> been used in the past, to force the Oracle RDBMS to
>>>
>>> issue direct IOs to the hosted data
>>> files, control files, redo logs, archive logs, voting disk,
>>>
>>> cluster registry, etc. It has been deprecated
>>> because it is no longer required. Oracle RDBMS users
>>>
>>> should instead use the init.ora parameter,
>>> filesystemio_options, to enable direct IOs.
>>>
>>>
>>> Just want to be cautious of what we use.
>>>
>>> Regards,
>>> Pravin
>>>
>>> On Tue, Oct 30, 2012 at 1:58 PM, Herbert van den Bergh
>>> <herbert.van.den.bergh at oracle.com
>>> <mailto:herbert.van.den.bergh at oracle.com>> wrote:
>>>
>>> Yes, I'm pretty sure that should be fine.
>>>
>>>
>>> On Oct 30, 2012, at 10:34 AM, Pravin K Patil
>>> <pravinkpatil at gmail.com <mailto:pravinkpatil at gmail.com>>
>>> wrote:
>>>
>>>> thanks for quick response, so does this mean, we can
>>>> even remove that option on current 1.4 OCFS2 and
>>>> prepare new host also without this option and we swing
>>>> the storage and we should be fine?
>>>>
>>>> Regards,
>>>> Pravin
>>>>
>>>> On Tue, Oct 30, 2012 at 12:03 PM, Herbert van den Bergh
>>>> <herbert.van.den.bergh at oracle.com
>>>> <mailto:herbert.van.den.bergh at oracle.com>> wrote:
>>>>
>>>> The datavolume option didn't really do much. It
>>>> just changed the filesystem identifier from OCFS2
>>>> to OCFS V1, so some programs which shall not be
>>>> named would detect it as OCFS and do something
>>>> special. Those programs have long since been
>>>> fixed. And there's absolutely no other functional
>>>> behavior change with or without the parameter.
>>>>
>>>> Thanks,
>>>> Herbert.
>>>>
>>>>
>>>> On 10/30/12 8:08 AM, Pravin K Patil wrote:
>>>>> Hi All,
>>>>>
>>>>> While building new servers, we just noticed that
>>>>> on new servers which are SLES11 SP2 and OCFS2 1.6
>>>>> there is no option for mount as datavolume
>>>>> All our file system which have oracle data files
>>>>> are mounted with this option in current system
>>>>> which is SLES10 SP4 and OCFS 1.4
>>>>>
>>>>> So when we swing the storage, we will have to be
>>>>> careful of this mount option. Any suggestions?
>>>>>
>>>>> Regards,
>>>>> Pravin
>>>>>
>>>>> On Thu, Oct 25, 2012 at 10:54 PM, Pravin K Patil
>>>>> <pravinkpatil at gmail.com
>>>>> <mailto:pravinkpatil at gmail.com>> wrote:
>>>>>
>>>>> Thanks a lot for all the responses, I will
>>>>> reply back with practical experience in few weeks.
>>>>>
>>>>> Pravin
>>>>>
>>>>>
>>>>> On Thu, Oct 25, 2012 at 9:39 PM, Tiger Yang
>>>>> <tiger.yang at oracle.com
>>>>> <mailto:tiger.yang at oracle.com>> wrote:
>>>>>
>>>>> 1.6 could recoginze 1.4 format, but after
>>>>> moving to the new server, maybe need
>>>>> enable new features which only supported
>>>>> by 1.6 via tunefs.ocfs2.
>>>>>
>>>>> Thanks,
>>>>> Tiger
>>>>>
>>>>>
>>>>> On 10/26/2012 01:19 AM, Pravin K Patil wrote:
>>>>>> Hi,
>>>>>>
>>>>>> We have current Oracle RAC running with
>>>>>> OCFS2 1.4.2 on SLES10 SP4 servers.
>>>>>> we are building new RAC nodes with SLES11
>>>>>> SP2 which will have OCFS2 1.6
>>>>>>
>>>>>> We plan to just represent the storage
>>>>>> from current HW to new HW and expect the
>>>>>> new server to recognize all FS and let
>>>>>> Oracle start RAC instances.
>>>>>>
>>>>>> Are there any steps required after/before
>>>>>> presenting the storage to new server.
>>>>>>
>>>>>> Regards,
>>>>>> Pravin
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Ocfs2-users mailing list
>>>>>> Ocfs2-users at oss.oracle.com <mailto:Ocfs2-users at oss.oracle.com>
>>>>>> https://oss.oracle.com/mailman/listinfo/ocfs2-users
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Ocfs2-users mailing list
>>>>> Ocfs2-users at oss.oracle.com <mailto:Ocfs2-users at oss.oracle.com>
>>>>> https://oss.oracle.com/mailman/listinfo/ocfs2-users
>>>>
>>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20121101/560fec2e/attachment-0001.html
More information about the Ocfs2-users
mailing list