Error when trying to lainch the visual administrator

[Former Member]

Hello,

I have installed the Solution manager 7.1 on Linux 5.4 / Oracle 11.2.0.2 while i am trying to open the visual administrator to configure the SLD (Creation of the onnection LCRSAPRFC_<SID>), i am getting the following error:

+SD1ODYLSV1:sd1adm 17> pwd

/usr/sap/SD1/DVEBMGS00/j2ee/admin

SD1ODYLSV1:sd1adm 18> ./go

java version "1.4.2"

Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)

IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142ifx-20110628 (JIT enabled)

J9VM - 20110627_85693_LHdSMr

JIT - 20090210_1447ifx5_r8

GC - 200902_24)

Exception in thread "main" java.lang.UnsatisfiedLinkError: awt (libXp.so.6: cannot open shared object file: No such file or directory)

at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:990)

at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:954)

at java.lang.System.loadLibrary(System.java:409)

at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:76)

at java.security.AccessController.doPrivileged(AccessController.java:197)

at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:81)

at sun.awt.DebugHelper.<clinit>(DebugHelper.java:56)

at java.lang.J9VMInternals.initializeImpl(Native Method)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)

at java.awt.Component.<clinit>(Component.java:571)

at java.lang.J9VMInternals.initializeImpl(Native Method)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:161)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:161)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:161)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:161)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:161)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.tools.launcher.Launcher.launch(Launcher.java:336)

at com.sap.engine.tools.launcher.Launcher.main(Launcher.java:114)

+

The package libXp.so.6 is already installed and the x server used (Exceed )in my case works fine.

I used the IBM SDK 1.4.2 for the installtion but during the installtion the GUI asked to use the SAP JVM and i accepted it.

Do we have to make changes to the Varaibales environment after the SAP JVM installtion? is the error related to the JAVA JDK?

Regards,

Hassan

[markus_doehr2 · Accepted solution]

> The package libXp.so.6 is already installed and the x server used (Exceed )in my case works fine.

Is that package installed in both 32bit and 64bit?

Since the JDK is 64bit you need a 64bit libXp.so.6.

Markus

[blanca_serrano]

Hello,

You can find the answer in Oracle Metalink Note:443617.1, which states:

Cause

=========

The i386 version of the libXp package is missing.

The Oracle Universal Installer (OUI) requires the file

libXp.so.6 and this file is installed with the package

libXp in RHEL 5 and OEL 5.

Issue the following to confirm the missing rpm:

% rpm -qa queryformat "%-%-%

(%)\n" grep libXp

Solution

=========

The package libXp was not installed in RHEL 5/OEL 5 with default

RPM packages, so it will need to be installed manually.

In RHEL 4 this file was provided by the package

xorg-x11-deprecated-libs which is installed with default package

installation but this is not the case for RHEL5/OEL5 and is

now provided with a different rpm, the libXp rpm.

Install the package libXp by the command:

1. rpm -ivh </path/to/>libXp.<version>.i386.rpm

To find out more details, you may access to Oracle Metalink

with SAP account

#758563 - Oracle Metalink access for SAP customers

I hope this helps you.

Regards,

Blanca

[Former Member]

Hello,

actually after adding /usr/X11R6/lib64 to LD_LIBRARY_PATH the problem was solved.

regards,

Hassan