cancel
Showing results for 
Search instead for 
Did you mean: 

sapinst failed

Former Member
0 Kudos

Try to insatll solution manager 4.0 on HP-UX 11.11

when I did the sapinst, the gui can be started but it shows me an error. When I puch the ok button, the gui colsed. I don't know what wrong.

>>>>>>>>>>>

  1. ./sapinst

Starting GuiServer using:

/opt/java1.4/bin/java -cp /oracle/tmp/sapinst_exe.24603.1190887332/JAR/instgui.jar:/oracle/tmp/sapinst_exe.24603.1190887332/JAR/inqmyxml.jar -Djava.security.egd=file:/dev/urandom SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true

>>>>>>>>>> the gui started, and shows

You start the installation without specifying a startup file via SAPINST_CONTROL_URL in the directory /oracle/tmp/sapinst_exe.24603.1190887332. The framework asumes that control.xml or product.catalog has to be used but there exist now such files.If there exist a installation with a different startup filename please specify that filename via SAPINST_CONTROL_URL.

>>>>>>>>>> after I click ok. the gui closed

here is what's the env

SAPINST_JRE_HOME=/opt/java1.4

PATH=$PATH:/opt/java1

DISPLAY=168.168.106.102:0.0

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Iwang,

This env. variable should be like JAVA_HOME=<dest.>, did U check with javac? did you added the IP Host name in the /etc/host file?

Regards,

Hari.

Former Member
0 Kudos

I don't think it it the JAVA_HOME's fault. The host name is ok. Because I have setup it. Is the Java version's problem. Can anyone help me check it?

The problem is the gui can be start, but give me a message box (show as above). After I click ok, the gui stoped and the sapinst exit.

  1. java -version

java version "1.4.2.07"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.07-050121-15:53)

Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.07-050121-17:30-PA_RISC2.0 PA2.0 (aCC_AP), mixed mode)

#[/]uname -a

HP-UX k5701 B.11.11 U 9000/899 664451351 unlimited-user license

Former Member
0 Kudos

The reason is the wrongly mount file system of CDROM. According to pdf, it should be:

  1. mount -r -F cdfs -o rr /dev/dsk/c4t2d0 /cdrom

I didn't notice this. So the sapinst must follow every step in the manual.

Cloesed this isuse.