| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to apply 6.0.0.7 fix using setupaix |
« View previous topic :: View next topic » |
| Author |
Message
|
| jcarr |
 Posted: Thu Jul 31, 2008 12:34 pm Post subject: Unable to apply 6.0.0.7 fix using setupaix |
 |
|
Novice
Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN
|
I'm trying to apply an update from WMB 6.0.0.3 to 6.0.0.7.
This is on AIX 5.2 - 10 (5200-10)
The first problem received was, during install, I received an error at about 53% of the way through using the setupaix program. I don't recall the error, but I do know it said something about a heap dump generated.
The disk where WMB is installed is at 74% capacity, with 2.6 GB free. Don't see that as an issue.
Not understanding the problem, I tried to execute setupaix again and write to a log. This time, when running, I get a message returning saying (more text to follow, so please keep reading):
Errors occurred during installation.
- null
Here's the error log:
file type: 0
file id: 0
length: 273
offset: 359886
file name: instructions.txt
file type: 5
file id: 1
length: 832
offset: 360159
file name: Verify.jar
file type: 2
file id: 2
length: 711
offset: 360991
file name: launch.txt
file type: 1
file id: 3
length: 610
offset: 361702
file name: any_aix.jvm
file type: 4
file id: 4
length: 36448447
offset: 362312
file name: aix_jre142-20040626.bin
Finding a JVM
Initiating JVM search based on hints...
WARNING: Unable to verify any_aix.jvm because the JVM_PROPERTIES tag was not specified.
WARNING: Unable to verify any_aix.jvm because the JVM_PROPERTIES tag was not specified.
WARNING: Unable to verify any_aix.jvm because the JVM_PROPERTIES tag was not specified.
A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>
Executing launch script command: "/tmp/isjzA0mib/jre/bin/java" -cp "":"setup.jar":"" -Dtemp.dir="/tmp/" -Dis.jvm.home="/tmp/isjzA0mib" -Dis.jvm.temp="1" -Dis.media.home="" -Dis.launcher.file="/home/jcarr/disk1/./setupaix" -Dis.jvm.file="/tmp/isjzA0mib/jvm" -Dis.external.home="/home/jcarr/disk1/." -Xms20m -Xmx60m run "-console" in working directory /home/jcarr/disk1/.
___________________________________________
Tried running using the GUI and console with the same results.
Also, I tried running as:
./setupaix -console -is:log log.txt -is:javahome /usr/java131
./setupaix -console -is:log log.txt -is:javahome /usr/java14
java14 re-produced the same error. java131 didn't even let us get to an options panel.
Any ideas on how to resolve?
_________________
If you can read this, you're too close. |
|
| Back to top |
|
 |
| paranoid221 |
| Posted: Thu Jul 31, 2008 1:34 pm Post subject: Re: Unable to apply 6.0.0.7 fix using setupaix |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 101
Location: USA
|
May be your java version needs to be above 1.4, like 1.4.2 and above.
Just a thought...  |
|
| Back to top |
|
|
| jcarr |
| Posted: Thu Jul 31, 2008 1:48 pm Post subject: |
|
|
Novice
Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN
|
Thanks for the reply.
Good suggestion. I checked the JVM and I was using an up to date version of Java 1.4.2.
Here's some more details:
I decided to uninstall WMB 6.0, and that was successful.
Then, I re-installed WMB 6.0.0.0 and that worked.
I decided to try to install 6.0.0.3 since that was already on there and, at 3%, I get that "null" error.
This is going to be a good story on why it's happening.
_________________
If you can read this, you're too close. |
|
| Back to top |
|
|
| jcarr |
| Posted: Wed Aug 06, 2008 2:04 pm Post subject: Problem resolved |
|
|
Novice
Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN
|
I had to open a PMR and IBM had to send a script (mqsi6_odmcleanup.sh ) to clean out Object Data Manager containing any references to mqsi60.
Here's some info about it in the event anyone hits this problem:
The ISMP uninstaller, that is installed with the Broker product, should:
1. Uninstall all the product binaries from the install directory.
2. Remove the product entries from the Software Vital Product Data (SWVPD) database. The SWVPD consists of a set of commands and the Object Data Manager (ODM) object classes for the maintenance of software product information. The ODM commands are used to remove the product entries.
3. Remove the product entries from /usr/lib/objrepos/vpd.properties file.
The information in the lpp, inventory, history, and product ODM object classes comprises the SWVPD for an installed software product. These object classes are stored in the following directories:
- /etc/objrepos / (root) part of the installable software product
- /usr/lib/objrepos /usr part of the installable software product
- /usr/share/lib/objrepos /usr/share part of the installable software product
The Broker installation will normally just update the /usr/lib/objrepos directory, but sometimes ISMP can cause fixpack ODM update failures such that the installation is left with mixed updates in both /etc/objrepos and /usr/lib/objrepos.
If you try to uninstall WMBv6 installation, although the product binaries are uninstalled and the vpd.properties file is updated correctly, most of the ODM entries (all apart from the inventory) are left, and therefore lslpp will still list the product as installed.
Cleanup the SWVPD
-----------------
To cleanup up the SWVPD, the ODM entries must be deleted from both /etc/objrepos and /usr/lib/objrepos. This can be done manually as follows:
1. export ODMDIR=/usr/lib/objrepos
2. Get a list of lpp identifiers for "mqsi6*":
odmget -q "name like mqsi6*" lpp | grep lpp_id
3. For each lpp_id, remove the matching entries, if any, from the inventory object class:
odmdelete -o inventory -q "lpp_id = [odmID1]"
4. For each lpp_id, remove the matching entries, if any, from the history object class:
odmdelete -o history -q "lpp_id = [odmID1]"
5. Remove the matching entries for "mqsi6*", if any, from the product object class:
odmdelete -o product -q "name like mqsi6*"
6. Remove the matching entries for "mqsi6*", if any, from the lpp object class:
odmdelete -o lpp -q "name like mqsi6*"
7. Now "export ODMDIR=/etc/objrepos" and repeat steps 2-6.
_________________
If you can read this, you're too close. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
