Oracle Reports Server Installation and Configurationeurope.appliedbiosystems.com/.../oraclereportsserver_solaris.pdf · Oracle Reports Server Installation and Configuration ... 5

Oracle Reports ServerInstallation and ConfigurationSQL*LIMS® 4 Software

Installation Guidefor Solaris operating system

Applera Corporation is committed to providing the world's leading technology and information for life scientists.Applera Corporation consists of the Applied Biosystems and Celera Genomics businesses.

For Research Use Only. Not for use in diagnostic procedures.

Notice

APPLERA CORPORATION MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE. Applera Corporation shall not be liable for errors contained herein or for incidental orconsequential damages in connection with the furnishing, performance, or use of this material.

Copyright Information

Copyright © 2002 Applied Biosystems. All rights reserved. This document or parts thereof may not be reproduced inany form without the written permission of the publisher.

Printed in the United States of America.

Information in this document is subject to change without notice. Applied Biosystems assumes no responsibility forany errors that may appear in this document. This document is believed to be complete and accurate at the time of publication.In no event shall Applied Biosystems be liable for incidental, special, multiple, or consequential damagesin connection with or arising from the use of this document.

Software and firmware programs are protected by copyright. It is unlawful to duplicate these programs in any manner otherthan for the user's personal use. Specifically, it is unlawful to use or duplicate these programs other than for use with thepurchaser's computer.

Trademarks

ABI Prism, Applied Biosystems, and SQL*LIMS are registered trademarks, and AB (Design), ABI, Applera, SQL*GT,SQL*QA, SQL*Protocol, SQL*Stability, and SQL*Schedule are trademarks of Applera Corporation or its subsidiaries in theU.S. and certain other countries.Solaris and Java are trademarks of Sun Microsystems, Inc.OpenVMS is a trademark of Compaq Computer Corporation.Oracle, SQL*Net and SQL*Plus are registered trademarks, and Oracle 8i and PL/SQL are trademarks of Oracle Corporation.Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.All other trademarks are the property of their respective owners.

Printed in the USA, 06/2002

1-1

Installing and Configuring theOracle Reports Server for Solaris

The purpose of this document is to describe the process of installing the Oracle Reports6i Serverapplication on a Sun SPARC Solaris server.

At the time of this writing, the Reports6i Server installation that comes in the Oracle Tools CD Packv3 will NOT run on Solaris 2.7 without an Oracle Patch. The current Oracle patch is called ‘Patch 4a’.It will bring the Reports 6i Server up to version 6.0.8.13.

It is possible that new versions of the patches will exist. In that case, you should compare the patchinstructions for the newest revision to this document and adjust these installation proceduresaccordingly.

BackgroundReviewing all the information at the time of this document, the procedure used to install Reports 6i onSolaris is summarized here:

� Install Reports 6i Release for the Unix platform (from Forms and Reports6i CD)� For Solaris only, apply OS patches required for Patch 4a on the Solaris OS. � Install relevant patch for Oracle Developer 6i for the Unix OS� Configure environment� Configure SQL*LIMS environment� Compile reports from NT platform for the Unix environment. � Verify the Reports server is working with the SQL*LIMS Event server.

ConventionsIn this document variables or values that should be modified to match your environment will bedisplayed in angle brackets or as <variable>.

Installing Developer 6i Software

� To install the Developer 6i software:

1. On the server, connect as the OS user who will own the Oracle Reports Server. In thisdocument, ‘orarpts’ is used as an example. It is recommended that you create an OS userdifferent than any already installed Oracle products on the Unix server.

2. Set the environment variables:setenv DISPLAY <machine_name>:0.0

setenv ORACLE_TERM vt220 (Needed to install in char mode)

For example, if the host name is “zeppo”, then the command is:setenv DISPLAY zeppo:0.0


1-2 Oracle Reports Server for Solaris

3. Create a directory on the server in which to install the 6i software. This directory can be‘parallel’ to the RDBMS server home. For example, if the Oracle server home is:/opt/product/oracle/ora816

The Oracle Reports home can be located at:/opt/product/oracle/repserver

Also, the directory can be located under a different mount point. For this document, theexample Oracle Reports Home will be:/data1/repserver

Do not put the Oracle Reports Home in any existing Oracle Home database directory!

