LSF 9.0.1.6 Patch Install Fails

 22 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
I have a brand new install of LSF 9.0.1.6 on HP-UX 11.31 with WebSphere 7.0, Tivoli 6.2, and Oracle 11gR2. After the 9.0.1.6 base install I was able to complete all smoke tests successfully and everything appeared fine. When I try to install a LCT patch the install fails during the activation of LDAS. I have attached the portion of the install.log where the errors occur. Has anyone else had problems installing patches?
Attachments
Jimmy Chiu
Veteran Member
Posts: 641
Veteran Member
Set the lawson services to manualstart, do a clean reboot, apply the patch with lawson services off.
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
I am on Unix so there are no services that autostart. I rebooted but the install still failed.
Jimmy Chiu
Veteran Member
Posts: 641
Veteran Member
Which JT you are installing? Lawsec off.
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
I tried a batch install of all JT's and then I uninstalled the environment and started over trying just P6167 and P746. lawsec is off.
Bart Conger
Advanced Member
Posts: 18
Advanced Member
3 Helpful Replier
3 Engaged Reader
Sometimes the batch install skips the large base patches, in error. The batch update process can still be used with one patch, install one at a time as you are and continue validating manual stops and starts after each patch to ensure you did not get a bad one. It takes a little longer but hopefully will help you to find the error.
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
I have tried the P746 and P6167 one at a time and still get the error. The install is having trouble finding the lajavarts library even though it is in $GENDIR/lib/shared.
Jeff White
Veteran Member
Posts: 83
Veteran Member
Are your process definition settings for lawson filled out in WebSphere?
com.lawson.gen
com.lawson.lawdir
etc

Check:
LD_LIBRARY_PATH
/etc/lawson.env
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
Yes, I have everything entered in WebSphere. I double checked even though I was already able to logon to the Portal and ran LO920 before I tried the patch install. The WebSphere application server is stopped during the patch install anyway, so that should not be where these values come from.

$GENDIR/lib/shared is in the LD_LIBRARY_PATH of lawson.env.
EricS
Veteran Member
Posts: 80
Veteran Member
Kevin, in my /etc/lawson.env /lawson/law/gen/lib/shared is also in LIBPATH. We also went to a convention of using complete paths, no variables. I don't really remember why that was as it was years ago. Might either one or both of those. Not sure if that will help.
Jeff White
Veteran Member
Posts: 83
Veteran Member
Did you run the . cv as root before starting kicking off the patch?

We're the exact same setup as you are, except we're still on Oracle 10g. I didn't run into this issue after install.

Jeff
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
Eric,
The actual entry in lawson.env is the complete path and not $GENDIR. I believe LIBPATH is for AIX, but I can try putting it in my lawson.env.

Jeff,
Yes, I did the following before installing.
newgrp lawson
umask 0
. cv envname
Jeff White
Veteran Member
Posts: 83
Veteran Member
For HP-UX 11.31, in the lawson.env I have PATH and LD_LIBRARY_PATH. I don't think you want to put LIBPATH in there.
Jimmy Chiu
Veteran Member
Posts: 641
Veteran Member
any error in your ladb.log and lase.log?
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
No errors in ladb.log or lase.log.
Jeff White
Veteran Member
Posts: 83
Veteran Member
Can you post your /etc/lawson.env ? And the results of "env" as root?

If you'd rather email it, my email is jeffwhite@growmark.com
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
I have attached the information that you have requested.
Attachments
Jeff White
Veteran Member
Posts: 83
Veteran Member
I installed the exact same patches last week without error.

Can you run the stoplaw and startlaw manually from the command line without an error?

Jeff White
Veteran Member
Posts: 83
Veteran Member
Do you have a copy of /etc/lawson.env before you added all of the other settings? Try going back to the original /etc/lawson.env and try it again.
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
The original does not have ORACLE_HOME. I suppose I could try adding just that variable and updating PATH and LD_LIBRARY_PATH for oracle. What I don't understand is why the base LCT install did not get these errors. The install.log at this point in the base install shows "LDAS is ok"
Jeff White
Veteran Member
Posts: 83
Veteran Member
But the base install didn't have all of those extra values in lawson.env. I don't know if lawson is complaining about all of those extra values being in there or not, but it's worth a shot. This is what we have: (PATH and LD_LIBRARY_PATH not filled out):
Set LAWENVNAME prod901
Set GENDIR /law90/gen
Set LAWDIR /law90/lawson
Set LADBDIR /law90/DB
Set LAW_JAVA_HOME /opt/java6
Set LAW_JAVA_BIN /opt/java6/bin/IA64W
Set COBDIR /opt/cobolse51
Set ORACLE_HOME /law90/db10g
Set LAWIPC 0x9
Set TWO_TASK gmkprd2
Set DATASET TF60
Set TAXFACTORY /law90/taxfacUS
Set TAXFACTORYCA /law90/taxfacCA
Set PATH
Set LD_LIBRARY_PATH
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
Jeff,

I added the ORACLE_HOME to the original lawson.env and the install was successful. I'll see if I can figure out which variable was causing the problem.

Thanks for your help.

Kevin
Kevin Anderson
Advanced Member
Posts: 22
Advanced Member
Based on the documentation on page 43 of the Lawson Core Technology Installation Guide, I included $JAVA_HOME/bin in the PATH before $LAW_JAVA_BIN. Removing that solved the problem.

Thank you everyone for our help.