[Info-Ingres] OpenRoad 3.5 and ingres 2006

This is a discussion on [Info-Ingres] OpenRoad 3.5 and ingres 2006 within the Ingres Database forums in Other Databases category; We're using an old OpenRoad3.5 application with an Ingres 2.6 database hosted on a solaris 2.6 server. This is a legacy system that they just don't want to get rid of. The Sun server is now coming to the end of it's useful life and support, so I though I'll simply do a unloaddb of the database on to our existing solaris 10 server with Ingres 2006 64bit and then repoint the vnode on each openroad client. Before I invest time testing... Has anyone had experience doing this? If so what gotchas are ...

Go Back   Database Forum > Other Databases > Ingres Database

Database Forums

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 08-27-2008, 05:48 AM
Default [Info-Ingres] OpenRoad 3.5 and ingres 2006

We're using an old OpenRoad3.5 application with an Ingres 2.6 database
hosted on a solaris 2.6 server. This is a "legacy" system that "they"
just don't want to get rid of.

The Sun server is now coming to the end of it's useful life and support,
so I though I'll simply do a unloaddb of the database on to our existing
solaris 10 server with Ingres 2006 64bit and then repoint the vnode on
each openroad client.

Before I invest time testing...

Has anyone had experience doing this? If so what gotchas are there?

Will OpenRoad3.5 work ok with Ingres 2006 (I suspect it does)?

Is there license information on using OpenRoad3.5 with Ingres 2006? I
seem to recall there may be some issues with components of OpenRoad that
are not covered....?

Thanks

Gareth

Cymraeg:-
Mae'r neges hon yn gyfrinachol nad chi yw'r derbynnydd y bwriedid y neges ar ei gyfer, byddwch mor garedig â rhoi gwybod
i'r anfonydd yn ddi-oed. Dylid ystyried un rhywd datganiadau neu sylwadau a wneir uchod yn rhai personol,ac nid o angen rhaid yn rhai o
eiddo Ymddiriedolaeth Prifysgol GIG Abertawe Bro Morgannwg, nac unrhyw ran gyfansoddol ohoni na chorff cysylltiedig.

Cofiwch fod yn ymwybodol ei bod yn bosibl y bydd disgwyl i Ymddiriedolaeth Prifysgol GIG Abertawe Bro Morgannwg roi cyhoeddusrwydd i gynnwys unrhyw ebost neu
ohebiaeth a dderbynnir, yn unol ag amodau'r Ddeddf Rhyddid Gwybodaeth 2000. I gael mwy o wybodaeth am Ryddid Gwybodaeth, cofiwch gyfeirio
at wefan Ymddiriedolaeth Prifysgol GIG Abertawe Bro Morgannwg ar www.abm.university-trust.wales.nhs.uk

English:-
This message is confidential. If you are not the intended recipient of the message then please notify the sender immediately.
Any of the statements or comments made above should be regarded as personal and not necessarily those of Abertawe Bro Morgannwg University NHS Trust, any
constituent part or connected body.

Please be aware that, under the terms of the Freedom of Information Act 2000, Abertawe Bro Morgannwg University NHS Trust may be required to make public the
content of any emails or correspondence received. For further information on Freedom of Information, please refer to the Abertawe Bro Morgannwg University NHS
Trust website at www.abm.university-trust.wales.nhs.uk.

Reply With Quote
  #2  
Old 08-27-2008, 06:52 AM
Default Re: [Info-Ingres] OpenRoad 3.5 and ingres 2006

Gareth Williams wrote:

> We're using an old OpenRoad3.5 application with an Ingres 2.6 database
> hosted on a solaris 2.6 server. This is a "legacy" system that "they"
> just don't want to get rid of.
>
> The Sun server is now coming to the end of it's useful life and support,
> so I though I'll simply do a unloaddb of the database on to our existing
> solaris 10 server with Ingres 2006 64bit and then repoint the vnode on
> each openroad client.
>
> Before I invest time testing...
>
> Has anyone had experience doing this? If so what gotchas are there?
>
> Will OpenRoad3.5 work ok with Ingres 2006 (I suspect it does)?


As a client it should work fine if you do what you describe above.

