今天装IAS Report时又遇到了一个REP-3000的错误，调试了三个小时，才发现是一个环境变量配置的问题。
DISPLAY=:0.0;export DISPLAY
这个hostname可以由机器的IP代替，这个机器的IP不是服务器的IP，而是安装或者启动XWindow的客户端的机器的IP。
如果你安装的时候用的是远程的xwindows的客户端的话，这个IP会自动配置为你当时登录客户端机器的IP，如果你后来配置report时
更换了机器，也需要注意更改这个IP.
Metalink里面的一篇文章，给转帖过来了
PURPOSE
========
The purpose of this document is to:
- provide information on how to resolve the REP-3000 error.
- explain why the DISPLAY environment variable is required when
running Reports on UNIX machines.
- describe the history behind this problem.
- give hints on how to troubleshoot problem.
- include a comprehensive summary of various scenarios which may
result in a REP-3000 error.
SCOPE & APPLICATION
====================
Intended Audience: Developers, System Administrators, Consultants
Most of the information in this note is based on Oracle Reports 6i, but
there will be some version-specific items included, i.e. Reports 9i,
Reports 2.5.x, even though some of the versions are no longer supported.
Bear in mind that support for Reports versions prior to Reports 6i (6.0.8.x)
is limited to known issues and migration.
This note is broken up in the following sections:
I. PROBLEM DESCRIPTION
II. SOLUTION
III. EXPLANATION
IV. HISTORY
V. TROUBLESHOOTING:
VI. SCENARIOS WHERE YOU MAY ENCOUNTER REP-3000
1. Reports Version-Specific Issues
2. Oracle Forms Related Issues
3. Oracle Applications Related Issues
4. NLS_LANG Related Issues
5. OC4J Issues
6. General Issues
I. PROBLEM DESCRIPTION
=======================
Running a report using Reports Runtime (rwrun60), using Reports Builder
(rwbld60), using Reports Server Client (rwcli60), accessed over the Web
(rwcgi or rwservlet), or called from Oracle Forms results in the following error:
REP-3000: INTERNAL ERROR STARTING ORACLE TOOLKIT
II. SOLUTION
============
You must set the DISPLAY environment variable to a valid X Windows session.
If you are running report using rwrun60, you need to set DISPLAY in the same
session that you invoke rwrun60. If you are running report through the
Reports Server (Services) using rwcli60 or on the web, then you need to
ensure that the Reports Server (Services) is started from the session that
has a valid DISPLAY environment variable.
Syntax to set the DISPLAY environment variable:
C Shell
---------
% setenv DISPLAY :0.0
Bourne or Korn Shell
--------------------------
$ DISPLAY=:0.0;export DISPLAY
NOTE: you may use :0.0 instead of :0.0.
You have 2 options to enable your Reports Server (Services).
Option 1
---------
You will need to setup the DISPLAY environment variable to point to an active
X Windows. This means:
1. reconfiguring your Unix server to have an active xterm session.
2. using the IP Address of your PC with X-emulation, e.g. Exceed or X-Reflection.
Please note that the use of PC based X-emulation is not supported. See Note 2056834.6.
3. finding a Windows printer server that is always up and use its IP Address.
In cases 2 & 3, you do not have to be connected to the server, just have the
PC running and available on the network.
Option 2
---------
If you do not want to run a full-blown X-Windows, then you may use the
freeware X server VNC.
Information on how to use VNC is included in:
section 1.5.7.1.6 in the iAS 1.0.2.2 release notes (Note 146652.1)
or section 12.22 in the iAS 1.0.2.1 release notes (Note 139837.1)
III. EXPLANATION
===============
In order to run bitmapped reports, the engines spawned by the Oracle
Reports Server (Services) need to have access to an appropriate
windowing system. On Windows platforms this is a non-issue, but on
non-Windows platforms this means that a valid X Windows session must
be available.
If the DISPLAY environment is not set correctly for the Reports Server
on UNIX platforms, issuing any command to run a report results in the
REP-3000 error.
IV. HISTORY
===========
Setting the DISPLAY to a valid X Windows session is a REQUIREMENT
and has always been a requirement. It is NOT a bug. It provides a
fundamental capability that Reports requires for font metrics and
rasterization, image manipulation and conversion, etc. This is not
just specific to Oracle Reports. All UNIX-based machines require an
X-Windows and Motif environment to run any GUI-based product. A
long time ago, there was a special character mode executable that
did not require X Windows when doing only character mode reports.
However, this is no longer the case.
V. TROUBLESHOOTING
===================
Take the following steps to help you troubleshoot REP-3000 errors:
1. First, test the integrity of DISPLAY by issuing "xclock" command.
- Login to the machine where Reports Server is installed.
- From the UNIX command prompt, set the DISPLAY to a valid
X Windows session:
setenv DISPLAY :0.0
- Ensure that DISPLAY was set correctly:
echo $DISPLAY
- Type command "xclock"
If you see a clock come up, then the DISPLAY is set correctly.
If you do not see the clock, then DISPLAY is not set to an active Xterm.
You must have xclock working before running any reports.
Another way to test whether an X server is running on given machine
and you have permissions to connect to it, you can use the following command:
xterm -display :0.0
If you do not have permissions to access the display or if there is no
such display running on the given machine, an error similar to the
following is displayed:
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
xterm Xt error: Can't open display: :0.0
2. If the error occurs when running report on the Web, then you need
to first test it using Reports Runtime on the machine where your Reports
Server is running. Steps:
- Set DISPLAY to a valid X Windows session
- Run report using sample syntax:
rwrun60 report=test.rdf userid=username/password@db destype=file desname=test.html desformat=html batch=yes
If rwrun60 works, go to step 3.
If rwrun60 does not work, then:
- Re-check your DISPLAY environment variable
- Go back to step 1 and test the integrity of DISPLAY
- Review Section VI (below) to see if any of the scenarios
match your situation.
- If nothing else works, then try to relink Oracle Reports executables.
See Note 154512.1 for details.
3. Test it using rwcli60. Steps:
- Set DISPLAY to valid X Windows either in the reports60_server
startup script, or in reports60.sh (if you are manually starting
up the reports server using rwmts60)
- Restart the reports server with this DISPLAY set
- Run report using sample syntax:
rwcli60 server=repserver.world report=test.rdf userid=username/password@db destype=file desname=test.html desformat=html batch=yes
where repserver.world is the name of your reports server services.
If rwcli60 works, go to step 4.
If rwcli60 does not work, then:
- Check the DISPLAY setting in the script that you used to start
up the reports server. Most likely, you used the reports60_server
script which is located in Reports 6i Oracle_Home.
- Review Section 6 (below) to see if any of the scenarios match
your situation.
4. If rwrun60 and rwcli60 work, then the problem is in the CGI or Servlet
setup, and not the Reports Server Services.
For CGI setup, the DISPLAY needs to be set in the CGI shell script, and/or
the 6iserver.conf file. This is found under the Reports 6i Oracle_Home in
the conf directory (e.g. /u01/app/oracle/product/ias/6iserver/conf)
Edit the 6iserver.conf to read:
.
# Forms and Reports CGI needs to have ORACLE_HOME set
SetEnvIf Request_URI "rwcgi60" ORACLE_HOME=/u05/app/oracle/product/iAS9i/6iserver
SetEnvIf Request_URI "rwcgi60" DISPLAY=:0.0
For the Servlet setup, you need to set DISPLAY in the jserv.properties file.
For details, see Note 162453.1.
VI. SCENARIOS WHERE YOU MAY ENCOUNTER REP-3000
==============================================
There are numerous situations where you may encounter the REP-3000 error.
The different scenarios as well as their resolutions are listed below.
These are grouped in the following categories:
1. Reports Version-Specific Issues
2. Oracle Forms Related Issues
3. Oracle Applications Related Issues
4. NLS_LANG Related Issues
5. General Issues
VI-1. REPORTS VERSION-SPECIFIC ISSUES:
------------------------------------
A) REPORTS 6i PATCH5 or HIGHER: Reports No Longer Work After Patch5
Description:
After applying Reports 6i patch 5 or higher, running reports in batch no
longer works. Gives error:
REP-3000: Internal error starting Oracle Toolkit
Why can't the server work anymore without a console/Xwindows setup like
it did before?
Solution:
See Section II above. ("Solution").
Explanation:
In patch 5, development addressed several bugs regarding image display and
resolution. One of the things to come out of this was that we needed to
enforce the requirement for a valid display being set. We have always said
that you needed to have the DISPLAY environment variable set to a valid X
Display on non-Windows platforms. It provides a fundamental capability that
Reports requires for font metrics and rasterization, image manipulation and
conversion, etc.
Essentially, you have been relying on a behavior that was against the
documentation.
Also, to help the graphics/reports integration work better, the software
now accesses the OS to pull Pixel information from the windowing system.
In the past this was hardcoded into the software and it could cause a
problem when images were run on different resolutions. We have found that
in some cases this Pixel check has been the cause of the REP-3000. You can
get around this by setting an environment variable that overrides the OS
windowing check. In the reports60_server script add the line:
REPORTS60_DEFAULT_PIXEL_SIZE=80; export REPORTS60_DEFAULT_PIXEL_SIZE
WARNING: Setting this parameter also overrides the fixes that Patch 5
incorporated for proper report/graphics integration. Note this is not
recommended. You may experience graphic degradation if this is set.
B) REPORTS 9i: Running Report on Web in 9iAS V2 Environment
Description:
You have successfully installed 9iAS V2 on your Unix machine. When
attempting to run a report through a URL you get the following error:
"Oracle Reports Server CGI - Report Job has terminated with error.
Reports Server Replies:
REP-3000: Internal error starting Oracle Toolkit."
Solution:
To ensure that the DISPLAY environment variable is set correctly in a 9iAS V2
environment, or any environment where a Reports9i server is being used, you
have to add an entry referencing this variable in the reports.sh script.
This file is found in the ORACLE_HOME/bin directory.
Explanation:
The reports.sh script is accessed every time that a Reports9i Server engine
is started. By setting the correct value for DISPLAY in this file, and
restarting the appropriate OC4J instance, you ensure that every new server
engine will be accessing the correct information concerning this variable.
C) REPORTS 9i/10g: Reports in-process server gives REP-3000 error when running report
Description:
When running a sample report using the Reports in-process server, the
following error message appears in the browser:
REP-3000: Internal error starting Oracle Toolkit.
Solution:
Ensure that the DISPLAY environment variable is set correctly in the
following configuration file:
9i:
$ORACLE_HOME/j2ee/OC4J_BI_Forms/config/oc4j.properties
10g:
$ORACLE_HOME/opmn/conf/opmn.xml
The default DISPLAY entry is as follows:
9i:
oracle.display=:0.0
10g:
You need to change the default entry to a machine with a valid X server.
For example, to use the X server running on myserver:0.0, you would change
the default entry to:
9i:
oracle.display=myserver:0.0
10g:
After these changes are completed, it is necessary to restart the
Forms/Reports OC4J instance. You can either restart this using
Enterprise Manager, or from the command line using the following commands:
$ cd $ORACLE_HOME/opmn/bin
$ ./opmnctl stopproc type=oc4j instancename=oc4j_bi_forms
$ ./opmnctl startproc type=oc4j instancename=oc4j_bi_forms
Explanation:
When running a Reports Server from the command line, the environment
variable DISPLAY setting is used. However, the Reports in-process server
uses the oc4j.properties or opmn.xml configuration file for the display
setting.
D) ORACLE REPORTS 6.0.5.X: REP-3000 Error Running rwrun60c
Description:
Running a report using rwrun60c fails with the following errors:
REP-3000: Internal error starting Oracle Toolkit.
REP-0548 Problem Initializing Oracle Toolkit.
Solution:
Apply patch 5a for Developer 6.0
or
Use Developer 6i with Patch 1 or higher
or
Use Workaround:
1. Set TERM=vt100
2. Unset ORACLE_TERM
Explanation:
You have encountered a known bug:
Bug 771022 TOOLKIT ERROR WHEN LAUNCH RUNTIME (RWRUN60C)
E) ORACLE DEVELOPER 1.6.1: Running Report in 1.6.1 Environment
Description:
You have set your DISPLAY correctly and the "xclock" product runs without
any problems. You can open an XTERM successfully and can run other motif
and x-windows programs successfully from the server. However, you still
receive the REP-3000 error when running r25runm or any Reports executable
in an Oracle Developer 1.6.1 environment.
Solution:
Set ORA_NLS33 environment variable to:
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/datad2k
Explanation:
Oracle Developer 1.6.1requires ORA_NLS33 to be set for the Reports 2.5 and
Forms 4.5 motif products to run. Other versions of Developer do not need
this variable. This will point the NLS to the correct nlb files. The
ORA_NLS33 is defaulting to $ORACLE_HOME/ocommon/nls/admin/data and picking
up the wrong file.
F) REPORTS 2.5.X: Running Report Using r25runm Batch=Yes On VMS
Description:
You are getting REP-03000 when using R25RUN batch=yes on VMS.
Solution:
Setting mode=character gets rid of the error.
VI-2. ORACLE FORMS RELATED ISSUES:
---------------------------------
A) REP-3000 Using RUN_REPORT_OBJECT After Installing Patch 5
Description:
You are using Reports inside Forms, started with RUN_REPORT_OBJECT (without
REPORT_SERVER specified) or RUN_PRODUCT with batch=yes. After applying
Developer 6i patch 5 or higher, you get the REP-3000 error when you run
reports. This worked fine before installing Patch 5.
Solution:
Set the DISPLAY variable to a valid Xwindows before starting the report
or the Forms listener.
If you are running Webforms with Forms servlet listener, you have to set
the variable in the jserv.properties file.
$ORACLE_HOME/Apache/Jserv/etc/jserv.properties
wrapper.env=DISPLAY=:0.0
You have to restart your apache listener afterwards.
Explanation:
See Section IV-1.A above.
B) REP-3000 Running Forms 4.5.x Executable On MOTIF
Description:
You have set your DISPLAY correctly and the "xclock" product runs without
any problems. You can open an XTERM successfully and can run other motif
and X-Windows programs successfully from the server. However, when run
f45runm or any Forms executable in an Oracle Developer 1.6.1 environment,
you receive one or more of the following errors:
FRM-91111: Internal Error: window system startup failure.
FRM-10039: Unable to start up the Forms Designer.
REP-03000: Internal error starting Oracle Toolkit.
Solution:
Set ORA_NLS33 environment variable to:
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/datad2k
Explanation:
See Section VI-1.D above.
VI-3. ORACLE APPLICATIONS RELATED ISSUES:
-----------------------------------------
A) Running Applications 11i Reports Result in REP-3000
Description:
Using Oracle Applications Release 11i and Reports Server 6i, any report
run from Applications results in a REP-3000 error.
Solution:
Set DISPLAY to a valid Xwindows in the shell scripts that set up your Apps
environment. Set it in the following:
- reports60.csh
- reports60.sh
- reports60_server
- adrepctl.sh (starts the repserver)
- adcmctl.sh (concurrent manager script)
- all 3 ENV files that reside under APPL_TOP:
.env (controls application-environmental script of applmgr)
APPSORA.env (setups up ORACLE_HOME and all the other XX_TOPs.)
APPLSYS.env (defines all the top-level directories and NLS env variables)
Then restart your reports server after modifying these scripts.
If this does not work, then check your NLS_LANG setting in all of
the above scripts. Try setting NLS_LANG to AMERICAN_AMERICA.WE8ISO8859P1.
For more info, see Section 6.IV.A.
Explanation:
Resolving issue is a matter of setting DISPLAY in the appropriate script.
VI-4. NLS_LANG RELATED ISSUES:
-----------------------------
A) REP-3000 When NLS_LANG Is Set to NON Western European Character
Description:
Encounter REP-3000 when the Reports server NLS_LANG is set to any Language,
like AMERICAN_AMERICA.ZHT16BIG5, other than AMERICAN_AMERICA.WE8ISO8859P1.
Solution:
If NLS_LANG is set to AMERICAN_AMERICA.ZHT16BIG5, then set the
TK60_UNKNOWN or ORACLE_UNKNOWN environment variable to:
TK60_UNKNOWN=$ORACLE_HOME/guicommon6/tk60/admin/ZHT
Explanation:
By default, when the _ in NLS_LANG is AMERICAN_AMERICA,
the Reports server looks for the Tk2Motif.rgb in $ORACLE_HOME/guicommon6/tk60/admin
directory. However, for non-western European character sets, the corresponding
Tk2Motif.rgb files reside in individual folders under $ORACLE_HOME/guicommon6/tk60/admin.
For example:
ZHT16BIG5: Tk2Motif.rgb is in $ORACLE_HOME/guicommon6/tk60/admin/ZHT folder.
ZHS16CGB231280: Tk2Motif.rgb is in $ORACLE_HOME/guicommon6/tk60/admin/ZHS folder.
If _ in NLS_LANG matches the then there is no
need to set TK60_UNKNOWN.
For example, if NLS_LANG is set to "TRADITIONAL CHINESE"_TAIWAN.ZHT16BIG5,
then Reports server automatically goes to $ORACLE_HOME/guicommon6/tk60/admin/ZHT
directory to find the correct Tk2Motif.rgb and TK60_UNKNOWN need not be set
in this case.
B) REP-0069, REP-57054 and REP-3000 errors if NLS_LANG is set to UTF8 in UNIX.
Description:
Encounter the following errors when running a report to PDF in UNIX,
when NLS_LANG is set to AMERICAN_AMERICA.UTF8.
REP-0069: Internal error
REP-57054: In-process job terminated: Terminated with error:
and/or
REP-3000: Internal error starting Oracle Toolkit.
SIGSEGV 11* segmentation violation
Solution:
1. Edit the file Tk2Motif.rgb located at /guicommon9/tk90/admin
2. There, you can find this line which is commented:
!Tk2Motif*fontMapCs: iso8859-2=EE8ISO8859P2
3. Add a line below this as :
Tk2Motif*fontMapCs: iso8859-1=UTF8
Explanation:
See explanation from Issue A above.
C) REP-3000 with NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
Description:
Error REP-3000 occurs when starting rwrun60 with NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
After setting NLS_LANG=AMERICAN_AMERICA.US7ASCII, the error is gone.
After setting NLS_LANG=AMERICAN_AMERICA.UTF8, rwrun60 runs OK, too.
Unsetting NLS_LANG altogether works just fine, too.
Solution:
Restore Tk2Motif.rgb - comment out as follows:
change
Tk2Motif*fontMapCs: iso8859-1=UTF8
into
!Tk2Motif*fontMapCs: iso8859-1=UTF8
Explanation:
Tk2Motif.rgb had been modified, the following line was inserted:
Tk2Motif*fontMapCs: iso8859-1=UTF8
This means reports expects UTF8 ...
VI-5. OC4J ISSUES:
-------------------
A) REP-3000 Error when Running Rerport on Web Before Running OC4J Demo.
Description:
REP-3000 Oracle toolkit error when the report is run through rwservlet.
The error doesn't occur if the OC4J DEMO is run before running the report.
Solution:
In order to overcome this problem set the DISPLAY to :0.0.
Explanation:
The reason why the report after running OC4J_DEMO is as follows.
When OC4J_DEMO is run it would use the "OC4J_DEMO.properties" file which
has the property "oracle.display=:0.0". This would set the display to the
server. If the report is run after running OC4J_DEMO you wouldn't get any
errors as the display is already set.
VI-6. GENERAL ISSUES:
-------------------
A) REP-3000 When Trying to Convert a Report
Description:
You are receiving REP-3000 when trying to convert an .RDF report using the convert tool. E.g.
rwcon60 (Reports 6.0.x) or r25convm (Reports 2.5.x) or r25mrepm (Reports 2.5.x), etc
Solution:
You must do one or both of the following:
- Set DISPLAY to valid X Windows
- Pass batch=yes on the command line if you don't have motif installed
on Unix
B) REP-3000 / "XLIB: CONNECTION TO REFUSED BY SERVER" When Running Reports
Description:
When running reports over the WEB generating HTML, you get REP-3000 error
in the browser, and on the server you see:
Xlib:connecion to refused by the server
Xlib:invalid MIT-magic-cookie key...
Solution:
If you are logged on machine A and want to display the output to machine B,
try:
a. on machine A, type 'setenv DISPLAY B:0.0'
b. on machine B, type 'xhost +'
c. start your program on machine A
In this case, set the DISPLAY environment variable on the server where
you have installed the Reports Server and then issue the 'xhost +' command.
If you perform 'xhost +' you need to be logged in as 'root' and you need
to telnet directly to the server.
Explanation:
You have embedded graphics in your report and only when generating HTML
you get the errors. You have set the DISPLAY environment variable; however,
Reports cannot access the display screen.
C) Starting Reports Server In Conjunction With VNC Server Fails
Description:
Starting Reports Server in conjunction with VNC server fails with errors:
REP-3000: Internal error starting Oracle Toolkit.
Xlib: connection to "s0006mq2:13.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Solution:
Drop .Xauthority and re-start Reports Server.
Explanation:
The file .Xauthority in the home directory of the VNC user is corrupt.
D) REP-3000 on Linux RedHat 7.1 after all the above has been accomplished
Description:
Starting Reports Server with PC or VNC server fails with errors:
REP-3000: Internal error starting Oracle Toolkit.
Solution:
The package that is the problem is openmotif-2.2.2-3_ICS
Please make sure that you have installed Motif 2.1.
Motif: Open Motif 2.1.30
Runtime libraries and executables version 2.1.30-4_MLI.hi
Open Motif 1.2 or 2.2 are not certified with 6i.
You can download the latest Open Motif 2.1 binary or source packages from
the Metro Link Web site at:
http://www.metrolink.com/openmotif/
Metro Link's Open Motif binary packages are also available directly from
the Open Group's official Open Motif Web site at:
http://www.opengroup.org/openmotif/
Explanation:
Only Open Motif 2.1 is tested/certified with Reports 6i.
E) Rep-3000 even with DISPLAY pointing to XVFB process
Description:
Starting Reports Server with DISPLAY is pointing to the XVFB process running
fails with errors:
REP-3000: Internal error starting Oracle Toolkit.
Solution:
Create a script with the following commands so that they are executed by
root user at startup.
For SUN-SOLARIS 8
---------------
/usr/X11R6/bin/Xvfb :1 -ac -screen 0 1024x768x8 &
DISPLAY=:1.0;export DISPLAY
/usr/X/bin/olwm &
xhost +
For SUN-SOLARIS 9
---------------
/usr/openwin/bin/Xvfb :1 -screen 0 1152x900x8 &
DISPLAY=:1.0;export DISPLAY
/usr/openwin/bin/twm &
xhost +
For HP-UX and TRU64
--------------------
/usr/bin/X11/Xvfb :1 -ac -screen 0 1024x768x8 &
DISPLAY=:1.0;export DISPLAY
/usr/bin/X11/mwm &
xhost +
For AIX
-------
Use
/usr/bin/X11/xinit -- -force -vfb -x abx -x dbe -x GLX :1
instead of the following:
/usr/bin/X11/X -force -vfb -x abx -x dbe -x GLX :1
DISPLAY=:1.0;export DISPLAY
xhost +
For AIX release 5.0 and 5.1, the syntax should be:
/usr/bin/X11/xinit -- :1 -force -vfb -x abx -x dbe -x GLX
Note that the :1 is in a different position.
For AIX version 5.2 and higher, the syntax to load xvfb and windows manager is:
/usr/lpp/X11/bin/xinit /usr/lpp/X11/bin/mwm -- :1 -vfb -force -x abx -x dbe -x GLX &
For Linux
---------
Linux requires that mwm be started first
/usr/X11R6/bin/mwm &
/usr/X11R6/bin/Xvfb :1 -ac -screen 0 1024x768x8 &
DISPLAY=:1.0; export DISPLAY
xhost +
Explanation:
Olwm and mwm are window managers for the X Window System that implements
parts of the OPEN LOOK graphical user interface. They are standard products
and come built in with Sun Solaris and HP-UX installations respectively.
The "X" command for AIX (second command) creates a vfb that does not include
a Motif Window Manager (MWM) whereas the vfb created using "xinit" does have
the MWM.
If using XVFB, Oracle Reports somehow needs that the Window Manager be
started with automatic display placement.
F) REP-3000 on Linux when try to execute Runtime, Builder or Reports Server
Description:
Get error REP-3000 on Linux platform when trying to start rwbld60
and rwrun60, and running reports using Reports Server.
Solution:
1) Switch to the KDE environment, not just a plain X window session.
2) Add /opt/kde2/lib to the LD_LIBRARY_PATH.
Explanation:
This is an issue of incompatibility between Motif 2.1 and the Gnome
Desktop Manager on Linux. The workaround is to use KDE instead of Gnome.
Reference:
Bug 1416449 REP-3000:INTERNAL ERROR STARTING ORACLE TOOLKIT WHEN REPORT STARTED ON REDHAT6.0
Note 136678.1 Shared Libs Missing Sarting Motif Executables on SuSE Linux with Gnome
G) Rep-3000 with DISPLAY pointing to Xsun process
Description:
Starting Reports Server with DISPLAY pointing to the Xsun process running
fails with error:
REP-3000: Internal error starting Oracle Toolkit.
Solution:
Need to also start up the window manager dtwm when starting up Xsun.
The following is a sample script this is executed by root user at startup.
1. Start up Xsun using following script (which includes windows manager dtwm):
root># more /etc/init.d/dtlogin
#!/bin/sh
#
case "$mode" in
'start')
/usr/openwin/bin/xinit /usr/dt/bin/Xsession -- /usr/openwin/bin/X -nobanner >>/var/dt/Xerrors 2>&1
;;
'stop')
;;
*)
exit 1
;;
esac
exit 0
2. Check to be sure it started:
root># ps -ef |grep Xs
root 7254 7252 0 14:58:03 pts/1 0:00 /bin/ksh /usr/dt/bin/Xsession
root 7252 7237 0 14:58:02 pts/1 0:00 /usr/openwin/bin/xinit /usr/dt/bin/Xsession -- /usr/openwin/bin/X -nobanner
root 8427 6712 0 15:27:06 pts/5 0:00 grep Xs
root># ps -edf| grep wm
root 7333 7331 0 14:58:07 ? 0:01 dtwm
root 8470 6712 0 15:28:35 pts/5 0:00 grep wm
3. As root, set DISPLAY accordingly:
DISPLAY="0:0";export DISPLAY
Check to ensure it's set:
root># echo $DISPLAY
0:0
4. Execute xhost +
Explanation:
Like XVFB, Xsun needs to have the window manager started in order for
Reports to work. The dtwm is the window manager for the X Window System
that implements parts of the OPEN LOOK graphical user interface.
It is a standard product and comes built in with Sun Solaris.
H) Rep-3000 with DISPLAY pointing to vncserver on AIX
Description:
Reports server runs when DISPLAY set to remote Xwindows process.
After vncserver is installed and started, the reports server will fail with
REP-3000.
The cause is that the $HOME/.vnc/xstartup script has conflicts with the
vncserver on this platform.
Solution:
To implement the solution, please execute the following steps:
1. Edit the $HOME/.vnc/xstartup
A) Comment line:
FROM
/usr/dt/bin/dtwm &
TO
#/usr/dt/bin/dtwm &
B) Comment line:
FROM
#mwm &
TO
mwm &
NOTE: The actual process required for each AIX server may vary.
