A Troubleshooting Oracle Content DB Installation

This appendix discusses solutions to common installation problems.

This appendix includes the following topics:

• Verifying Oracle Content DB Requirements

• Troubleshooting Oracle Content DB Installation Errors

• Oracle Content DB Installation Problems and Solutions

• Troubleshooting Configuration Assistants

• Troubleshooting Oracle Real Application Clusters

A.1 Verifying Oracle Content DB Requirements

Review the following information before performing any of the troubleshooting steps in this appendix:

• Ensure that the computer meets the hardware and software requirements specified in Chapter 4, "Preinstallation Requirements for Oracle Content DB Middle Tier".

• Ensure that you have completed all of the preinstallation tasks specified in Chapter 4, "Preinstallation Requirements for Oracle Content DB Middle Tier".

• When installing Oracle Content DB, check that the Oracle Application Server Infrastructure with which you want to associate Oracle Content DB is running during installation.

A.2 Troubleshooting Oracle Content DB Installation Errors

If you encounter an error while running Oracle Universal Installer during the installation of the Oracle Content DB middle tier:

• If you entered incorrect information in one of the Oracle Universal Installer screens, return to that screen by clicking Back until the screen displays.

• If you encounter an error while Oracle Universal Installer is copying or linking files, perform the following tasks:

  1. Note the error and review the following installation logs for causes:

     • oraInventory_location/logs/installActionstimestamp.log

     • oraInventory_location/logs/oraInstalltimestamp.err

     • oraInventory_location/logs/oraInstalltimestamp.out

  2. Remove the failed installation by following the steps in Appendix G, "Deinstalling the Oracle Content DB Middle Tier".

  3. Correct the issue that caused the error and restart the installation.

See Also: "Oracle Content DB Installation Problems and Solutions"

A.3 Oracle Content DB Installation Problems and Solutions

This section includes the following topics:

• Location of Installation Log Files

• Linking Fails and ORA Errors Occur

• Prerequisite Checks Fail at the Start of Installation

• Message About Installing in a Non-Empty Directory

• Oracle Universal Installer Disappears After Running the Preinstallation Checks

• Unable to Clean Up a Failed Installation

• Forgot the Password for the cn=orcladmin Account

• OPMN Configuration Assistant—Start HTTP Server Failures

• WARNING: DCM Service May Not be Available at This Time

A.3.1 Location of Installation Log Files

Oracle Universal Installer writes the following log:

• oraInventory_location/logs/installActionstimestamp.log

• oraInventory_location/logs/oraInstalltimestamp.err

• $ORACLE_HOME/install/make.log

In addition, the Oracle Content DB configuration assistant log (ContentConfig.log) can be found in the following location:

$ORACLE_HOME/content/log/

A.3.2 Linking Fails and ORA Errors Occur

Problem

Linking fails, and ORA errors are displayed during installation.

Solution

Exit Oracle Universal Installer and check the log files for any error message. In particular, check the $ORACLE_HOME/install/make.log file.

Remove the failed installation. Before attempting to reinstall Oracle Content DB, make sure that your computer meets all the requirements listed in Chapter 4, "Preinstallation Requirements for Oracle Content DB Middle Tier".

Check especially the following requirements:

• Ensure that the kernel parameters are set to the proper values. If you change the value of a kernel parameter, you must exit Oracle Universal Installer and restart your computer for the new value to be applied.

• Ensure that you are installing Oracle Content DB in a valid directory. For example, you cannot install Oracle Content DB in a database Oracle home.

  
  

  See Also: "Prerequisite Checks Performed by Oracle Universal Installer" for a list of valid directories

  
  

A.3.3 Prerequisite Checks Fail at the Start of Installation

Problem

The prerequisite checks that are run at the start of installation, fail.

Solution

If the prerequisite checks display warnings about missing operating system patches or patch bundles, the patch may actually be missing, or it may have been superseded. If your computer contains the patch that supersedes it, you can ignore the warning.

A.3.4 Message About Installing in a Non-Empty Directory

Problem

Oracle Universal Installer displays a message that you are installing into a non-empty directory.

Solution

If you start and later abort an installation of Oracle Content DB that proceeds beyond the Specify File Locations screen, Oracle Universal Installer creates the Oracle home directory that you specified. If you later try to install Oracle Content DB again in the same directory, the directory contains files created by Oracle Universal Installer and it gives a warning that the directory is not empty.

You must perform the following tasks:

1. In the warning dialog, click No to return to the Specify File Locations screen.

