B Troubleshooting

Installation Logs

You can find installation log files in the /admin/mwcc/ocs/904/logs/install directory. The log file names are derived from the install type. Installation log files are named in the following format:

<install_type>_install.log.<date_time_stamp>

where:

• <date_time_stamp> is the date and time during the time of installation

• <install_type> could be one or more of the following:

  • ocs_infra - for an Infrastructure installation

  • ocs_infostore - for an Infostore installation

  • ocs_mt - for a Oracle Collaboration Suite mid-tier installation

  • midtier - for a complete middle-tier installation

  • dbtier - for a complete database-tier installation

  • singletier - for a complete single tier installation

Installation Questions and Answers

The following is a list of installation questions and answers.

The installation does not start, and the screen prompt says that the validation failed. Why?

Your system did not meet the minimum system requirements for Oracle Collaboration Suite CC. Review the log file /tmp/system_val.log. Correct any system values that do not meet expected system requirements, and restart the installation. For more information on system requirements, see Chapter 2, " Deployment Requirements".

The installation takes a long time. Why?

Check all the files in the following directories to see if there are any errors:

• $ORACLE_BASE/oraInventory/logs

• /admin/mwcc/ocs/904/logs/install

If you find any errors in these log files, then fix the cause of the errors. Restart the installation. If the problem persists, then contact Oracle Support.

This installation is completed very quickly. Is something wrong?

If the installer completes the installation or exits in less than five minutes, then check to ensure that the installation was performed completely. It is possible that the installation encountered an error and shut down.

Review the latest file in the oraInventory log, which is located at $ORACLE_BASE/oraInventory/logs. If the log file indicates that Enterprise Manager (EMD) is up, then check the status of Enterprise Manager with the following command:

$ emctl status

If you have checked other potential causes of errors, then ensure that you have created the Symlink for the fuser executable, as described in Chapter 5, " Installation and Configuration From the Product CD-ROMs on a Two-Tier System".

Installation Error Messages

The following are error messages that might be recorded in oraInventory logs located in the $ORACLE_BASE/oraInventory/logs directory. You can ignore these error messages.

• org.xml.sax.SAXParseException and stack trace...

• A file not error $ORACLE_HOME/Apache/Apache/fcgi-bin/lexacal-private/ini/webcal.ini

• There is no non empty value found for variable SSO host under section InstallData in file $ORACLE_HOME/config/ias.properties

Configuration Logs

You can find configuration log files in the /admin/mwcc/ocs/904/logs/config directory. The log file names are derived from the configuration type. Configuration log files are named in the following format:

config_<config_type>.log.<date_time_stamp>

where:

• <date_time_stamp> is the date and time during the time of configuration

• <config_type> could be one or more of the following:

  • infostore_email - for Email Infostore configuration

  • infostore_files - for Files Infostore configuration

  • ocsmt_caldb - for Calendar Server configuration

  • infra_dbonly - for Infrastructure database only configuration

  • infra_oidsso - for Infrastructure OID and SSO Server configuration

  • infra_all - for a complete Infrastructure configuration

  • ocsmt_email - for Oracle Collaboration Suite CC mid-tier configuration for Email

  • ocsmt_files - for Oracle Collaboration Suite CC mid-tier configuration for Files

  • ocsmt_calweb - for Oracle Collaboration Suite CC mid-tier configuration for Calendar Web

  • ocsmt_all - for Oracle Collaboration Suite CC mid-tier configuration for the complete Calendar component

  • ocsmt_calall - for complete configuration for Calendar

  • ocsall - for complete Infrastructure, Email Infostore, Files Infostore, and complete Oracle Collaboration Suite mid-tier

When you configure more than one component at the same time, the configuration log file name will have multiple <config_type>’s in it. For example, if you configured Email and Files Infostores at the same time on the database-tier, the configuration log file name will be:

config_infostore_email_infostore_files.log.<date_time_stamp>

Configuration Questions and Answers

The following is a list of configuration questions and answers.

Configuration cannot start, and it prints a message saying that the validation has failed. Why?

Your system did not meet the minimum system requirements for Oracle Collaboration Suite CC. Review the log file /tmp/system_val.log. Correct any system values that do not meet expected system requirements, and restart the configuration.

This configuration is taking a long time. Is something wrong?

The following reasons can cause configuration to take a long time:

• Languages: When you selected languages for the configuration to install, if you chose to select all languages, configuration of these languages will take a long time to complete. Oracle Corporation recommends that you install only languages that you intend to use.

• Middle-tier Configuration Errors: If you are configuring an Oracle Collaboration Suite CC middle-tier deployment, then check the following log files to see if any errors are listed:

  • Appropriate log file in the directory /admin/mwcc/ocs/904/logs/config

  • $ORACLE_HOME/config/infratool.log

  • $ORACLE_HOME/assistants/opca/install.log

  • $ORACLE_HOME/assistants/opca/portal.log

• Infrastructure Configuration Errors: If you are configuring an Oracle Collaboration Suite CC Infrastructure deployment, then check the following log files to see if any errors are listed:

  • All files in the directory /admin/mwcc/ocs/904/logs/config

  • $ORACLE_HOME/config/infratool_instance_jazn.log

  • $ORACLE_HOME/config/schemaload.log

  • $ORACLE_HOME/config/infratool_mod_osso.log

The File $ORACLE_HOME/config/infratool_instance_jazn.log reports an error.

Due to known issues, sometimes the configuration improperly reports an error in this file. If "Configuration failed for MODOSSO" is the only error reported, then this error can be ignored. Oracle Corporation has assigned bug numbers 2421146 and 2419366 to track these issues.

I am configuring Infrastructure with OID and SSO. According to the configuration log file, there are errors. What do I do?

Correct errors as necessary. However, if the configuration log file has error messages such as the following, you can ignore them:

################################################################################

SQL> ERROR:

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

Linux Error: 2: No such file or directory

 

 

SQL> Creating OID entries for SSO

SP2-0640: Not connected

NLS_LANG character set = UTF8

NLS_LANG param = AMERICAN_AMERICA.UTF8

 

################################################################################RRepository Access API throws exception:oracle.ias.repository.schema.SchemaException: Unable to retrieve the requested attributes:javax.naming.NoPermissionException: [LDAP:

error code 50 - Insufficient Access Rights]; remaining name 'orclResourceName=orasso,orclReferenceName=metadb.iasapl23.us.oracle.com,cn=IAS

Infrastructure Databases, cn=IAS, cn=Products, cn=OracleContext'

 

################################################################################

Portal SMI: Oracle home: /opt/oracle/product/infra/9.0.2 was registered. 

Portal SMI: ERROR: Web DAV: /dav_portal/orasso could not be found.

Portal SMI: Wrote DAD count: 1

################################################################################

While I am configuring Unified Messaging, I am unable to start the TNS listener as root. What do I do?

Check the log file $ORACLE_HOME/network/admin/listener_es.log. The most likely cause of this problem is that a sendmail process is already running.

If a sendmail process is running, then log in as root, and stop the sendmail process with the following command:

# /etc/init.d/sendmail stop

Restart the TNS listener as the owner of the middle-tier Oracle home.

Failure of Parameter Validations

If any of the parameter validations fail (you can be see failures in the log files), correct the error and re-run the config.sh script.

Error During Actual Configuration

If the error occurs during the actual configuration, examine the log files in the /admin/mwcc/ocs/904/logs/config directory. Check the log files for errors. Use one of the following ways to work around the error:

• correct the error, if possible

• remove the existing configuration

• remove the entry from certified configuration inventory

• re-run the installation and configuration of that Oracle home

Configuration Error Message

You can ignore the following error message.

ERROR at line 1:
ORA-01649: operation not allowed with a backup controlfile

Configuration Relinking Errors

You can ignore the following configuration relinking errors:

• gcc: $ORACLE_BASE/product/ocsmt_904/rdbms/lib/sllfls.o: No such file or directory

• make: *** [$ORACLE_BASE/product/ocsmt_904/rdbms/lib/sqlldr] Error 1