Help needed with DB2 UDB 8.1 ESE on HP-UX 11i
Tom Williams
I learned that DB2 UDB 8.1 requires HP-UX 11i and I've since upgraded
from 11.00B to 11i. Cool. I'm installing UDB 8.1 now and I'm able
to run the Java-based GUI installer over the network via X. I answer
the questions and start the installation process and it gets most of
the way through the installation and then something just "hangs". The
Java installation status window stops updating and a process called
"PA_" is taking 99% of the CPU and I have NO idea what it's doing.
It's been running like this for well over an hour now.
the 1.4.1_02 JRE is installed on the system.
Any idea on how I can find out what's going on and if there's a
problem?
Thanks in advance...
Peace...
Tom
Darin McBride
> Hi! Ok, in this thread:
>
>
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=2438ae9c.0302101154.767e29e6%40posting.google.com&rnum=1&prev=/groups%3Fq%3DUDB%2B8.1%2Binstall%2BHP-UX%2Bgroup:comp.databases.ibm-db2%26hl%3Den%26lr%3D%26ie%3DUTF-8%26group%3Dcomp.databases.ibm-db2%26selm%3D2438ae9c.0302101154.767e29e6%2540posting.google.com%26rnum%3D1
>
> I learned that DB2 UDB 8.1 requires HP-UX 11i and I've since upgraded
> from 11.00B to 11i. Cool. I'm installing UDB 8.1 now and I'm able
Now there's a treat - someone looking for their information (and
finding it!) before asking a question in usenet. Almost unheard of!
:-)
> to run the Java-based GUI installer over the network via X. I answer
> the questions and start the installation process and it gets most of
> the way through the installation and then something just "hangs". The
> Java installation status window stops updating and a process called
> "PA_" is taking 99% of the CPU and I have NO idea what it's doing.
> It's been running like this for well over an hour now.
>
> the 1.4.1_02 JRE is installed on the system.
>
> Any idea on how I can find out what's going on and if there's a
> problem?
Well, that there's a problem, I have a hard time imagining anyone
doubting. WHAT the problem is, however, is definitely yet to be
discovered.
As I had posted earlier in the above quoted thread, the debug info that
would be needed is to run db2setup with the '-d' flag. There will be
output in /tmp/db2setup.* which can be compressed and sent to me. (Be
sure to remove the antispam parts of my email address first ;-)
Note that if it is reasonably significant to work through, I may ask
you to contact IBM and open a PMR over this. In that case, save the
db2setup.* files for that time - they'll definitely be needed.
Tom Williams
> Now there's a treat - someone looking for their information (and
> finding it!) before asking a question in usenet. Almost unheard of!
> :-)
:)
> As I had posted earlier in the above quoted thread, the debug info that
> would be needed is to run db2setup with the '-d' flag. There will be
> output in /tmp/db2setup.* which can be compressed and sent to me. (Be
> sure to remove the antispam parts of my email address first ;-)
Ok, since the app seems to be "hung" vs "crashing" I wasn't sure if
the "-d" would be helpful. I'll re=run it with this option and will
gather the output.
> Note that if it is reasonably significant to work through, I may ask
> you to contact IBM and open a PMR over this. In that case, save the
> db2setup.* files for that time - they'll definitely be needed.
I'll also talk to our main IBM POC about opening a PMR about this
issue, if necessary. Thanks!
Peace...
Tom
Darin McBride
> Darin McBride <dmcb...@naboo.to.org.no.spam.for.me> wrote in message
> news:<%yZpb.298158$9l5.173649@pd7tw2no>...
>
>> Now there's a treat - someone looking for their information (and
>> finding it!) before asking a question in usenet. Almost unheard of!
>> :-)
>
> :)
>
>> As I had posted earlier in the above quoted thread, the debug info that
>> would be needed is to run db2setup with the '-d' flag. There will be
>> output in /tmp/db2setup.* which can be compressed and sent to me. (Be
>> sure to remove the antispam parts of my email address first ;-)
>
> Ok, since the app seems to be "hung" vs "crashing" I wasn't sure if
> the "-d" would be helpful. I'll re=run it with this option and will
> gather the output.
Fair enough question. Once you're sure it is hung, then you can kill
it, and now it's crashed. :-)