My Oracle Support Banner

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 15, 2023

Applies to:

Oracle Reports Developer - Version 12.2.1.0.0 and later
Linux x86-64

Symptoms

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:

<Nov 2, 2015 9:00:28 PM GMT> <INFO> <NodeManager ComponentManager> <Server failed so attempting to restart (restart count = 1)>
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:

<Warning> <oracle.dfw.framework> <DFW-40121> <failure creating incident from WLDF notification oracle.dfw.incident.IncidentCreationException: DFW-40116: failure creating incident
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 [79]"
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.093+01:00] [WLS_REPORTS] [NOTIFICATION] [DFW-40101] [oracle.dfw.incident] [tid: Thread-72] [userId: <anonymous>] [ecid: <ecid>] [APP: reports] [partition-name: DOMAIN] [tenant-name: GLOBAL] An incident has been signalled with the incident facts: [problemKey=DFW-99998 [java.lang.UnsatisfiedLinkError][oracle.reports.util.EnvironmentGlobal.<init>][reports] incidentSource=SYSTEM incidentTime=Tue Nov 03 13:50:03 CET 2015 errorMessage=DFW-99998 executionContextId=null]
[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:

####<Nov 3, 2015 10:35:12 AM CET> <Error> <WebLogicServer> <masked_server.and.domain> <WLS_REPORTS> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <00501a40-ff9a-4479-bc75-8edbab0ef8a1-00000060> <1446543312639> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000337> <[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "631" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@6c1149ac[GET /reports/rwservlet/showenv]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:

  

Changes

 New installation on Linux OEL7 or RedHat7.

Cause

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
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.