E Troubleshooting the Oracle Database Companion CD Installation

This appendix contains the following information on troubleshooting:

Verifying Requirements
Reviewing a Log of an Installation Session
Cleaning Up After a Failed Installation
Silent or Noninteractive Installation Response File Error Handling
Images Displaying Incorrectly in Oracle HTML DB
Oracle HTML DB Online Help Not Working

E.1 Verifying Requirements

Before you try any of the troubleshooting steps in this appendix, do the following:

Check Chapter 2, "Oracle Database Companion CD Requirements" to make sure that the system meets the requirements and that you have completed all of the preinstallation tasks.
Read the release notes for the product on your platform before installing it. The release notes are available on the Oracle Database installation media. You can find the latest version of the release notes on the Oracle Technology Network Web site:
```
http://www.oracle.com/technology/index.html
```

E.2 Reviewing a Log of an Installation Session

This section covers the following topics:

Reviewing the Log of an Oracle Companion CD Installation Session
Reviewing the Log of an Oracle HTML DB Installation Session

E.2.1 Reviewing the Log of an Oracle Companion CD Installation Session

Oracle Universal Installer creates the DRIVE_LETTER:\ORACLE_BASE\ORACLE_HOME\Inventory\logs directory the first time it runs to record an inventory of products that it installs on your system as well as other installation information.

The log file is named installActionsdate_time.log, where date_time is the date and time of the installation. For example, installActions2004-055-14_09-00-56-am.log.

You can also view a list of installed components by clicking Installed Products on any window of Oracle Universal Installer.

Note:

Do not delete or manually alter the Inventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system.

The installActionsdate_time.log file contains a log of actions executed during the installation process. This file also records any link errors during installation. Do not delete or alter the installActionsdate_time.log file.

E.2.2 Reviewing the Log of an Oracle HTML DB Installation Session

After you install Oracle HTML DB, Oracle Universal Installer creates a log file in the htmldb directory using the naming convention installYYYY-MM-DD_HH24-MI-SS.log. In a successful installation, the log file contains the following text:

Thank you for installing Oracle HTML DB.
Oracle HTML DB is installed in the FLOWS_010600 schema.

If the log file contains a few errors, it does not necessarily mean that your installation failed. Acceptable errors are noted as such in the log file.

E.3 Cleaning Up After a Failed Installation

This section covers the following topics:

Cleaning Up After a Failed Oracle Companion CD Installation
Cleaning Up After a Failed Oracle HTML DB Installation

E.3.1 Cleaning Up After a Failed Oracle Companion CD Installation

If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory. Perform the following steps to remove the files:

Stop the Oracle HTTP Server as described in the "Starting, Stopping, or Restarting Oracle HTTP Server".
Insert Oracle Database installation media and navigate to the companion directory. Alternatively, navigate to the directory where you downloaded or copied the installation files. Then double-click setup.exe to start Oracle Universal Installer.
Click Deinstall Products on the Welcome window or Installed Products available on any Oracle Universal Installer window. The Inventory window appears, listing installed products.

Select the products that you want to remove and click Remove.

Note:

If you have more than one installation on the system, products installed in other Oracle homes appear in the Inventory window. If you select products from other Oracle homes, they are deinstalled.

If you installed Oracle HTTP Server, manually remove the Oracle HTTP Server Oracle home directory used in the failed installation.
If you installed Oracle HTML DB, follow the steps in the next section.

E.3.2 Cleaning Up After a Failed Oracle HTML DB Installation

In a successful Oracle HTML DB installation, the following banner displays at the end of the installation:

Thank you for installing Oracle HTML DB.
Oracle HTML DB is installed in the FLOWS_010600 schema.

However, if the installation fails, in addition to using Oracle Universal Installer to remove the Oracle HTML DB components, you need to drop either one or two database schemas depending upon the installation type before retrying the installation.

E.3.2.1 Cleaning Up After a Failed Upgrade Installation

In the case of a failed upgrade installation, you should first revert Oracle HTML DB to release 1.5 and then remove the schemas associated with release 1.6.

To revert Oracle HTML DB to release 1.5:

If you altered your images directory, you need to point the text alias /i/ back to images directory for release 1.5.

Execute the following command in SQL*Plus:

Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM, for example:
```
c:\> sqlplus sys/SYS_password as sysdba
```

Execute the following:

SQL> ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;
SQL> exec FLOWS_010600.wwv_flow_upgrade.switch_schemas
('FLOWS_010600','FLOWS_010600');

To remove the release 1.6 schema:

Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM.
Execute the following commands:
```
DROP user FLOWS_010600 CASCADE;
```

E.3.2.2 Cleaning Up After a Failed New Installation

To remove schemas after a failed new installation:

Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM.

Execute the following commands:

drop user FLOWS_010600 cascade;
drop user FLOWS_FILES cascade;

E.4 Silent or Noninteractive Installation Response File Error Handling

To determine whether a silent or nonintereactive installation succeeds or fails, check the silentInstallActionsdate_time.log file, located in the DRIVE_LETTER:\Program Files\Oracle\Inventory\logs directory.

A silent installation fails if:

You do not specify a response file.
You specify an incorrect or incomplete response file.

For example, a common problem is that while all the product-specific data is filled out correctly, the staging area location may be incorrect. If this is the case, check the FROM_LOCATION variable and make sure that it points to the products.xml file in the installation media. In the installation media, this products.xml is in companion\stage.
Oracle Universal Installer encounters an error, such as insufficient disk space.

Oracle Universal Installer or a configuration assistant validates the response file at runtime. If the validation fails, the installation or configuration process ends. Oracle Universal Installer treats values for parameters that are of the wrong context, format, or type as if no value was specified in the file.

E.5 Images Displaying Incorrectly in Oracle HTML DB

If the images in Oracle HTML DB do not display correctly, Oracle HTML DB may be having a problem locating the directory where these images are stored. The directory location for the images is stored in an alias in the marvel.conf file. To address this problem:

Open the marvel.conf file, located in ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf, in a text editor.
Look for an alias to the images directory, which appears similar to the following:
```
Alias /i/ C:/oracle/product/10.2.0/db_HTMLDB/htmldb/images
```
Check for the following problems:
- If the /i/ alias appears more than once, rename the first instance of /i/ to a different alias name. Alternatively, copy the images from the ORACLE_BASE\ORACLE_HOME\htmldb\images directory to the directory defined by the first /i/ alias.
- If the /i/ alias points to an incorrect directory, correct the directory path.

E.6 Oracle HTML DB Online Help Not Working

If users are accessing Oracle HTML DB through a Virtual Host, the online help will not work. Consider the following example:

The hostname of the Oracle HTTP Server where the Oracle HTML DB DAD resides is internal.server.com and the port is 7777.
Users access Oracle HTML DB through a Virtual Host. In their Web browsers, users see external.server.com and the port 80.

In this example, Oracle HTML DB online help will not work if the users cannot access internal.server.com. To resolve this issue, add the following lines to the Oracle HTML DB Database Access Descriptor (DAD) to override the CGI environment variables SERVER_NAME and SERVER_PORT:

PlsqlCGIEnvironmentList SERVER_NAME=external.server.com
PlsqlCGIEnvironmentList SERVER_PORT=80