Caution: the directory paths can get to be very long if the starting point is 3 or 4 subdirectories downas the starting point.

4. Create a directory in which to install Reports 6i.

For example, in a c-shell session, do the following:su - root

cd /data1

mkdir repserver

chmod 777 repserver

5. Insert the Oracle Forms and Reports 6i CD into the server CD-ROM drive.

For Solaris, the file manager window automatically appears. Unlike the statement in theOracle Installation Guide, the installer does not automatically run.

6. In the c-shell session, start the character mode Oracle installer:setenv ORACLE_HOME /data1/repserver

cd /cdrom/oracle/orainst

./orainst

� To use the character mode Oracle install tool

1. In the Install Type window of the Install Tool, choose Custom.

2. In the Preamble.txt window, choose OK.

3. In the README.FIRST window, choose OK.

4. In the Installation Activity Choice window, choose "Install, Upgrade or Deinstall Software",then choose OK.

5. In the Installation Options window, select "Install New Product – Do Not Create DBObjects", then choose OK.

6. In the Installation Options – Mount Point window, enter the Mount Point: /data1/repserver

Then choose OK.


Oracle Reports Server for Solaris 1-3

7. The Installation Options – Home Locator window will contain:/data1/repserver/app/oracle/product/

8.0.6 (the default)

Choose OK.

8. In the Environment Variables window:ORACLE_BASE: /data1/repserver/app/oracle

ORACLE_HOME: /data1/repserver/app/oracle/product/8.0.6

Note the path; you will use this later.

Then choose OK.

9. The Logging and Status window will contain:

Installer Log: [ORACLE_HOME]/orainst/install.log

SQL Log: [ORACLE_HOME]/orainst/sql.log

Make file Log: [ORACLE_HOME]/orainst/make.log

OS Log: [ORACLE_HOME]/orainst/os.log

Choose OK.

10. In the Install Source window, select "Install from CD-ROM", then choose OK.

11. In the NLS window, select "American/English", then choose OK.

12. The Information window will contain:

Post installation steps that need to be run by root will be written to:$ORACLE_HOME/orainst/root

Choose OK.

13. In the Software Asset Manager window, select "Oracle Reports Server and Reports Developer6.0.8.8.3", then choose Install.

14. In the X Libraries window:

/usr/openwin/lib (default)

Choose OK

15. In the Motif Library window:

/usr/dt/lib (default)

Choose OK

16. In the GUI Choice window, select all three choices, then choose OK.

17. In the Component Selection window, select all four choices, then choose OK.

18. In the Default Display for Reports Server window:

<machine_name>:0.0 (default)

Choose OK.

19. In the Reports Server Parameters window:

TNS Name: Rep60_<machine_name> (default)

Port: 1949 (default)

Choose OK.



20. In the Reports Server: Web Listener window, select “Use Oracle Web DB Listener,” thenchoose OK.

21. In the WebDB Listener window:

Host Name: <machine_name>

Listener Port: 8000

Choose OK

22. In the Process Startup window, select Yes to start up the processes.

23. In the Reports Security window, select No.

24. In the Configuration Instructions window:$ORACLE_HOME/orainst/reports6iconfig.txt

Select YES and review the information. You should not need to perform any of the INFO orACTION items.

25. In the Installer Actions Completed window, choose OK.

26. In the Software Asset Manager, exit the installer.

At this point you need to run the root.sh file created by the Oracle install.

� To run the root.sh file created by the Oracle install:

1. Enter the following commands:setenv ORACLE_HOME /data1/repserver/app/oracle/product/8.0.6

cd $ORACLE_HOME/orainst

su

./root.sh

2. root.sh prompts you to confirm the environment settings.

Choose ‘Y’.

3. root.sh prompts you to specify a full pathname for the local bin directory.

Enter the Oracle Reports user's home directory path ‘/export/home/orarpts’. Refer toStep 1 on page 1-1 of Installing Developer 6i Software.

4. root.sh prompts you to OK the fact that ORACLE_HOME does not match the home directoryfor Orarpts.

Choose ‘Y’

5. Exit the root account:exit

Installing Patch Sets


Installing Patch SetsNext, download the Developer 6i Patch 4a kit for Solaris from the Applied Biosystems SQL*LIMSserver patches website.

Print and read the release notes.

Unix Operating System Patch Level for SolarisOracle requires your system to be a certain patch level with the Solaris Motif libraries. The followingis taken from the Solaris Patch 4a release notes. Note that there is no patch level for Solaris 2.8. Also,you may have to install other patches that are dependent on the patches listed below.

For Solaris 2.7, Motif patch 107081-19 or higher. This patch has pre-requisite patch requirements of1747364_60, 108376-24, and 107656-07. Review the release notes of the patches to be applied for pre-requisite patch information. Your server may have different prerequisite patch requirements.

� To check for the patch existence and level use the following commands:

1. Solaris 2.7, as a superuser:# patchadd -p | grep <patch number>

2. Contact your system administrator to check for the existence of the Motif patch and if thepatch needs to be applied to the Solaris system. See the Solaris patch release notes for theinstructions to install the OS patches.

Installing Oracle Developer 6i Patches

� To install Oracle developer patches:

1. Determine whether there is an Unzip utility installed on the server. From the OS prompt, issuethe command:which unzip

If your server does not already have an unzip utility installed, you can download a Freeware Unixunzip utility from the www.info-zip.org or any other source. An Unzip utility is needed to unpackthe Oracle patch.

2. Download the relevant patch from the Applied Biosystems SQL*LIMS server patcheswebsite. Print and read the release notes. There may be differences between later patch releasenotes and these instructions.

Solaris Developer Release 6i Patch 4a (Oracle patch number 1747364).

3. After downloading the patch, use the unzip utility to unzip the patch files into the OracleReports Server Home or $ORACLE_REPORTS_HOME directory on the server.

For the Oracle Reports OS Owner the Oracle Reports Home and the Oracle Home will be identical. Inthe rest of the document, all references to the $ORACLE_HOME refer to the Oracle Reports Home.

4. To install, use the instructions in the README. A summary of the steps documented in theREADME file follows.

5. If you are not already logged in, log in to the Oracle Reports owner OS account on the server.

6. Navigate to the user’s home directory.cd ~

7. Edit the .cshrc file for the user to add /usr/ccs/bin to PATH statement:vi .cshrc

http://www.info-zip.org/

Installing Patch Sets


8. Save the .cshrc file.source .cshrc

9. Unzip the patch.

cd $ORACLE_HOME

uncompress developer6i_patch4a.tar.Z

tar -xvf developer6i_patch4a.tar

cd developer6i_patch4

./patch_install.sh |& tee patch_install_p4a.log

10. After installing the patch, check the log file generated (patch_install_p4a.log) for errors.

11. After installing the patch files into the $ORACLE_HOME (the Reports 6i home), modify theLD_LIBRARY_PATH to allow the relink to find the correct libraries.

Enter the following line (not two lines, no line feed or carriage return) in the .cshrc setenv LD_LIBRARY_PATH$ORACLE_HOME/lib:$ORACLE_HOME/network/jre11/lib/sparc/native_threads

12. Then relink the executables:cd $ORACLE_HOME/procbuilder60/lib

make -f ins_procbuilder.mk install

cd $ORACLE_HOME/reports60/lib

make -f ins_reports60w.mk install

cd $ORACLE_HOME/graphics60/lib

make -f ins_graphics60w.mk install

Configuring the Oracle Environment



Adding PrintersEdit the uiprint.txt file that contains printer entries. The file must contain at least one valid printer. Thefile is located in $ORACLE_HOME/guicommon6/tk60/admin”.

� To edit the printer entries:

1. Navigate to the $ORACLE_HOME/guicommon6/tk60/admin directory.cd $ORACLE_HOME/guicommon6/tk60/admin

2. Edit the file uiprint.txt using a text editor.

3. Remove or comment out the "Not a printer entry" line.

4. Add new entries that are valid for your printers.

For example:lp1:PostScript:1:HP4Si connected to mercury:hpljet41.ppd:

Each line contains five fields separated by colons. NOTE: All the fields must be filled and theline must end with a colon.

Printer:Printer_Driver:Toolkit_Driver:Printer_Descr:Printer_Descr_File:

The fields are:

Printer: The name of the printer, as used with the lpr or lp command.

