Systems Support Perspectives (Second in an occasional series)
Richard Lesses 2700011KU1 Visits (8118)
So, end of March, and time to blog again. I was going to do an entry on upgrading from Maximo 126.96.36.199 to Maximo 188.8.131.52. Things didn't work out as I planned. I have 26 screen shots ready for that post (or posts), but at about screen shot 24, I realized that I had goofed. Instead of upgrading from Maximo 184.108.40.206, my upgrade database was at Maximo 220.127.116.11. That is not supposed to be upgradeable to 18.104.22.168. Rules are, follow the instructions step-by-step, and don't magically hope that the 22.214.171.124 upgrade will update my database without a problem, just because it contains the scripts for Fix Pack 126.96.36.199. (This is a database I upgraded from 6.2.8 a few years ago, just before I started blogging. Now that was an epic venture, as far as Maximo installation and upgrade goes. It would have made a great set of blog entries.)
Anyway, this meant that I had first to apply a single dot Fix Pack to my upgrade database. An easy thing, no? I've done it many times. Just make a backup of my database and my SMP directory and I would have it done in a few hours at best.
Over a week later, I have finally wrestled my upgrade database to Maximo 188.8.131.52. What was wrong with it? It was pretty simple. Two things, actually. First, since I had migrated this SMP directory from another machine (virtual, now vanished) my Deployment Engine had the wrong host name. This problem was easy enough to fix: see http
Mar 31, 2015 12:23:55 PM com.