REP-3000: Internal error starting Oracle Toolkit==

richardliu1123

 

REP-3000: Internal error starting Oracle Toolkit.

2009-11-26 12:21

开发人员在测试一张报表时，报错，如上。 这张报表输出格式为postscript，为了测试原因所在，先将active user输出格式改为postscript，提交报一样的错误，看来是系统自身的问题了。 搜索之后，发现大部分问题在于x-window的设置上，那就先检查系统吧。 1. Ensure the correct DISPLAY environment variable is set on the E-Business server(s) In the main environment file, as pointed to by $APPLFENV, verify / set the DISPLAY environment variable to an active and available X display server. DISPLAY=<hostname>:<display_number>.0 ; export DISPLAY i.e. DISPLAY=acme.com:0.0 ; export DISPLAY Note 2: Some notes, such as 200474.1, advocates placing the DISPLAY environment variable in startup scripts: adrepctl.sh, adcmctl.sh, gsmstart.sh. Caution should be observed; these scripts override the DISPLAY value in the main environment file and may add a level of confusion if different values are present on each server or script. On Autoconfig ready instances, make any environment variable changes via the Autoconfig Context Editor or Oracle Applications Manager (OAM) and re-run Autoconfig on all nodes in order to ensure that all changes are properly synchronized across all tiers and to prevent the lost of the current environment changes next time Autoconfig runs. 2. Invoke or re-invoke the xhost command as root. On the server where the X display server resides, as root, execute xhost +<hostname1>+<hostname2>… Where <hostname> are the E-Business server names requiring X display server access, such as the Concurrent Processing Server, Oracle Reports Server, etc. Typically, this action needs to be done any time the host with the X display server is bounced. 3. As the "root" user, bounce (restart) the X display server and/or any required window manager (i.e. mwm, olwm, fvwm, twm, etc.) associated with the X display server or window system. Make sure to perform the xhost + command again. Note 3: Please reference the X display server’s guide or contact the vendor for assistance on stopping or starting the X sever or window manager in used. 4. Validate that the 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. If this value is incorrect, then the concurrent processing server is not aware of the proper DISPLAY setting. In short, this environment variable needs to be defined before starting the concurrent processing server. The Sysadmin report "Generate concurrent processing environment information" also lists all environment variables visible to the concurrent processing server. 5. 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. Note 4: If Pasta is being utilized and the IX_RENDERING variable is set without a corresponding displayfontpath entry, a REP-3000 can occur--see Note 361639.1 "Cannot Open Display Font File: ... REP-3000: Internal Error Starting Oracle Toolkit" 6. If bitmap (Postscript, PDF, etc) reports fail from within Oracle Applications, does a report in Postscript format run successfully from the OS command line? a) Login as the applmgr on the host where the concurrent processing server resides and source the main environment file. b) Set the DISPLAY environment variable, if not already set by the main environment file. echo $DISPLAY DISPLAY=<hostname>:0.0 ; export DISPLAY c) Run the "Active Users" report in Postscript format with the ar60runb executable and the following options. Provide the apps password an populate the parameters with the full path of $FND_TOP and $APPLTMP. --- 12.0 Example --- appsrwrun.sh userid=apps/apps report=/<$FND_TOP>/reports/US/FNDSCURS.rdf batch=yes destype=file mode=bitmap desname=/<$APPLTMP>/ActUsr.ps desformat=/<10.1.2.$ORACLE_HOME>/reports/printers/psl132.prt errfile=/<$APPLTMP>/ActUsr.log Note: The full path to appsrwrun.sh is contained within the $APPLORB environment variable --- 11.5 Example --- ar60runb userid=apps/apps report=/<$FND_TOP>/reports/US/FNDSCURS.rdf batch=yes destype=file mode=bitmap desname=/<$APPLTMP>/ActUsr.ps desformat=/<8.0.6.$ORACLE_HOME>/reports60/admin/printer/psl132.prt errfile=/<$APPLTMP>/ActUsr.log 7. If bitmap reports still fail with a REP-3000 from Oracle Applications or from the OS command line, the most likely cause of the error is that the X display server and/or window manager is not accessible, usable, or started. a) Review the following documents for further insight and additional recommended checks: Note 200474.1 "Comprehensive REP-3000 Troubleshooting and Overview Guide", particularly the startup script examples at section "VI-6. GENERAL ISSUES:" Note 207532.1 "Troubleshooting Tips for REP-3000 Error when Running PDF/POSTSCRIPT/HTML Reports" Note 153960.1 "FAQ: X Server testing and troubleshooting" Note 181244.1 "Configuring VNC Or XVFB As The X Server For Applications 11i("Configuring an X Display Server for Applications on Unix Platforms")" b) Update any on-going Oracle service request with the results of the previous steps. c) Use the command xdpyinfo -display <hostname>:<display_number>.0 to inspect and verify the display settings. Please consult the vendor’s documentation for detailed instructions on modifying any settings. d) Contact the vendor of the third party X display server or VNC product for assistance on configuring their product for use. ======================== 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=<uname -n>:0.0; export DISPLAY 在这里先看下系统能否看到display，sysadmin运行请求：Print Environment Variable Report，这个在后面也有，实际上放在前面比较容易发现问题。当前系统使用端口2：0 不过其实2：0不在使用。。。。AIX使用的太少，x-window还要收费，不知道是不是配置的原因，但是走另外的路吧，安装一个VNC，AIX安装VNC，操作大抵跟linux一样，只是配置稍有不同。 安装好之后继续 3) Issue the following command on that server xterm -display <value from uname-n>.<domain>:0.0 or xterm -display <value from uname-n>:0.0 Note: the xterm should open a window on the display <value from uname-n>:0.0 - verify that a window is open on the display 4) Issue the following command on that server xdpyinfo -display <value from uname-n>.<domain>:0.0 or xdpyinfo -display <value from uname-n>: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: <your postscript printername>: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/<SID>.env and $ORACLE_HOME/<SID>.env should have defined the display variable as a customization. Include the following lines at the end of the file: # Begin customizations DISPLAY="<host server name>: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/<SID>.env $ORACLE_HOME/<SID>.env $APPLCSF/scripts/adcmctl.sh $APPLCSF/scripts/adfrmctl.sh $APPLCSF/scripts/adrepctl.sh ***** All these files must have the same DISPLAY = <xhost Server Name:0.0> 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 检查完毕后，有些注意的地方，比如root执行xhost +，比如在EBS的管理用户oracle环境变量里面添加DISPLAY，printenv可以看到display的设置，不要被其中某些错误所吸引，因为它本身可能和这个问题一点关系没有。。。 有一个问题要注意的是，在并发的启动脚本里面，已经把端口写定了，2：0，我想是因为安装的时候数据库层的display参数带过来的， 那其他脚本里面是不是也写定了呢，在启动脚本目录：find . | xargs grep -i display 发现，果真有另外三个已经写定了，端口写定但是主机没有固定，那就把主机也写定吧，修改启动脚本。 之后重新启动AP服务器，ok