2. In the Specify File Locations screen, click Installed Products to display the Inventory screen.

   If your Oracle home is listed in the Inventory screen, you have to deinstall the Oracle home.

   
   

   See Also: Appendix G, "Deinstalling the Oracle Content DB Middle Tier" for information about deinstalling the Oracle home

   
   

   If your Oracle home is not listed in the Inventory screen, you can delete the files from the Oracle home and continue with the installation.

A.3.5 Oracle Universal Installer Disappears After Running the Preinstallation Checks

Problem

Oracle Universal Installer disappears after running preinstallation checks.

Solution

The directory that is the mount point of the CD-ROM or DVD-ROM was mounted with incorrect permissions, and this caused the pwd command to not work correctly. When you run pwd, it returns cannot determine current directory.

To fix this problem:

1. Unmount the DVD-ROM.

2. Change permissions of the mount directory to 755.

3. Remount the DVD-ROM.

4. Oracle Universal Installer should now run correctly.

A.3.6 Unable to Clean Up a Failed Installation

If your installation was not successful, you must first deinstall it before you can reinstall Oracle Content DB.

See Also: Appendix G, "Deinstalling the Oracle Content DB Middle Tier" for more information

A.3.7 Forgot the Password for the cn=orcladmin Account

Problem

You forgot or do not know the password for the cn=orcladmin account.

Solution

You can reset the password in the database. The DSE root attribute name is orclsupassword.

Note: After a certain number of failed attempts to connect, the cn=orcladmin account becomes locked. In this case, you must unlock the account. The account can also become locked if the password has expired.

See Also: Oracle Content Database Administrator's Guide for information about unlocking and setting the default password expiration time for the cn=orcladmin account

A.3.8 OPMN Configuration Assistant—Start HTTP Server Failures

Problem

The OPMN Configuration Assistant - Start HTTP Server fails when you rerun it.

Solution

The problem is that Oracle HTTP Server is already running. Before rerunning the configuration assistant, stop Oracle HTTP Server, as follows:

$ $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server

Rerun the OPMN Configuration Assistant - Start HTTP Server.

A.3.9 WARNING: DCM Service May Not be Available at This Time

Problem

When installing the first node of a cluster, the Java Security Configuration Assistant may return the following message:

WARNING: DCM service may not be available at this time to synchronize $ORACLE_HOME/j2ee/home/config/jazn-data.xml file.

This is due to a failure in updating the DCM repository and could happen if your load balancer virtual server is not configured to return immediately to the calling client when the backend services to which it forwards traffic are unavailable.

Solution

To correct the problem:

1. Run the following command after installation completes:

   $ $ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct jazn
   
   

2. Verify that the dcmctl updateConfig command did not return any errors.

A.4 Troubleshooting Configuration Assistants

This section includes the following topics:

• Configuration Assistant Result Codes

• Irrecoverable Errors

A.4.1 Configuration Assistant Result Codes

Configuration assistant failures are noted at the bottom of the installation screen. The configuration assistant interface displays additional information, if applicable. The execution status of the configuration assistant is identified by the result codes listed in Table A-1.

Table A-1 Configuration Assistant Result Codes

Status	Result Code
Configuration Assistant Succeeded	0
Configuration Assistant Failed	1
Configuration Assistant Cancelled	-1

Result codes are written to the oraInventory_location/logs/installActionstimestamp.log file.

A.4.2 Irrecoverable Errors

Some configuration assistant failures are irrecoverable (fatal). You cannot recover from an irrecoverable error by correcting the problem and continuing. You must remove the current installation and reinstall Oracle Content DB. The following tasks describe the recovery procedure:

1. Deinstall the failed installation as described in Appendix G, "Deinstalling the Oracle Content DB Middle Tier".

2. Correct the cause of the irrecoverable error.

3. Reinstall Oracle Content DB.

4. If the error reoccurs, then you must remove all Oracle installations from your computer.

A.5 Troubleshooting Oracle Real Application Clusters

To ensure that the installation succeeds on the remote nodes you choose, select a path for Oracle home that is the same on all chosen nodes and is writable. Otherwise, installation on the remote nodes fails. No error message indicates this failure.

A.6 Need More Help?

For more help troubleshooting Oracle Content DB installation, go to OracleMetaLink at:

http://metalink.oracle.com

If you have a support contract with Oracle, the steps to download any Oracle Content DB patches from OracleMetaLink are:

1. Log into OracleMetaLink.

2. Click Patches & Updates.

3. Ensure that Patch Number is selected in the Simple Search list.

   Enter the required patch number in the adjacent box.

   If you do not know the patch number, select Product or Family in the Simple Search list.

4. Select the appropriate operating system from the Platform or Language list.

5. Click Go.

6. Under Results, click Download to download the patch or click View Readme to go through the information in the readme before downloading the patch.

If you do not find a solution for your problem, open a service request.