Printer_Driver: Specifies the type of printer driver used for the printer. This can bePostScript, ASCII, or PCL.

Toolkit_Driver: Specifies the version number of the printer driver that should be used by theToolkit. The Toolkit supports 1 for ASCII or Level 1 PostScript printers, 2 for Level 2PostScript printers, and 5 for HP PCL printers.

Printer_Desc: Contains a free-format description of the printer, for example, the speed andthe location of the printer.

Printer_Descr_File: Specifies the printer description file to be used with the printer. It shouldbe one of the following types: ASCII printer would have this set to None. This field is ignoredfor all ASCII printers. If you are using a PostScript printer, this entry should contain the nameof a PPD file. PPD stands for PostScript Printer Description. If there is no PPD file for theprinter, use default.ppd. If you are using PCL printing, this entry should contain the name ofthe HPD file. For more information, refer to the Oracle Forms Server and Reports ServerInstallation Guide.

Note: The first non-commented line in the uiprint.txt file must define a valid printer. Printers thatsupport the PCL5 language are required for Unix. The "Printing Services" and "Saving output to file"may not work properly in the Reports Developer Tools unless the uiprint.txt file is configured properly.

In the uiprint.txt file, do not name the printer “lp”. Also, the printer defined in the system cannot havethe name ‘lp’. If the system printer name is named ‘lp’ you will have to edit the printers.conf file onyour system.

Each .ppd or .hpd file corresponds to a specific printer type. Use the correct file for your printer.



Enabling Connection to the DatabaseAfter you modify the uiprint.txt file you must then edit the Oracle Reports tnsnames.ora file to allowconnection to the database.

This file is located in the $ORACLE_HOME (the Reports 6i home)/network/admin directory. Youneed to add two entries; one for the reports server and another that defines which host, protocol andport to use when connecting to the reports server.

Rep60_<machine_name>=(ADDRESS=(PROTOCOL=tcp)(HOST=<machine_name>)(PORT=1949))

The first entry is normally made by the Reports 6i installation. Make sure it has been created and iscorrect.

Make sure you remove the ‘.’ attached to the <machine_name> in the above string created by theinstaller. The entry created by the Oracle Installer will look like the following: Rep60_harpo=(ADDRESS=(PROTOCOL=tcp)(HOST=harpo.)(PORT=1949))

� To edit the Oracle Reports' tnsnames.ora file:

1. Edit the entry to remove the period after the server name:Rep60_harpo=(ADDRESS=(PROTOCOL=tcp)(HOST=harpo)(PORT=1949))

2. Then in the same file, add an entry for the report server to connect to the Oracle 8i database.

This would look similar to what you would use to connect to the database from a Formsclient.prod1= (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = <machine_name>.mydomain.com) (PORT = 1521)) ) (CONNECT_DATA = (SID = prod1) ) )

This example presumes that there is a database on the system with the followingcharacteristics:

� An SID named "prod1"

� Located on a server with the fully qualified domain name"<machine_name>.mydomain.com". The network DNS server would have to resolve thisname. It can be the actual IP address

� The address of the database's listener is 1521. (You can use ‘lsnrctl stat’ on the databaseserver to reveal this port number)

3. Next, you will need to add some environment variables to the ‘reports60.csh’ file in the$ORACLE_HOME directory of the reports server.

Before editing the file, backup or copy the file and edit one copy and preserve the other copy.



� To edit the reports60.csh file:

1. Edit the file using a file editor and towards the bottom of the file, add the following entries(refer to Section 4.7 of the Oracle Forms Server and Reports Server Installation Guide).setenv TK_PRINTER lp1

setenv TK6_PRINTER lp1

setenv TK_PRINT_STATUS "lpstat -p '%n'"

setenv TK6_PRINTER_STATUS "lpstat -p '%n'"

setenv TK_PRINT "lp -s -d'%n' -n%c"

(%n is for the printer name; %c is for the number of copies)setenv TK6_PRINT lp -s -d'%n' -n%c"

setenv PRINTER lp1

The TK_PRINTER/TK6_PRINTER should match your printer name defined on the serverand the TK_PRINT variable matches the syntax that will match an OS command call to callthe print command and specify a printer.

2. Then modify the indicated lines in the same filesetenv DISPLAY <machine_name>:0.0

