HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- HPUX Insight Mgr 4.0 to 4.2 upgrade
Server Management - Systems Insight Manager
1833344
Members
4494
Online
110051
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
Forums
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
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
01-11-2005 01:22 PM
01-11-2005 01:22 PM
HPUX Insight Mgr 4.0 to 4.2 upgrade
Here's the problem.
The orginal installation was Insight Mgr 4.0 with ProgreSQL version 7.3.1. It had over 200 devices installed, and was working.
I downloaded the new IM 4.2 upgrade pkg, and read the instructions. They stated that all I need to do was do an swinstall on the new IM software.
That I did, and swinstall also automatically marked the ProgreSQL 7.4.1 database package as a dependency. The packages installed, and then started the configuration section. The IM pkg appeared to progress without a problem until it tried to connect to the existing database. The SQL db would not come up. It was complaining about the data files being in 7.3.1 format which it said were incompatable. Also, the new sql pkg appeared to only partially installed, as an swlist listed both versions.
So, I uninstalled the new sql package, and reinstalled it. That cleared up the swlist, but not the db startup error.
So now, I appear to be close to having the upgrade completed, except that the new db binaries can't work with the existing 7.3.1 db.
So, I'm assuming that the new db package should be able to upgrade the older versiosn files. Otherwise, it sure shouldn't be called an upgrade!
My opther choice is to back everything out back to IM 4.0. But, eventually I'llhave to move forward.
The other choice is to do a fresh install, and then reenter all of the existing configurations. Not something that I really want to do either.
Any ideas or suggestions?
The orginal installation was Insight Mgr 4.0 with ProgreSQL version 7.3.1. It had over 200 devices installed, and was working.
I downloaded the new IM 4.2 upgrade pkg, and read the instructions. They stated that all I need to do was do an swinstall on the new IM software.
That I did, and swinstall also automatically marked the ProgreSQL 7.4.1 database package as a dependency. The packages installed, and then started the configuration section. The IM pkg appeared to progress without a problem until it tried to connect to the existing database. The SQL db would not come up. It was complaining about the data files being in 7.3.1 format which it said were incompatable. Also, the new sql pkg appeared to only partially installed, as an swlist listed both versions.
So, I uninstalled the new sql package, and reinstalled it. That cleared up the swlist, but not the db startup error.
So now, I appear to be close to having the upgrade completed, except that the new db binaries can't work with the existing 7.3.1 db.
So, I'm assuming that the new db package should be able to upgrade the older versiosn files. Otherwise, it sure shouldn't be called an upgrade!
My opther choice is to back everything out back to IM 4.0. But, eventually I'llhave to move forward.
The other choice is to do a fresh install, and then reenter all of the existing configurations. Not something that I really want to do either.
Any ideas or suggestions?
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP