Hi Sumit,
The version is 7.1 and build id is 3209 which is what the conductor or
"virtuoso-t -?" would indicate.
Note, you should also consider using the git repository where there is a
stable/7 branch the equivalent of what is on source forge and also a develop/7
branch which has all the fixes since the stable/7 release, as detailed at:
http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VOSGitUsage
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter -- http://twitter.com/OpenLink
Google+ -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers
On 9 May 2014, at 02:16, "Purohit, Sumit" <sumit.puro...@pnnl.gov> wrote:
> Thanks Hugh,
>
> Based on your suggestions i am able to upgrade virtuoso. Thanks
>
> Last question, although i installed v7.1.0 from
> http://sourceforge.net/projects/virtuoso/files/
> but installed conductor show "07.10.3207" . Does conductor uses a different
> internal version number ?
>
> thanks
> sumit
>
> From: Hugh Williams [hwilli...@openlinksw.com]
> Sent: Thursday, May 08, 2014 3:58 PM
> To: Purohit, Sumit
> Cc: virtuoso-users@lists.sourceforge.net
> Subject: Re: [Virtuoso-users] Instructions to upgrade to V 7.1.0
>
> Hi Sumit,
>
> You simply run the "checkpoint" command from "isql" to commit pending
> transactions into the database file before shutting the database running with
> the 7.0 binary and restarting with the 7.1 binary. As otherwise you will get
> an error indicating the trx file is not compatible with the binary, we shall
> create a tech note for this to make it clearer for users ...
>
> We would need to see more about your specific use case query , error ,
> dataset being used etc to know if it might be affected by the binary
> upgrade, there have been many query optimiser enhancements between 7.0 and
> 7.1 query plan may or may not have changed, but can't say for sure ...
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc. // http://www.openlinksw.com/
> Weblog -- http://www.openlinksw.com/blogs/LinkedIn --
> http://www.linkedin.com/company/openlink-software/Twitter --
> http://twitter.com/OpenLinkGoogle+ --
> http://plus.google.com/100570109519069333827/Facebook --
> http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
> On 8 May 2014, at 22:23, "Purohit, Sumit" <sumit.puro...@pnnl.gov> wrote:
>
>> and before using default 7.1 binaries i want to recompile it as in my
>> project i face issue mentioned here;
>> http://boards.openlinksw.com/phpBB3/viewtopic.php?f=12&t=801#p2310
>>
>> Do you think need to recompile changes anything mentioned above ?
>>
>> thanks
>> sumit
>>
>> From: Purohit, Sumit
>> Sent: Thursday, May 08, 2014 2:00 PM
>> To: Hugh Williams
>> Cc: virtuoso-users@lists.sourceforge.net
>> Subject: Re: [Virtuoso-users] Instructions to upgrade to V 7.1.0
>>
>> thanks for prompt response.
>> Can you explain what you mean by "nsuring a checkpoint has been performed
>> such that the trx file is 0 bytes" as this was my 2nd question.
>>
>> Thanks again.
>>
>> --sumit
>>
>> From: Hugh Williams [hwilli...@openlinksw.com]
>> Sent: Thursday, May 08, 2014 2:18 PM
>> To: Purohit, Sumit
>> Cc: virtuoso-users@lists.sourceforge.net
>> Subject: Re: [Virtuoso-users] Instructions to upgrade to V 7.1.0
>>
>> Hi Summit,
>>
>> There are no instructions necessary, as the databases between the two
>> versions are compatible. So you simply shutdown the 7.0 database instance
>> ensuring a checkpoint has been performed such that the trx file is 0 bytes
>> and then start the database with the new 7.1 binary.
>>
>> Best Regards
>> Hugh Williams
>> Professional Services
>> OpenLink Software, Inc. // http://www.openlinksw.com/
>> Weblog -- http://www.openlinksw.com/blogs/LinkedIn --
>> http://www.linkedin.com/company/openlink-software/Twitter --
>> http://twitter.com/OpenLinkGoogle+ --
>> http://plus.google.com/100570109519069333827/Facebook --
>> http://www.facebook.com/OpenLinkSoftware
>> Universal Data Access, Integration, and Management Technology Providers
>>
>> On 8 May 2014, at 21:51, "Purohit, Sumit" <sumit.puro...@pnnl.gov> wrote:
>>
>>> Hi,
>>> I want to update virtuoso (open source) from 7.00.3203 to latest version
>>> 7.1.0.
>>> I could not find any update instructions for this version. Included
>>> README.UPDATE talks about "Upgrading from VOS 6.1.X to VOS 6.1.4" as latest.
>>>
>>> Is there any documentation to upgrade to v7.1.0 ?
>>>
>>> 2nd question i have is that
>>> http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/UpgradingToVOS610
>>> page suggests to make sure "transaction log (virtuoso.trx) is empty ". Is
>>> shutting down of server is sufficient condition to achieve this ? or do we
>>> need to do something else ?
>>>
>>> Thanks
>>> Sumit Purohit
>>> ------------------------------------------------------------------------------
>>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
>>> • 3 signs your SCM is hindering your productivity
>>> • Requirements for releasing software faster
>>> • Expert tips and advice for migrating your SCM now
>>> http://p.sf.net/sfu/perforce_______________________________________________
>>> Virtuoso-users mailing list
>>> Virtuoso-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>
>> ------------------------------------------------------------------------------
>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
>> • 3 signs your SCM is hindering your productivity
>> • Requirements for releasing software faster
>> • Expert tips and advice for migrating your SCM now
>> http://p.sf.net/sfu/perforce_______________________________________________
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