setenv ORACLE_HOME /data1/repserver/app/oracle/product/8.0.6

setenv TWO_TASK prod1 (TNSNAMES.ora alias from above)

3. Comment out the following:## setenv TNS_ADMIN < tnsadmin directory >

## setenv ORACLE_SID < ORACLE SID >

## setenv FORMS60_PATH …

## setenv FORMS60_TERMINAL …

4. Remove the string “${LD_LIBRARY_PATH}:” from the LD_LIBRARY_PATH definition.

5. Remove the string “:${PATH}” from the PATH definition.

6. Add the Oracle owner’s path variables.

To make the environment useful, enter all path values from the Oracle OS account .cshrc inthe path definition in this file.

For example, if the Oracle OS account has the following path statement in the .cshrc file: set path=(/bin /usr/bin /usr/ucb /usr/ccs/bin /etc /opt/product/orasvr816 $ORACLE_HOME/bin .)

Define the path statement in the reports60.csh file as:setenv PATH $ORACLE_HOME/bin:/bin:/usr/bin:/usr/ucb:/usr/ccs/bin:/etc:/opt/product/orasvr816

7. Add the path(s) that contains reports to be executed to the definition of REPORTS60_PATH.

Use the fully qualified path names that are used in the lims owner environment for$LIMS_REPORTS and/or $LIMS_USER_REPORTS. These variables are defined for theLIMS Owner in the $LIMS_DIR/v4_0_16/admin/sqllims.environment file. Don't useenvironment variables, since the Oracle account doesn't have these defined. Use colons to addseparate the path for the $LIMS_REPORTS and the $LIMS_USER_REPORTS path values.

setenv REPORTS60_PATH <LIMS_REPORTS path>



Simplifying Oracle Reports Administration - An ExampleTo make it convenient for the user that will be starting the reports server, you may want to set avariable in the Unix Oracle user c-shell.

� To set a variable in the Unix oracle user c-shell configuration file

1. To set a variable called ORACLE_REPORTS_HOME do the following :cd /export/home/orarpts

vi .cshrc

2. Add a line:setenv ORACLE_REPORTS_HOME /data1/repserver/app/oracle/product/8.0.6

3. Save the filesource .cshrc

Using the Developer Tools

� To use the developer tools:

1. Connect as the Unix Oracle Reports user.cd $ORACLE_REPORTS_HOME

source reports60.csh

2. You can then "cd bin" and run any of the Reports utilities (rwrun60 reports runtime; rwbld60reports builder; etc.) or restart the reports server.

Stopping and Starting the Reports Server

� To stop the reports server:

� After sourcing the environment as described, type:reports60_server stop

� To start or restart the reports server:

� Type:reports60_server start

If the Reports server is already running, it will automatically be stopped and restarted by this script.

Configuring the SQL*LIMS Instance


Configuring the SQL*LIMS InstanceThe final step is to log out of the Oracle user and log in to the LIMS_OWNER for the SQL*LIMSinstance. After logging in, you would want to change the variables in the SQL*LIMS instance file todefine the report server home, server name and tns entry.

� To configure the instance:

1. Edit the file that corresponds to $LIMS_DIR/instances/<machine_name>_<oracle_sid>.Change these four values:setenv ORACLE_REPORTS_EXE /<path>/execute_report

setenv ORACLE_REPORTS_SERVER Rep60_<machine_name>

setenv ORACLE_REPORTS_TNS <matching TNS entry>

setenv ORACLE_REPORTS_HOME /data1/repserver/app/oracle/product/8.0.6

where the <path> variable above is the $lims_programs environmental variable from theLIMS Owner account. Usually this value is similar to the following: /pen/sqllimssvr/v4_0_16/bin

The <matching TNS entry> is the Oracle Reports tnsnames.ora alias created for the databaseto which the Report Server will be connected.

By default, there are placeholders for these variables. Use the actual values for yourconfiguration.

2. If the SQL*LIMS server processes are running, you should restart the Event Monitor aftersetting these values.

To restart the LIMS event_monitor as the LIMS Owner:$LIMS_CMD/stop_monitors event_monitor

$LIMS_CMD/monitor event_monitor

Compiling Reports from Another Platform in the Unix Environment


