Before you try any of the troubleshooting steps in this appendix, do the following:
Check Chapter 2, "Oracle Database Preinstallation 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:
If you encounter an error during installation:
Do not exit Oracle Universal Installer.
If you clicked Next after you entered incorrect information about one of the installation windows, click Back to return to the window and correct the information.
If you encounter an error while Oracle Universal Installer is copying or linking files, see "Reviewing the Log of an Installation Session" for interactive installations or "Silent or Noninteractive Installation Response File Error Handling" for more information.
If you encounter an error while a configuration assistant is running, see the "Troubleshooting Configuration Assistants" section.
If you cannot resolve the problem, remove the failed installation by following the steps listed in the "Cleaning Up After a Failed Installation" section.
During an installation, Oracle Universal Installer records all the actions that it performs in a log file. If you encounter problems during the installation, review the log file for information about possible causes of the problem.
If you run Oracle Universal Installer during the time that Windows Scheduler jobs are running, then you may encounter unexplained installation problems if your Windows Scheduler job is performing cleanup, and temporary files are deleted before the installation is finished. Oracle recommends that you complete installation before the Windows Scheduler jobs are run, or disable Windows Scheduler jobs that perform cleanup of temporary files until after the installation is completed.
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.
By default, the log files are located in the following directory:
For example, if an interactive installation occurred at 9:00:56 a.m. on October 14, 2005, the log file would be named:
To determine whether a silent or noninteractive installation succeeds or fails, check the
.log file, located in
If necessary, see the previous section for information about determining the location of the
A silent or noninteractive 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
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 silent or noninteractive 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.
See Also:"Reviewing the Log of an Installation Session" for information about interactive installation log files
If you change the host name for ASM, then the Oracle CSS daemon will not start. In order to counter this problem, use the following steps:
delete to deconfigure CSS. This will remove any configuration related files on the system that referenced the old host name.
localconfig add to reconfigure CSS using the new host name.
C:\> ORACLE_BASE\ORACLE_HOME\bin\localconfig [add] [delete] [reset destination_Oracle_home] [-silent] [-paramfile Complete_path_of_file_specifying_parameter_values]
This section lists some of the errors that may occur while using Oracle Configuration Manager and provides tips to troubleshoot these errors.
Insufficient Privileges While Running installCCRSQL collectconfig
When you run the
installCCRSQL.exe script, it creates the
ORACLE_OCM user and sets up a job to collect database configuration information. The
ORACLE_OCM user requires
EXECUTE privileges on
DBMS_SCHEDULER for database versions 10g or later, and on the
DBMS_JOB for pre-10g databases. If these privileges are granted to
ORACLE_OCM user inherits these privileges, otherwise these privileges are explicitly granted when the
installCCRSQL.exe script is executed. If the inherited privileges are revoked, the following errors indicating the lack of privileges will be logged in the
ORA-12012: error on auto execute of job 52 ORA-04068: existing state of packages has been discarded ORA-04063: package body "ORACLE_OCM.package_name" has errors ORA-06508: PL/SQL: could not find program unit being called
To resolve these errors, you must grant the missing
EXECUTE privilege to the
For database versions 10g and later, grant
EXECUTE privileges on the
DBMS_SCHEDULER packages to the
ORACLE_OCM user by entering the following
SQL> grant execute on UTL_FILE to oracle_ocm; SQL> grant execute on DBMS_SCHEDULER to oracle_ocm; SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile; SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
For pre-10g databases, grant
EXECUTE privileges on the
DBMS_JOB package to the
ORACLE_OCM user by entering the following
SQL> grant execute on UTL_FILE to oracle_ocm; SQL> grant execute on DBMS_JOB to oracle_ocm; SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile; SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
There may be cases when the
ORACLE_OCM user needs to be granted the required privileges during installation. While granting the privileges, the following error may occur in the
ORA-04021: timeout occurred while waiting to lock object SYS.<package like UTL_FILE>
This error may occur if another procedure is using the package for which the privileges are being granted. To resolve this error, retry the install when the package is not being used. This error may occur while granting privileges on
ORA-01925 Error While Running installCCRSQL
This error may occur if the value of the
MAX_ENABLED_ROLES initialization parameter has been exceeded. To resolve this error, you must increase the value of the
MAX_ENABLED_ROLES parameter and restart the database as follows:
ora file where
sid is the database system identifier and increase the value of
MAX_ENABLED_ROLES . If a server parameter (spfile) has been used, alter the
MAX_ENABLED_ROLES parameter by using the following SQL*PLus command:
SQL>alter system set
Restart the database.
Once the database has been restarted, re-run the
Incorrectly configured host names are displayed on My Oracle Support (formerly OracleMetaLink) with only the short names.
To ensure that host names are displayed with their fully qualified names on My Oracle Support (formerly OracleMetaLink), the
windir\system32\drivers\etc\hosts file must contain an entry that includes both the host name and the domain in the following format:
IP-Address Full-HostName Short-HostName
10.10.10.10 myhost.mydomain myhost
hosts file has not been correctly configured, only the short name is displayed on My Oracle Support (formerly OracleMetaLink).
Oracle Configuration Manager Synchronization Messages: Oracle Configuration Manager does not allow you to run multiple commands simultaneously. If you attempt to do so, the following messages may be displayed:
Message: Another operation is in progress. Please wait...
Description: There are several Oracle Configuration Manager commands that cannot run concurrently. If you try to run one of these commands while another command is in progress, the second command will not be executed until the first command is completed. A message indicating that another command is in progress is displayed. The second command will automatically be run when the first command is completed.
Action: Initially, take no action, the second command will be executed when the first command is completed. But if the command execution takes too long, a timeout will occur. If a timeout occurs, ensure there is no Oracle Configuration Manager activity by executing
stop command. Delete the
lock file and restart the Scheduler by running the
start command. If you are running the command in Disconnected mode, ensure that no collection or update is taking place and then delete the
Message: Operation blocked, waiting...
Description: You cannot run the
emCCR update_components command if any other
emCCR command is running. If you try to run the command, it will be blocked. You also cannot run any
emCCR command while
update_components is running as all other commands will be blocked.
configCCR and most of the
Action: Initially, take no action, the command will get executed when the current command is completed. If a timeout occurs, ensure that there is no Oracle Configuration Manager activity by executing
stop. Delete the
update* files, and restart Oracle Configuration Manager by running
start. If running the command in Disconnected mode, ensure no collection or update is taking place and delete the
op* and the
Message: The Scheduler is down for upgrade.
Description: While upgrading Oracle Configuration Manager, you cannot run any of the
Action: Retry the commands later.
Review the installation log files listed in the "Reviewing the Log of an Installation Session" section.
Review the specific configuration assistant log file located in the
cfgtoollogs directory. Try to fix the issue that caused the error.
Note:Make sure that there is no space in the path.
If you see the Fatal Error. Reinstall message, look for the cause of the problem by reviewing the log files. See "Fatal Errors" for more information.
Oracle configuration assistant failures are noted at the bottom of the installation window. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the
The execution status codes are listed in the following table:
|Configuration assistant succeeded||0|
|Configuration assistant failed||1|
|Configuration assistant canceled||-1|
If you receive a fatal error while a configuration assistant is running:
Remove the failed installation as described in the "Cleaning Up After a Failed Installation" section.
Correct the cause of the fatal error.
Reinstall the Oracle software.
If you face any of the following situations for Oracle home, then run the
opatch lsinventory -detail command to list the contents of the inventory and see section "Recovering from inventory corruption" in the Oracle Universal Installer and OPatch User's Guide for information on fixing the issue.
Oracle home is cloned without completing the inventory steps.
There is bad inventory.
Inventory is not available but it is created when the Oracle Enterprise Manager Agent is installed in a separate Oracle home.
If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory. Follow the instructions in "Removing Oracle Database Software" to run Oracle Universal Installer to deinstall Oracle Database, manually remove the Oracle directory, and remove Oracle from the Registry Editor keys. Afterward, reinstall the software.
In "Configuring Oracle HTTP Server in a New Installation" , you added an alias entry that points to the file system path where you copied the images directory. If images in Oracle Application Express do not display correctly, you may have more than one definition of the
/i/ alias. To address this issue:
If possible, rename the first instance of
/i/ to a different alias name.
Alternatively, copy the images from the
ORACLE_BASE\ORACLE_HOME\apex\images directory to the directory defined by the first
If users are accessing Oracle Application Express through a Virtual Host, online Help will not work. Consider the following example:
The host name of the Oracle HTTP Server where the Oracle Application Express DAD resides is
internal.server.com and the port is
Users access Oracle Application Express through a Virtual Host. In their Web browsers, users see
external.server.com and port
In this example, Oracle Application Express online Help will not work if the users cannot access
internal.server.com. To resolve this issue, add the following lines to the Oracle Application Express Database Access Descriptor (DAD) to override the CGI environment variables
PlsqlCGIEnvironmentList SERVER_NAME=external.server.com PlsqlCGIEnvironmentList SERVER_PORT=80