- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Migration: ingres 1.2a --> ingres 2006
Operating System - HP-UX
1753962
Members
7621
Online
108811
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2006 03:15 AM
08-01-2006 03:15 AM
Migration: ingres 1.2a --> ingres 2006
We are considering migrating our hpux 10.2 (ingres 1.2a) production system onto an rx2620 integrity server running hpux 11iv2 and ingres 2006.
Does anyone have any experience of such a migration and know any potential pitfalls?
I am aware of the 32bit-->64bit transition.
Does hpux provide patches speficic to individual databases and if so is ingres covered?
Does anyone have any experience of such a migration and know any potential pitfalls?
I am aware of the 32bit-->64bit transition.
Does hpux provide patches speficic to individual databases and if so is ingres covered?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2006 04:50 AM
08-01-2006 04:50 AM
Re: Migration: ingres 1.2a --> ingres 2006
Paul,
AFAIK, there are no HP-UX "Ingres specific" patches. Ingres Corp may have some requirements listed in the release notes however.
Also, if the application is developed in 4GL (ABF), there were some additional keywords introduced in the move up to Ingres II 2.0 (I believe) that may need to be addressed. Refer to the migration guides below for additional info on this.
One last item. I seem to recall that their was an issue with one of the ingres files used by the report writer parser. it was fixed by editting a config file and (*I think*) changing a single-quote to a double-quote, or perhaps the other way around. You may have already had to do this as it may have been introduced w/ the 6.4 to 1.2 migration, as well. Again, the news group can probably be of more assistance with this.
Some additional resources:
Ingres Corp:
http://www.ingres.com
news group, very active, some ingres corp and developer participation:
http://groups.google.com/group/comp.databases.ingres
William's Ingres Database Reference
http://ariel.its.unimelb.edu.au/~yuan/Ingres/ingres.html
Various migration guides on William's site:
http://ariel.its.unimelb.edu.au/~yuan/Ingres/ingres.html#migration
hope this is of some help.
AFAIK, there are no HP-UX "Ingres specific" patches. Ingres Corp may have some requirements listed in the release notes however.
Also, if the application is developed in 4GL (ABF), there were some additional keywords introduced in the move up to Ingres II 2.0 (I believe) that may need to be addressed. Refer to the migration guides below for additional info on this.
One last item. I seem to recall that their was an issue with one of the ingres files used by the report writer parser. it was fixed by editting a config file and (*I think*) changing a single-quote to a double-quote, or perhaps the other way around. You may have already had to do this as it may have been introduced w/ the 6.4 to 1.2 migration, as well. Again, the news group can probably be of more assistance with this.
Some additional resources:
Ingres Corp:
http://www.ingres.com
news group, very active, some ingres corp and developer participation:
http://groups.google.com/group/comp.databases.ingres
William's Ingres Database Reference
http://ariel.its.unimelb.edu.au/~yuan/Ingres/ingres.html
Various migration guides on William's site:
http://ariel.its.unimelb.edu.au/~yuan/Ingres/ingres.html#migration
hope this is of some help.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP