Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.2) for Microsoft Windows Part Number B25463-03 |
|
|
View PDF |
This appendix describes common installation problems and solutions.
This appendix contains the following sections:
Section K.7, "Troubleshooting Administration Errors After Installation"
Section K.8, "Troubleshooting Oracle Collaboration Suite Web Client Configuration"
Section K.9, "Troubleshooting Oracle Real Application Clusters"
Review the following information before performing any of the troubleshooting steps in this appendix:
Ensure that the computer meets the requirements specified in Chapter 2.
Ensure that you have completed all of the preinstallation tasks specified in Chapter 3.
If you are installing Oracle Collaboration Suite Applications, check that the Infrastructure that you want to associate the Oracle Collaboration Suite Applications with is running during installation.
Read the Oracle Collaboration Suite Release Notes for Microsoft Windows prior to installing Oracle Collaboration Suite. The release notes are available with the platform-specific documentation. The most current version of the release notes is available on Oracle Technology Network at
If you are serving non-English content and forgot to install additional languages as explained in Section 1.7, the user interface might not be displayed properly because the required fonts were not installed. You can fix this by installing the fonts from the Oracle Metadata Repository Creation Assistant and Utilities CD-ROM. The steps to do so are as follows:
Insert and mount the Oracle Application Server Metadata Repository Creation Assistant 10g (10.1.2.0.2) CD-ROM.
Copy the contents of the utilities\fonts
directory on the CD-ROM to the ORACLE_HOME\jdk\jre\lib\fonts
directory.
This section describes the general tips for troubleshooting installation failures. See Section K.4 for specific failures and their solutions.
If you encounter an error during the installation of Oracle Collaboration Suite:
If you entered incorrect information about one of the installation screens, return to that screen by clicking Back until you see the screen.
Exit the installer only to access the component log files. The log files located in the ORACLE_HOME\cfgtoollogs
directory are inaccessible if the installer is still in use.
If you encounter an error while the installer is copying or linking files, perform the following tasks:
Note the error and review the installation logs for causes:
inventory_location\
logs
\installActions
timestamp
.log
inventory_location
\logs\oraInstall
timestamp
.err
inventory_location
\logs\oraInstall
timestamp
.out
The default inventory_location
is:
C:\Program Files\Oracle\Inventory
Remove the failed installation by following the steps in Appendix J.
Correct the issue that caused the error.
Restart the installation.
This section describes common installation problems and solutions:
Section K.4.3, "Prerequisite Checks Fail at the Start of Installation"
Section K.4.4, "Message About Installing in a Non-Empty Directory"
Section K.4.6, "Forgot the Password for the cn=orcladmin Account"
Section K.4.8, "Installer Does Not Display Correct Database Name for OracleAS Metadata Repository"
Section K.4.10, "OracleAS Randomize Password Configuration Assistant Failures"
Section K.4.11, "Database Configuration Assistant (DBCA) Failures"
Section K.4.12, "Harmless Error Message from Database Configuration Assistant (DBCA)"
Section K.4.14, "OPMN Configuration Assistant - Start HTTP Server Failures"
Section K.4.15, "OPMN Configuration Assistant - Start DAS Instance Failures"
Section K.4.16, "OPMN Configuration Assistant - Start OCA Failures"
Section K.4.17, "WARNING: DCM Service May Not be Available at This Time"
There are two sets of log files:
The installer writes the following log files:
oraInventory_location
\logs\installActions
timestamp
.log
oraInventory_location\logs\oraInstall
timestamp
.err
oraInventory_location
\logs\oraInstall
timestamp
.out
%ORACLE_HOME%
\install\make.log
The configuration assistants write log files in the %ORACLE_HOME%
\cfgtoollogs
directory.
Note that if you want to access the log files created by the configuration assistants, you need to exit the installer first. The log files are inaccessible if the installer is still in use.
Problem
Linking failed, and ORA errors were displayed during installation
Solution
Exit the 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 reinstalling Oracle Collaboration Suite, make sure that your computer meets all the requirements listed in Chapter 2.
Check especially the following requirements:
Check that the kernel parameters are set to the proper values. Note that if you change the value of a kernel parameter, you must exit the installer and restart your computer for the new value to take effect.
Check that you are installing Oracle Collaboration Suite in a valid directory. For example, you cannot install Oracle Collaboration Suite in a database Oracle home. See Section 2.9 for a complete list.
Problem
The prerequisite checks that are run at the start of installation failed
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.
Problem
The installer displays a message that you are installing into a non-empty directory.
Solution
If you started an installation and went beyond the Specify File Locations screen, but did not complete the installation, then the installer has already created the Oracle home directory that you specified. If you later try to install again in the same directory, which contains some files created by the installer, the installer gives a warning that the directory is not empty.
You must perform the following tasks:
In the warning dialog, click No to return to the Specify File Locations screen.
In the Specify File Locations screen, click Installed Products. This displays the Inventory screen.
If your Oracle home is listed in the Inventory screen, then you have to deinstall the Oracle home. See Appendix J for details.
If your Oracle home is not listed in the Inventory screen, then you can just delete the files from the Oracle home and continue with the installation.
If your installation was not successful, you have to deinstall it first before you can install Oracle Collaboration Suite again. Refer to Appendix J for instructions.
Problem
You forgot 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 have to unlock the account. See the next section, Section K.4.7, for instructions on how to unlock the account. |
Problem
The cn=orcladmin
account becomes locked after 10 failed attempts to connect. This is controlled by the password policy. 10
failed attempts is the default value.
Solution
If you know the cn=orcladmin
password, then you can unlock the account by running the following command:
Drive_Letter:\%ORACLE_HOME%\bin\oidpasswd> connect=dbsid unlock_su_acct=true
In the preceding comamnd, dbsid
is the SID for the database. For example:
Drive_Letter:\%ORACLE_HOME%\bin\oidpasswd> connect=orcl unlock_su_acct=true OID DB user password: enter_ODS_password OID superuser account unlocked successfully.
The command prompts for the password of the ODS schema. By default, the ODS password is the same as for the cn=orcladmin
and ias_admin accounts, which you entered during installation.
To change the password policy, see the Oracle Internet Directory Administrator's Guide.
Problem
During the Applications tier installation, in the Select OracleAS Metadata Repository screen, which is the screen where you select the OracleAS Metadata Repository that you want to use for the Applications tier, the installer does not display correctly the names of the available OracleAS Metadata Repository databases.
Solution
Check the log file oraInventory
\logs\installActions
timestamp
.log
. Look for the following lines:
*** Select OracleAS Metadata Repository Page*** Error:*** Alert: Error validating repository on multiple hosts and ports. A database hostname or port is missing.
If you see these lines, it means that your OracleAS Metadata Repository database name contains PORT
or HOST
in uppercase characters. To fix the problem, change the name of the database so that it does not contain PORT
or HOST
in uppercase characters.
This section describes the general tips for troubleshooting configuration assistant failures. See Section K.6 for specific configuration assistant failures.
Problem
Configuration assistant failed
Solution
Configuration assistants fail for a variety of reasons. Some things you can check are:
Check that the listener, database, and Oracle Internet Directory associated with the Oracle Collaboration Suite Infrastructure are up and running. If not, start them up and click Retry to rerun the configuration assistant that failed.
Check the log files for the failed configuration assistant to determine the problem. The log files are located in the %ORACLE_HOME%
\cfgtoollogs
directory.
Fix the problem indicated in the log file, and click Retry to rerun the failed configuration assistant.
Before rerunning OracleAS Randomize Password Configuration Assistant, you need to perform these steps:
Start Oracle Directory Manager.
Enter the Oracle Internet Directory host name, port, user name, and password.
Expand Entry Management, cn=OracleContext, cn=Products, cn=IAS, cn=IAS Infrastructure Databases.
Select orclreferencename=your_globaldb_name
.
For each schema under the your_globaldb_name
tree, there is an orclreferencename
entry. For the orclreferencename
entry:
Change the value of the orclpassword
attribute to the schema name. For example, if wireless
is the schema name, change the orclpassword
attribute value to wireless
.
Change orclflexattribute1
to false.
Click Apply.
Perform these steps for all the schemas except ODS
and OEM_REPOSITORY
.
Using SQL*Plus, log in to the database where the OracleAS Randomize Password Configuration Assistant failure is occurring, and run the following script.
prompt> sqlplus "sys/password as sysdba" SQL> @ORACLE_HOME\assistants\dbca\admin\unlock.sql
In the preceding command, password
specifies the password for the SYS user.
Rerun the OracleAS Randomize Password Configuration Assistant.
Problem
DBCA fails with the following error:
Open wallet failedoracle.net.config.ServiceAliasException at oracle.net.config.ServiceAlias.<init>(Compiled Code) at oracle.net.config.Service.<init>(Compiled Code) at oracle.net.config.DatabaseService.<init>(Compiled Code) at oracle.sysman.assistants.util.NetworkUtils.registerDBWithDirSrvc(NetworkUtils.j ava:1137) at oracle.sysman.assistants.dbca.backend.DirServiceStep.executePreReqImpl(Compiled Code) at oracle.sysman.assistants.dbca.backend.PrerequisiteStep.executeImpl(Prerequisite Step.java:149) at oracle.sysman.assistants.dbca.backend.Step.execute(Compiled Code) at oracle.sysman.assistants.dbca.backend.PostDBCreationStep.executeImpl(Compiled Code) at oracle.sysman.assistants.dbca.backend.Step.execute(Compiled Code) at oracle.sysman.assistants.dbca.backend.Host$ModeRunner.run(Compiled Code) at java.lang.Thread.run(Thread.java:466) ERROR :oracle.sysman.assistants.util.NetAPIException
Solution
This error occurs if the TNS_ADMIN environment variable is set. The TNS_ADMIN environment variable should not be set (see Section 2.6). If it is set, unset it and rerun DBCA by clicking Retry in the Configuration Assistants screen.
If you see the following "error copying OC4J config files" message in your log file, the message is harmless and can be ignored.
Nov 25, 2004 9:07:30 PM oracle.sysman.emcp.EMConfig updateReposVars INFO: Updating file /ASInstalls/ASInfra/sysman/emdrep/config/repository.variables ... Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig addPortEntries INFO: Updating file /ASInstalls/ASInfra/install/portlist.ini ... Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateEmdProps INFO: Updating file /ASInstalls/ASInfra/sysman/config/emd.properties ... Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateConfigFiles INFO: targets.xml file is updated successfully Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateEmomsProps INFO: Updating file /ASInstalls/ASInfra/sysman/config/emoms.properties ... Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateConfigFiles INFO: emoms.properties file is updated successfully Nov 25, 2004 9:07:40 PM oracle.sysman.emcp.EMConfig copyOC4JDir WARNING: Error copying OC4J config files from /ASInstalls/ASInfra/oc4j/j2ee/OC4J_DBConsole to /ASInstalls/ASInfra/oc4j/j2ee/OC4J_DBConsole_hostname.domain_portaldb Nov 25, 2004 9:07:40 PM oracle.sysman.emcp.EMConfig startOMS INFO: Starting the DBConsole ... Nov 25, 2004 9:08:26 PM oracle.sysman.emcp.EMConfig perform INFO: DBConsole is started successfully
Problem
The OracleAS Certificate Authority Configuration Assistant fails with following error (in the oca_install.log
file) for remote Metadata Repository:
checkAndClean : Error: Repository chosen for this oca installation is already used by other oca instance java.sql.SQLException: ORA-01017: invalid username/password; logon denied
Solution
Perform the following steps to resolve this error:
End the installer session.
Set the environment variables and run %ORACLE_HOME%
\cfgtoollogs\configToolCommands
.
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 with the following command:
Drive_Letter:\%ORACLE_HOME%\opmn\bin\>opmnctl stopproc ias-component=HTTP_Server
Rerun the OPMN Configuration Assistant - Start HTTP Server.
Problem
The OPMN Configuration Assistant - Start DAS Instance fails when you rerun it.
Solution
The problem is that the Oracle Delegated Administration Services instance is already running. Before rerunning the configuration assistant, stop the Oracle Delegated Administration Services instance by using the following command:
Drive_Letter:\%ORACLE_HOME%\opmn\bin\>opmnctl stopproc ias-component=OC4J_Security
Rerun the OPMN Configuration Assistant - Start DAS Instance.
Problem
The OPMN Configuration Assistant - Start OCA fails when you rerun it.
Solution
The problem is that the OCA instance is already running. Before rerunning the configuration assistant, stop the OCA instance with the following command:
Drive_Letter:\%ORACLE_HOME%\opmn\bin\> opmnctl stopproc ias-component=OC4J instancename=oca
Rerun the OPMN Configuration Assistant - Start OCA.
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
Perform the following steps to correct the problem:
Run the following command after installation completes:
Drive_Letter:\%ORACLE_HOME%\dcm\bin\>dcmctl updateConfig -ct jazn
Verify that the dcmctl updateConfig
command did not return any errors.
Use the following command to verify that the password is correct:
Drive_Letter:\%ORACLE_HOME%\jdk\bin\>java -Doracle.security.jazn.config=.\jazn\install\jazn.xml -jar jazn.jar -checkpasswd jazn.com admin -pw admin_password
Problem
The following warning message and pop-up windows appear after the completion of the single-computer installation:
"The application failed to initialize properly (0xc0000142). Click on OK to terminate the application."
This problem occurs if the desktop heap in the WIN32 subsystem is depleted.
Solution
To resolve this problem, stop the installation and perform the following steps:
Select Start, Run to open the Run dialog box.
Enter Regedit in the Open field.
The Registry Editor window appears. From the HKEY_LOCAL_MACHINE
subtree, go to the \System\CurrentControlSet\Control\Session Manager\SubSystems
key.
Select Windows.
From the Edit menu, select String.
The SharedSection
parameter value will be similar to the following:
SharedSection=xxxx,yyyy,zzzz
The value xxxx
represents the heap size common to all desktops. The value yyyy
defines the size of the desktop heap and prevents memory-intensive applications from consuming too many resources. The value zzzz
controls the size of the desktop heap for non-interactive services.
In addition to the preceding three values of the SharedSection
parameter, there can also be a fourth value, aaaa
, which controls the heap size of Terminal Services.
Increase the value of zzzz
from 512
to any value between 1024 to 3072 depending on your configuration.
Restart the computer.
Start the Oracle Collaboration Suite installation again.
For more information, refer to
http://support.microsoft.com/default.aspx?scid=kb;EN-US;184802
Problem
On some Microsoft Windows operating systems, Oracle Collaboration Suite Databases with large SGA_TARGET and SGA_MAX_SIZE values might crash.
This occurs because out of the default 4 GB of the address space available on Microsoft Windows, the upper 2 GB of the address space is usually reserved for the system. This only leaves 2 GBs available for the processes to use, causing resource-intensive setups to crash under heavy load.
This problem rarely occurs on Microsoft Windows Server 2003, Microsoft Windows NT 4 (Enterprise Edition), Microsoft Windows 2000 Advanced Server, and Microsoft Windows 2000 Datacenter Server.
Solution
To resolve this problem, perform the following steps:
If you are using Microsoft Windows Server 2003, Microsoft Windows NT 4 (Enterprise Edition), Microsoft Windows 2000 Advanced Server, and Microsoft Windows 2000 Datacenter Server, perform the following steps:
Select Start, Run to open the Run dialog box.
Enter Regedit in the Open field.
The Registry Editor window appears. Locate the HKLM\System\CurrentControlSet\Control\SystemStartOptions
registry key.
Now locate the /3G
and /USERVA
boot options. If you can not find these options, add them.
Reboot your computer.
Performing these steps will configure your system such that only the upper 1 GB of the address space is reserved for the system, leaving 3 GBs of address space available for use by the processes. Refer to your Microsoft Windows operating system manual for more information.
The second workaround applies in the following cases:
You are not using Microsoft Windows Server 2003, Microsoft Windows NT 4 (Enterprise Edition), Microsoft Windows 2000 Advanced Server, or Microsoft Windows 2000 Datacenter Server.
You are using one of the Microsoft Windows operating systems mentioned earlier, but the problem still persists even after you follow the preceding steps.
In this case, you must lower the values of SGA_TARGET and SGA_MAX_SIZE in your database. Values less than 800 MB will prevent this issue in any small or middle-sized Oracle Collaboration Suite deployments. If you are running a more complicated configuration (such as, large number of Infrastructrure tiers or Applications tiers), then you must lower these values further.
Refer to Oracle 10.1 Database Performance Tuning Guide for more information.
This section contains the following topics:
To troubleshoot errors that occur when configuration assistants are running:
Review the installation log files listed in Section K.3.
Review the configuration assistant log files located in the ORACLE_HOME\cfgtoollogs
directory for a specific Oracle Collaboration Suite configuration assistant. Try to fix the issue that caused the error.
If you see a "Fatal Error. Reinstall" message, try to find the cause of the problem by analyzing the log files. Refer to Section K.6.4 for further instructions.
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 these result codes:
Status | Result Code |
---|---|
Configuration Assistant Succeeded | 0 |
Configuration Assistant Failed | 1 |
Configuration Assistant Cancelled | -1 |
Result codes are written to the following log file:
C:\Program Files\Oracle\Inventory\logs\installActions
timestamp
.log
During the installation, configuration assistants run when the Configuration Assistants screen appears. If a configuration assistant fails, try the following procedure to correct the problem:
Review the installation log files.
Review the log files for each configuration assistant located in the ORACLE_HOME\cfgtoollogs
directory (Example: Drive_Letter:\oracle\data\mtier\cfgtoollogs
orDrive_Letter:\oracle\data\infra\cfgtoollogs
).
Refer to the following:
If the failed configuration assistant has any dependencies, then run the dependencies again. You must do this even if the dependency completed successfully.
Run the failed configuration assistant again. If you are using the installer, select the configuration assistant and click Retry.
If the configuration assistant fails again after you click Retry, then remove the C:\Temp\EM_CONFIG_INSTALL.lk
file and try rerunning the configuration assistant.
If the configuration assistant fails again after you click Retry, then remove the component entry from the ORACLE_HOME
\sysman\emd\targets.xml
file.
If an optional configuration assistant fails, and it does not have any dependencies, run the remaining configuration assistants. Uncheck the cancelled optional configuration assistant, highlight and check the next listed configuration assistant, and click Retry.
If configuration assistant failure occurs when you are running configuration assistant execution commands from Oracle Universal Installer or on the command line, then rerun the configuration assistant execution command again.
You can use the generated script file named configToolCommands
located in the ORACLE_HOME
\cfgtoollogs
directory to execute the failed configuration assistant again. The configToolCommands
script is generated after you exit the installer. During silent or noninteractive installation, the configToolCommands
script is generated immediately after configuration assistant failure.
You must perform the following tasks before using the generated script:
Open the autogenerated %ORACLE_HOME%
\cfgtoollogs\configToolCommands
script in an editor. Search and replace all occurrences of *Protected value, not to be logged*
with the passwords you specified during the installation. If it is a common password, then it becomes simpler and you just have to replace all occurrences of the preceding string with that common password.
Set the ORACLE_HOME environment variable to the ORACLE_HOME
path.
Run the %ORACLE_HOME
%\cfgtoollogs\configToolCommands
script to rerun all the failed and skipped configuration assistants.
Set the ORACLE_HOME environment variable to the ORACLE_HOME
path.
Note: If the description of a configuration assistant includes an "Initial Tasks" section, you must perform these tasks before running the configuration assistant. |
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 Collaboration Suite. The following tasks describe the recovery procedure:
Deinstall the failed installation using the procedure described in Appendix J.
Correct the cause of the Irrecoverable error.
Reinstall Oracle Collaboration Suite.
If the error reoccurs, then you must remove all Oracle installations from your computer.
This section explains some errors that you may encounter after installation.
If a user logs in to Oracle Collaboration Suite and sees a generic OracleAS Portal page instead of the Oracle Collaboration Suite Home page, do the following:
Ensure that the user is a member of the Oracle Collaboration Suite Users group, as follows:
Log in to Oracle Delegated Administration Services as orcladmin
at the following URL:
http://host_name:port_number/oiddas/
Note: In a typical installation, Oracle Delegated Administration Services is located where the Infrastructure is installed. |
Click the Directory tab.
Search for the user by user ID (orclguest
, for example).
Select the user from the search results, and click Edit.
Scroll down to the Public Groups Assignment section, and ensure that the user is a member of the Oracle Collaboration Suite Users group.
If the user is not a member, select the Oracle Collaboration Suite Users box, and click Apply.
Log out of Oracle Delegated Administration Services.
Ensure that the Oracle Collaboration Suite Users group is the user's default group, as follows:
Log in to OracleAS Portal as the user in question. For example, go to http://
host_name
:
port_number
/
, click End User Login, and log in as orclguest
.
If the Oracle Collaboration Suite Home page appears, the user is now correctly provisioned and the rest of this procedure is unnecessary.
If the OracleAS Portal Welcome page appears, click Account Info.
On the Account Info page, ensure that the user's default group is set to OCS_PORTAL_USERS
.
If it is not, manually enter OCS_PORTAL_USERS
for the user's default group, and click Apply.
Ensure that the user's Default Home Page is blank.
Click the Home global button. You should see the Oracle Collaboration Suite Home page. If not, proceed to Step 3.
If the Oracle Collaboration Suite Home page still does not appear, do the following:
Log in to OracleAS Portal as the user in question. For example, go to http://
host_name
:
port_number
/
, click End User Login, and log in as orclguest
.
When the OracleAS Portal Welcome page appears, click Account Info.
On the Account Info page, ensure that the user's default group is set to OCS_PORTAL_USERS
.
If it is not, manually enter OCS_PORTAL_USERS
for the user's default group, and click Apply.
Click the Browse Pages icon next to the Default Home Page field.
Locate the OCS_V2_PAGE_GROUP
page group, and click to expand it.
Locate the Oracle Collaboration Suite Home page, and click Return Object.
Click Apply.
Click the Home global button and the correct home page should appear.
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.
If this appendix does not solve the problem you encountered, try these other sources:
Oracle Collaboration Suite Release Notes, available on the Oracle Technology Network at
OracleMetaLink at
If you have a support contract with Oracle, then the steps to download a patch from the OracleMetaLink site are:
login to OracleMetaLink at
Click Patches & Updates on the left side of the page.
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 that you need to download, then select Product or Family in the Simple Search list.
Select the appropriate operating system from the Platform or Language list.
Click Go.
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.