Compiling Reports from Another Platform in the Unix EnvironmentThis section describes how to take an already developed 6i report and compile it for the Unix platform.If you have already done this step or you are creating new reports on Unix, you can skip this section.Note that report (.rep) files compiled in Windows will not run on Unix. You will have to recompile thereports in order to execute the reports in the Unix environment.

� To compile reports for the Unix platform:

1. Connect to the Oracle Reports user account using the su command, so that the session willnot inherit current manually set environment variables.

Do not use the “-” option, as this will load the Oracle OS account environment variables.

2. Configure the environment as follows:cd $ORACLE_REPORTS_HOME

source reports60.csh

cd bin

rwbld60

3. Connect to the database and open a report.

If you are using one of the Applied Biosystems supplied reports, you need to copy the reportfiles from the client CD from the /core and the /schedule directories into the directory$LIMS_REPORTS.

4. Copy only the .rdf files and the .txt and logo.tif files.

The .rep files are compiled for a Windows environment and will not run on Unix. If the filesare being moved to the server via FTP, the .rdf files must be FTP’d in binary mode.

5. From the File menu, select Choose Printer and verify that you can select a printer and that noerrors occur after clicking OK.

Errors here (Invalid Printer, etc) will indicate the TK environment variables are not set, thereis no printer listed in uiprint.txt, or the printer is named “lp”.

6. From the File menu, use Page Setup and verify that no errors occur after clicking OK.

7. Connect to the database as a report developer account.

Reports should not be compiled or tested as the LIMS Owner as a general policy. This can lead toprivilege issues when LIMS Users attempt to run the report. See the article “Testing CustomForms and Reports for SQL*LIMS” in the Winter ’97 issue of the newsletter.

8. Compile all the program units in the report.

From the menu choose Program, Compile, All or use the keyboard shortcut <Shift>-<Ctrl>-K.

9. Recompile the report.

From the menu choose File, Administration, Compile Report or the keyboardshortcut <Ctrl>-t.

10. Run the report and select a file distribution type.

Verify that the report executes correctly and that if a file is generated that it can be opened inthe appropriate application.

11. Run the report to a printer.

Verify that the output is produced on the indicated printer.

12. Change the Owner (chown) and permissions (chmod) of the compiled reports (*.rep files) forthe intended users.

Verifying the Reports Server Running with the LIMS Event Server


Verifying the Reports Server Running with the LIMS Event ServerFor this verification, you will use the SQL*LIMS 4.0.16 client to submit a report to the LIMS eventserver.

� To verify the Reports Server:

1. Set the environment variable EM_DEBUG to N in a LIMS Owner session.

2. Verify that the four ORACLE_REPORTS environment variables are set as defined above inthe instance file.

3. If any environment variables were changed in the previous step restart the LIMS event server.

4. From the SQL*LIMS Client -> Install Event choice, select a server report that is configuredwith a file and printer destination.

You must use a file type even for the printer, as Oracle requires that some value be passedinto the software. The printer will not use the value. Do not use ASCII.

If a file type ever produces an error, try to produce the same output to the same file type in theReports Runtime on the server. Chances are that Oracle doesn't support that file type.

You must specify printer names and file paths that are known to the server. You cannotbrowse, as this will browse on your client PC and not produce a file path that the server canaccess.

5. Then run the event to a file distribution only.

Verify that the event request does not go to ERROR and that the data is in the file in thespecified directory.

6. Repeat the event, but send the output to the printer.

Verify that the output appears correctly on the specified printer.

Troubleshooting Oracle Reports Server and LIMS Configuration


Troubleshooting Oracle Reports Server and LIMS ConfigurationThe Oracle Software is sensitive and must have the correct number of parameters and values must becorrect or problems will appear.

� If requests are not at ERROR, but the output is not produced:

1. Connect as Oracle Reports user and run the environment configuration as described in theprevious section.

2. Then run the following command to look in the process list for stalled requests on the Unixserver:ps -ef | grep rw

The typical output from the ps command would look like this:oracle 29655 14941 0 10:55:03 pts/15 0:00 grep rw

oracle 13154 13152 0 14:37:09 ? 0:00 rwmts60 name=Rep60_zeppo

If there is a thread listed beginning with rwrun60 for an extended period, then the reportserver thread is stuck and you would need to restart the reports server to clear this condition.

