B Known Issues

This appendix describes known issues with the Oracle DataLens Servers installation and configuration.

B.1 Oracle DataLens Server Conflicts with QuickTime

If your Oracle DataLens Server does not start, it could be because there is a conflict with QuickTime CLASSPATH Environment Variable. You can work around this issue by deleting the CLASSPATH environment variable created by the QuickTime installation, which has no effect on the ability of QuickTime to run.

Delete the QuickTime CLASSPATH variable entry using the following steps:

1. From the Start menu, right-click Computer, select Properties, and then select Advanced Settings.

2. Click Environment Variables.

3. In the System variables section, locate and select the following entry:

   CLASSPATH 'C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip'

4. Click Delete.

5. Click OK twice to close all dialogs.

B.2 Oracle DataLens Server Port Number

The Oracle DataLens Server uses port 2229 by default. On a standard installation with a dedicated server, this should not pose any problems. If there is a problem with this port, then the port number can be changed.

If there is a clash with the default port number (2229), then change to port 8089 or another unused port number. You can do this by stopping your WebLogic Server and then editing the ServerProfiles.xml file located in the EDQP_HOME installation directory.

B.3 Privilege Problems

On Linux and UNIX, verify that the entire EDQP directory structure (by default, this is /opt/Oracle/Middleware/opdq/...) is owned by the administration user you use to administer your Oracle DataLens Server. For more information, see "Establishing the Required User Accounts".

On Windows, the share rights and folder rights must be set so that the administration user you use to administer your Oracle DataLens Server can access the repository share.

B.4 WebLogic Server Installation Issues

When installing WebLogic Server, it is possible that the installation may not complete correctly so installing using the console mode fails because the directory exists. You must uninstall the WebLogic Server product, and then manually remove any remaining directories in the WL_HOME directory.