Xserver XML and concurrent managers.
REP-3000: Internal error starting Oracle Toolkit :This page can help you resolve error REP-3000 in an 11.5.9 or 11.5.10.2 implementation.
idbasolutions.com Apr 2008
Disclaimer: Apply to a TEST environment first. Use on production systems is at DBAs own risk.
Metalink Notes:
Note 364838.1 Quick Checks for REP-3000: Internal Error Starting Oracle Toolkit.
Note 181244.1 “Configuring VNC Or XVFB As The X Server For Applications 11i(”Configuring an X
Display Server for Applications on Unix Platforms”)”
Note 153960.1 “FAQ: X Server testing and troubleshooting”
MetaLink note 165195.1 titled “Maintaining System Configurations with AutoConfig”.
If you get the following error from any concurrent programs then it might be related to Xserver not running or not being configured correctly:
REP-3000: Internal error starting Oracle Toolkit.
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)
As root install and configure Xserver or “Headless” X display servers such as VNC by following
steps in Metalink note 181244.1.
There must be an Xserver running on the concurrent node.
This is a 3rd party software, typically VNC which should be installed and started by root.
Unix computer vendors ship and support an X display server to run on their video display
hardware. If video display hardware is available on the computer where 9iAS and/or Applications
11i is installed, this is the preferred X display option.
“Headless” X display servers do not require video adapter hardware nor a monitor.
–>See Metalink note 181244.1.
Following are steps to setup Xserver:
======================================
Today: 12-Dec-07
sysadmin installed Xhp on node1 and node2:
ps -aef | grep -i xhp
daemon 9805 9804 0 13:23:58 pts/ta 0:00 /usr/bin/X11/Xhp :10 -screen 0 1024×768x8
-fbdir /var/X11/Xserv
–>This tells me that Xhp is running on 10 so DISPLAY on node1 should be set to:
DISPLAY=your_hostname:your_display_number .0; export DISPLAY
Example:
DISPLAY=acme.com:1.0; export DISPLAY
Put these two line in oratrn and appltrn .profile file:
DISPLAY=node1_host_name.com:10.0; export DISPLAY
DISPLAY=node2_host_name:10.0; export DISPLAY
Edit Context area on each node server db and apps serach and update display. See “Use
autoconfig to regenerate configuration files.doc”
logout and login again.
Stop apps.
as db owner save TNS stuff.
run autoconfig as apps on all node. And for db as well. db first.
logout and login again.
Then gracefull bounce Apps and db on all nodes. Copy original TNS stuff.
Do the following to make sure Xserver is being used by Apps (from Note 364838.1):
1) Concurrent Processing Server sees the correct DISPLAY value?
Run the Sysadmin report “Prints environment variable values” with the “DISPLAY” parameter and
check that the correct DISPLAY value is present.
–>This now shows that DISPLAY is set to node1:10.0 as opposed to before I changed the
context area this wreport used to show node1:0.0
2) Verify that the DISPLAY variable is usable by running a concurrent report in Postscript
format.
Run the Sysadmin report “CP Postscript Report Regression Test” with the parameter BASIC. If the
reports completes successfully, the concurrent processing server is aware of the DISPLAY value
and the current variable value is usable.
–>This run fine no error as opposed to before the Xserver where it failed.
3) Also make sure Output Post Processor (OPP) is working following steps in “XML Publisher
notes.doc”