3. If repeating the event causes this condition again, then the parameters being passed are thelikely problem.

Either unsupported parameter values are being used or a required one is missing.

� If the WebDB listener is not up, then the port that was specified during installation may bein conflict:

1. Check that the WebDB Listener is running

2. Now check for the WebDB Listener:ps –ef | grep wdb

The typical output from this ps command would look like this:orarpts 8705 8703 0 Dec 14 ? 0:00 wdbstart -f /product/oracle/repserver/app/oracle/product/8.0.6

orarpts 8706 8705 0 Dec 14 ? 0:00 wdblsnr hamlet.pe-c.com 9100

3. Try another port number.

For example: 9100

In order to change the port number you must stop the Oracle Report Server and edit the scriptfile reports60_server in $ORACLE_REPORTS_HOME.

Change two lines in the script, 79 and 102, from the old port number to the new number, forexample:79 pid=`ps -ef | grep wdblsnr | grep 9100 | awk '{print $2}'`

102 echodo wdbstart hamlet.pe-c.com 9100 &

4. Start the report server and check for the processes again.

� Report does not generate output:

1. Verify that the report uses synonyms on datagroup views, to test the report from the OS createa user specifically to develop and test reports.

2. See the “Requests at ERROR” technique for procedures to create an Oracle Reports developeruser.

Troubleshooting Oracle Reports Server and LIMS Configuration


� Requests at ERROR:

Another technique, if requests are at ERROR, is to do the following. This requires setting theenvironmental variable EM_DEBUG=N.

1. Open the event server log in $LIMS_ERROR.

2. Find the request and select the entire string where it indicates the following:

(Apr-02-2001 08:41:21, 4): Running the following cmd: (… long command string)

3. Copy and paste this to a file and place it in the $ORACLE_REPORTS_HOME/bin directory.

4. Change its permissions to be executable (chmod 777).

5. Edit the file and provide a valid USERID triplet: username/password@alias.

6. Enroll a “Reports Developer” user in SQL*LIMS, determine the accessid and then alter theaccessid account password.

7. Log into the Report Developer and also Reports Runtime with this accessid to test the outputof reports with the same privileges that a user in SQL*LIMS would have inside theSQL*LIMS application.

To determine the accessid for the new SQL*LIMS user account:select accessid from nai_users where userid = <username>;

To alter the password for the accessid to a known value:alter user <accessid> identified by <any password>;

Once the password is modified for the Oracle account or accessid, the SQL*LIMS user will no longerbe able to log into SQL*LIMS client. This is because the encrypted password has been modified for theLIMSUSER account. You can use SGU to reset all of the LIMSUSER passwords to restore theaccount(s) and allow connections to the SQL*LIMS client. In the $LIMS_PROGRAMS directory, issuethe following command as the LIMS Owner account. sgu / feedback option=5

8. After the Report Developer account is prepared, you can execute this script (from Step 5) asthe prepared accessid to help diagnose Oracle configuration problems.

Doing so isolates SQL*LIMS from the problem and provides more direct access to the Oraclemessages.

� Checking Report Requests

To check if the report requests are getting to the Report Server, Oracle provides some commandsthat can be run from your web browser.

1. To check the report queue and job status, use this URL:http://<servername>:<port>/dev60cgi/rwcgi60/showjobs? server=<ReportServerName>

For example:http://hamlet:9100/dev60cgi/rwcgi60/showjobs? server=Rep60_hamlet.

2. To run a report, use this URL:http://<servername>:<port>//dev60html/runrep.htm

For example:http://hamlet.:9100/dev60html/runrep.htm

3. To check general report processing, use the test .rdf provided by Oracle.

This report makes a connection to the database and prints the system date.

mailto:username/password@alias

Appendix - Examples of Report Files


Appendix - Examples of Report FilesNote: This example file is taken from an HP-UX installation.

Example of reports60.csh File# $Header: reports60.csh@@/main/TOOLS_DEV2K_994/6 \

# Checked in on Fri Jan 28 11:17:08 PST 2000 by mverma \

# Copyright (c) 60, 2000 by Oracle Corporation. All Rights Reserved. \

# $

## Example file to set environment variables in c-shell for Oracle Reports6i.