I am not an OpenROAD expert but I believe there are problems with using
Ingres 2006 to develop/build applications using OR 3.5. You will need
to make sure you have a system you can use to build the app. It should
be easy enough to create a peer 2.6 installation for that purpose.
Or you could migrate the dev Database to a wintel host if you want to be
cheap about it.

OR 3.5 enterprise support ends in December. Ingres 2.6 will end in
December 2009. Extended support will be available for both for some
time after that.

> Is there license information on using OpenRoad3.5 with Ingres 2006? I
> seem to recall there may be some issues with components of OpenRoad that
> are not covered....?


There are no license implications as a result of changing the version of
Ingres you are connecting to. The two products are licensed separately,
and the proprietary elements of OpenROAD are covered by the OpenROAD
license. (Heck, you can connect OpenROAD to Oracle if you want.)

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.


Reply With Quote
  #3  
Old 08-29-2008, 05:31 AM
Default Re: OpenRoad 3.5 and ingres 2006

On Aug 27, 6:48*pm, "Gareth Williams" tr.wales.nhs.uk> wrote:
> We're using an old OpenRoad3.5 application with an Ingres 2.6 database
> hosted on a solaris 2.6 server. This is a "legacy" system that "they"
> just don't want to get rid of.
>
> The Sun server is now coming to the end of it's useful life and support,
> so I though I'll simply do a unloaddb of the database on to our existing
> solaris 10 server with Ingres 2006 64bit and then repoint the vnode on
> each openroad client.
>
> Before I invest time testing...
>
> Has anyone had experience doing this? If so what gotchas are there?
>
> Will OpenRoad3.5 work ok with Ingres 2006 (I suspect it does)?
>
> Is there license information on using OpenRoad3.5 with Ingres 2006? I
> seem to recall there may be some issues with components of OpenRoad that
> are not covered....?
>
> Thanks
>
> Gareth
>
> Cymraeg:-
> Mae'r neges hon yn gyfrinachol nad chi yw'r derbynnydd y bwriedid y negesar ei gyfer, byddwch mor garedig â rhoi gwybod
> i'r anfonydd yn ddi-oed. Dylid ystyried un rhywd datganiadau neu sylwadaua wneir uchod yn rhai personol,ac nid o angen rhaid yn rhai o
> eiddo Ymddiriedolaeth Prifysgol GIG Abertawe Bro Morgannwg, nac unrhyw ran gyfansoddol ohoni na chorff cysylltiedig.
>
> Cofiwch fod yn ymwybodol ei bod yn bosibl y bydd disgwyl i Ymddiriedolaeth Prifysgol GIG Abertawe Bro Morgannwg roi cyhoeddusrwydd i gynnwys unrhyw ebost neu
> ohebiaeth a dderbynnir, yn unol ag amodau'r Ddeddf Rhyddid Gwybodaeth 2000. I gael mwy o wybodaeth am Ryddid Gwybodaeth, cofiwch gyfeirio
> at wefan Ymddiriedolaeth Prifysgol GIG Abertawe Bro Morgannwg arwww.abm.university-trust.wales.nhs.uk
>
> English:-
> This message is confidential. If you are not the intended recipient of the message then please notify the sender immediately.
> Any of the statements or comments made above should be regarded as personal and not necessarily those of Abertawe Bro Morgannwg University NHS Trust, any
> constituent part or connected body.
>
> Please be aware that, under the terms of the Freedom of Information Act 2000, Abertawe Bro Morgannwg University NHS Trust may be required to make public the
> content of any emails or correspondence received. For further informationon Freedom of Information, please refer to the Abertawe Bro Morgannwg University NHS
> Trust website atwww.abm.university-trust.wales.nhs.uk.


I am currently doing some DBA work at a site that runs OR 3.5 and
Ingres 2006. I upgraded them in November 2007 from Ingres 2.0 to
Ingres 2006 at the server end. They have no problems with their OR App
provided you keep the client running on the original Ingres 2.0
NET.

Sidney
Reply With Quote
Reply


Thread Tools
Display Modes



All times are GMT -4. The time now is 11:22 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Integrated by bbpixel2009 :: jvbPlugin R1013.368.1

Search Engine Friendly URLs by vBSEO 3.1.0
vB Ad Management by =RedTyger=
In an effort to better serve ads to our visitors, cookies are used on Mydatabasesupport.com. For more information, check out our Privacy Policy.