Troubleshooting Tips for REP-3000 Error when Running PDF/POSTSCRIPT/HTML Reports [ID 207532.1] | |||||
Modified 28-APR-2009 Type TROUBLESHOOTING Status PUBLISHED |
In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
References
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
References
Applies to:
Oracle Application Object Library - Version: 11.5.0 to 11.5.10.2Information in this document applies to any platform.
All UNIX based machines require an X-Windows and Motif environment to run
any GUI-based product. This is the case to execute Bitmapped reports in Oracle
Report. All UNIX-based machines require an X-Windows and Motif environment to
run any GUI-based product.
Oracle Reports Server (Services) need to have access to an appropriate windowing
system. On Windows platforms this is a non-issue.
ems
Purpose
Rep-3000 occurs if running the report as pdf, postscript, xml or html.Last Review Date
April 28, 2009Instructions for the Reader
A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.
Troubleshooting Details
1) Do a "uname -n" on the machine that you have enabled the xhost + session
2) Set the DISPLAY environment variable (on that same machine)to the value
that was returned from step #1
Example:
DISPLAY=:0.0; export DISPLAY
3) Issue the following command on that server
xterm -display.:0.0
or
xterm -display:0.0
Note: the xterm should open a window on the display
:0.0
- verify that a window is open on the display
4) Issue the following command on that server
xdpyinfo -display.:0.0
or
xdpyinfo -display:0.0
Note: the xdpyinfo should show some information about the display
5) In the Application, work with the Oracle Seeded Report "Active Users" -
change the CONCURRENT > PROGRAM > DEFINITION > Output Type to
"Postscript" and Save.
6) On the Concurrent Processing Tier -- edit the
8.0.6 $ORACLE_HOME/guicommon6/tk60/admin/uiprint.txt file
and add the following entry
example:
:PostScript:1:5th FLOOR:default.ppd
7) Shutdown the following
Concurrent Managers
Forms Server
Reports Server
8) Autoconfig enabled instance.
a. Use editcontext or Oracle Application Manager to set the variable DISPLAY in the XML file of the instance.
b. Run the Autoconfig to re-generate the applications configuration files.
c. Files $APPL_TOP/.env and $ORACLE_HOME/.env should have defined the display variable as a customization. Include the
following lines at the end of the file:
# Begin customizations
DISPLAY=":0.0"
export DISPLAY
# End customizations
For instances not using Autoconfig.
Set the DISPLAY to the Server where the "xhost +" has been enabled in the following files
$APPL_TOP/.env
$ORACLE_HOME/.env
$APPLCSF/scripts/adcmctl.sh
$APPLCSF/scripts/adfrmctl.sh
$APPLCSF/scripts/adrepctl.sh
***** All these files must have the same
DISPLAY = setting
9) Start the following
Concurrent Manager
Forms Server
Reports Server
10) Test starting the Reports Runtime Executable from the Command Line.
In a Reflections Session, Can you issue the "ar60runb"
This should open the Reports runtime graphic tool on the xhost server
11) In the Application - Run the "Print Environment Variable Report"
for the "DISPLAY" variable
This will show the value of the Concurrent Manager DISPLAY setting
12) In the Application go to HELP > Diagnostic > Examine -
Click on the LOV for Block and choose
$ENVIRONMENT$
Then go to the 'Field' Section and type in 'DISPLAY'
Click on Value
This will show the Forms Server DISPLAY setting
13) If all the above checks out okay - run the Active Users Report
in the Postscript Format
2) Set the DISPLAY environment variable (on that same machine)to the value
that was returned from step #1
Example:
DISPLAY=
3) Issue the following command on that server
xterm -display
or
xterm -display
Note: the xterm should open a window on the display
- verify that a window is open on the display
4) Issue the following command on that server
xdpyinfo -display
or
xdpyinfo -display
Note: the xdpyinfo should show some information about the display
5) In the Application, work with the Oracle Seeded Report "Active Users" -
change the CONCURRENT > PROGRAM > DEFINITION > Output Type to
"Postscript" and Save.
6) On the Concurrent Processing Tier -- edit the
8.0.6 $ORACLE_HOME/guicommon6/tk60/admin/uiprint.txt file
and add the following entry
example:
7) Shutdown the following
Concurrent Managers
Forms Server
Reports Server
8) Autoconfig enabled instance.
a. Use editcontext or Oracle Application Manager to set the variable DISPLAY in the XML file of the instance.
b. Run the Autoconfig to re-generate the applications configuration files.
c. Files $APPL_TOP/
following lines at the end of the file:
# Begin customizations
DISPLAY="
export DISPLAY
# End customizations
For instances not using Autoconfig.
Set the DISPLAY to the Server where the "xhost +" has been enabled in the following files
$APPL_TOP/
$ORACLE_HOME/
$APPLCSF/scripts/adcmctl.sh
$APPLCSF/scripts/adfrmctl.sh
$APPLCSF/scripts/adrepctl.sh
***** All these files must have the same
DISPLAY =
9) Start the following
Concurrent Manager
Forms Server
Reports Server
10) Test starting the Reports Runtime Executable from the Command Line.
In a Reflections Session, Can you issue the "ar60runb"
This should open the Reports runtime graphic tool on the xhost server
11) In the Application - Run the "Print Environment Variable Report"
for the "DISPLAY" variable
This will show the value of the Concurrent Manager DISPLAY setting
12) In the Application go to HELP > Diagnostic > Examine -
Click on the LOV for Block and choose
$ENVIRONMENT$
Then go to the 'Field' Section and type in 'DISPLAY'
Click on Value
This will show the Forms Server DISPLAY setting
13) If all the above checks out okay - run the Active Users Report
in the Postscript Format
References
NOTE:161566.1 - REP-3000 When Running Ar60runb Or Ar60desbNOTE:200474.1 - Comprehensive REP-3000 Troubleshooting and Overview Guide
It 's amazing article and useful for developers
ReplyDeleteOracle SOA Online Course
This comment has been removed by a blog administrator.
ReplyDelete