Reports Builder / Server Fails to Start in 12c With " libXm.so.3: cannot open shared object file: No such file or directory" Only on Linux 7
(Doc ID 2073755.1)
Last updated on FEBRUARY 23, 2019
Applies to:Oracle Reports Developer - Version 220.127.116.11.0 and later
This is a new installation of Oracle Forms/Reports 12c on Linux OEL7 or RedHat7.
When trying to start the Reports Builder (DOMAIN_HOME/reports/bin/rwbuilder.sh), it fails to start with the following message:
ORACLE_HOME/bin/rwbuilder: error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory
Similar behavior happens for other reports components like rwconverter.sh.
For the standalone Reports server the behavior when trying to start it via startComponent.sh is an error that says please check nodemanager log files.
Checking DOMAIN_HOME/servers/repserv1/logs/repserv1.out file (For this example the standalone reports server is called repserv1) the following is being recorded:
ORACLE_HOME/bin/rwserver: error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory
<Nov 2, 2015 9:00:28 PM GMT> <INFO> <NodeManager ComponentManager> <The server 'repserv1' with process id 19097 is no longer alive; waiting for the process to die.>
<Nov 2, 2015 9:00:28 PM GMT> <FINEST> <NodeManager ComponentManager> <Process died.>
You may also see:
Cause: DFW-40112: There was an error executing adrci commands; the following errors have been found "DIA-48415: Syntax error found in string [create incident problem_key="BEA-000337 [/reports/rwservlet]",]" error_facility] at column "
Action: Ensure that command line tool "adrci" can be executed from the command line.
The behavior seen for the in-process reports server is a bit different. Here you will see that any webcommand (showjobs/getserverinfo/showenv/etc) will hang but no errors.
Checking WLS_REPORTS-diagnostic.log file the following will be recorded:
[2015-11-03T13:50:03.653+01:00] [WLS_REPORTS] [INCIDENT_ERROR] [DFW-40104] [oracle.dfw.incident] [tid: Thread-72] [userId: <anonymous>] [ecid: <ecid>] [errid: 8] [detailLoc: <DOMAIN_HOME>/servers/WLS_REPORTS/adr/diag/ofm/fmwdom/WLS_REPORTS/incident/incdir_8] [probKey: DFW-99998 [java.lang.UnsatisfiedLinkError][oracle.reports.util.EnvironmentGlobal.<init>][reports]] [APP: reports] [partition-name: DOMAIN] [tenant-name: GLOBAL] incident 8 created with problem key "DFW-99998 [java.lang.UnsatisfiedLinkError][oracle.reports.util.EnvironmentGlobal.<init>][reports]"
In addition WLS_REPORTS.log will show a struck thread as the following one:
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
New installation on Linux OEL7 or RedHat7.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document