## Refer to Install Doc for more detail on each of these environment

## variables. You need to modify all the environment variables before doing

## source on this file ( % source reports60.csh ).

setenv DISPLAY 123.456.78.910:0.0

setenv ORACLE_HOME /data/repserver/app/oracle/product/8.0.6

## if you need more than one directory in your path, all directories

## should be separated by ':'

setenv PATH $ORACLE_HOME/bin:${PATH}

setenv SHLIB_PATH $ORACLE_HOME/lib:$ORACLE_HOME/network/jre11/lib/PA_RISC/ native_threads:/usr/lib

## You need to set TNS_ADMIN and TWO_TASK

## or ORACLE_SID to connect to database

#setenv TNS_ADMIN < tnsadmin directory >

#setenv TWO_TASK sqalims

#setenv ORACLE_SID < ORACLE SID >

## setting for all products

#if [ "$NLS_LANG" = "" ]

#then

#setenv NLS_LANG AMERICAN_AMERICA.WE8ISO8859P1

#fi

setenv ORACLE_TERM vt220

setenv TK60_ICON $ORACLE_HOME/tools/devdem60/bin/icon

setenv UI_ICON $TK60_ICON

setenv DEMO60 $ORACLE_HOME/tools/devdem60

## setting for Forms Runtime

#setenv FORMS60_PATH $ORACLE_HOME/tools/devdem60/demo/forms

#setenv FORMS60_TERMINAL $ORACLE_HOME/forms60/admin/terminal/US



## setting for Reports Runtime

setenv REPORTS60_PATH $ORACLE_HOME/tools/devdem60/demo/reports:/pen/sqllimssvr

/v4_0_16/reports:/home/sqaora

setenv REPORTS60_TERMINAL $ORACLE_HOME/reports60/admin/terminal/US

setenv REPORTS60_TMP /tmp

setenv REPORTS60_CLASSPATH $ORACLE_HOME/network/jre11/lib/rt.jar:$ORACLE_HO

ME/reports60/java/myreports60.jar:$ORACLE_HOME/reports60/java/xmlparser.jar

setenv REPORTS60_JNI_LIB$ORACLE_HOME/network/jre11/lib/PA_RISC/native_threads/libjava.sl

setenv REPORTS60_DEV2K FALSE

## If REPORTS60_NO_DUMMY_PRINTER is set, no printer needs to be set up

## for Reports Server.

##setenv REPORTS60_NO_DUMMY_PRINTER

## setting for Graphics Runtime

#setenv GRAPHICS60_PATH$ORACLE_HOME/tools/devdem60/demo/graphics:$ORACLE_HOME/tools/devdem60/demo/ forms:$ORACLE_HOME/graphics60/admin/sql:$ORACLE_HOME/

tools/devdem60/admin

#setenv SQLLIB_PATH $ORACLE_HOME/tools/devdem60/demo/forms

## setting for Web Graphics

#setenv GRAPHICS_WEB_DIR $ORACLE_HOME/tools/devdem60/demo/graphics

#setenv OWS_IMG_DIR $ORACLE_HOME/tools/devdem60/web

## setting for Project Builder

#setenv ORACLE_AUTOREG $ORACLE_HOME/guicommon6/tk60/admin/

#

#

setenv TK_PRINTER lp1

setenv TK6_PRINTER lp1

setenv TK_PRINT_STATUS "lpstat -p '%n'"

setenv TK6_PRINT_STATUS "lpstat -p '%n'"

##setenv REPORTS60_NO_DUMMY_PRINTER yes

setenv TK_PRINT "lp -s -d'%n' -n%c"

##setenv TK_PRINT echo

setenv TK6_PRINT "lp -s -d'%n' -n%c"

##setenv PRINTER lp1



Example of tnsnames.ora file for Report Server

Rep60_zeppo=(ADDRESS=(PROTOCOL=tcp)(HOST=zeppo)(PORT=1949))

prod = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = zeppo.sjo.pe-c.com) (PORT = 1521)) ) (CONNECT_DATA = (SID = prod) ) )

Documents

Oracle Reports Server Installation and Configurationeurope.appliedbiosystems.com/.../oraclereportsserver_solaris.pdf · Oracle Reports Server Installation and Configuration ... 5