4 Troubleshooting Your Upgrade
- Troubleshooting an Upgrade
Understanding the errors that you may encounter while running the Upgrade Assistant will help you to effectively troubleshoot them. - Reviewing Log Files
Do not delete the log files. They help diagnose and correct the problem while you run the Upgrade Assistant. - Investigating Examination Failures
Identify and troubleshoot failures that occur during the Examination phase of the upgrade. - Investigating Upgrade Failures
Identify and troubleshoot failures that occur during the upgrade. - Resolving Common Upgrade Assistant Errors
Attempt to resolve common Upgrade Assistant errors before contacting Oracle Support. - Attempting to Upgrade an Unsupported Domain
Do not attempt to upgrade the schemas or domain configurations in an unsupported domain. - Restarting the Upgrade Assistant After a Failure
You must resolve errors before you restart the Upgrade Assistant.
Troubleshooting an Upgrade
Understanding the errors that you may encounter while running the Upgrade Assistant will help you to effectively troubleshoot them.
Note:
Your course of action depends on the phase in which the error occurred.If errors occur while you are running the Upgrade Assistant, use the following steps to troubleshoot the problem:
Parent topic: Troubleshooting Your Upgrade
Reviewing Log Files
Do not delete the log files. They help diagnose and correct the problem while you run the Upgrade Assistant.
-logLevel
value on the command line. The default value is -logLevel NOTIFICATION
. You can alter the location of your log files using the -logDir
parameter. You can obtain more detailed logging information by running the Upgrade Assistant with -logLevel TRACE
. However, this may cause the log file to become very large.
Note:
TRACE
messages are not included in the Upgrade Assistant Log File Viewer. To view TRACE
messages, use another tool.
Tip:
To expedite the review process, search for the wordERROR
.
For more information about the error messages in your log files, see Resolving Common Upgrade Assistant Errors.
Log files are stored in the following default directory:
-
(UNIX)
ORACLE_HOME/oracle_common/upgrade/logs/uatimestamp.log
-
(Windows)
ORACLE_HOME\oracle_common\upgrade\logs\uatimestamp.log
where timestamp
states the actual date and time when the Upgrade Assistant was run.
Some components create a second log file called uatimestamp.out
, also in the same location.
For database schema upgrades of certain components, there can also be an output (.out
) file that contains the screen output of commands that were run in a shell process or as PL/SQL scripts. You can locate these output files in the same default directory.
If there are questions or issues about an upgrade failure that cannot be resolved with the information in this guide, it is important to retain the log files. If you submit a service request, you must upload the entire Upgrade Assistant .log
file and the .out
files (if available) along with the service request.
Parent topic: Troubleshooting Your Upgrade
Investigating Examination Failures
Identify and troubleshoot failures that occur during the Examination phase of the upgrade.
To determine the cause of an Examination failure:
To complete the upgrade, resolve the issues and then launch the Upgrade Assistant again, or, if possible, click Back to return to a previous screen and make the necessary changes.
Note:
The readiness check performs checks to a far greater level of detail than the Examination phase. If Examine fails, you can run the Upgrade Assistant with the-readiness
parameter and make sure that the report does not show any test failures.
Issues detected during the Examination phase can be resolved without restoring from backup (as is required to resolve errors encountered during the actual upgrade). However, if you attempt to resolve an Examination error in a way that changes the state of the system, you need to restore the entire system to the pre-upgrade state (before any upgrade operations were attempted).
Parent topic: Troubleshooting Your Upgrade
Investigating Upgrade Failures
Identify and troubleshoot failures that occur during the upgrade.
To determine the cause of an upgrade failure:
To complete the upgrade, restore the entire environment using your pre-upgrade backup to a point in time before any upgrade operations were attempted, resolve the issues, then launch the Upgrade Assistant again. You will have to start the upgrade process from the beginning to ensure a successful (complete) upgrade.
Note:
You should back up all databases withRMAN
and be able to do a point-in-time recovery from those backups. If the Fusion Middleware repository for your domains spans multiple Oracle Database servers, you must restore from each of those backups.
Parent topic: Troubleshooting Your Upgrade
Resolving Common Upgrade Assistant Errors
Attempt to resolve common Upgrade Assistant errors before contacting Oracle Support.
The following sections provide descriptions of the most common upgrade errors. For a complete list of Fusion Middleware errors, see Error Messages.
- Ensuring there is sufficient disk space
- Resolving Database Connection Problems When Upgrading Schemas
Parent topic: Troubleshooting Your Upgrade
Ensuring there is sufficient disk space
If an upgrade fails because the database server has run out of disk space, you must restore the database server environment from backups, add sufficient disk space or remove unwanted files (such as temp or trace files) from the database server, and then retry the upgrade.
Note:
Once a database schema upgrade has failed due to this class of error, you cannot simply add more disk space and retry the upgrade. The schemas have been left in an inconsistent state and may have been markedINVALID
. You cannot recover from this error without restoring the original database state from backups.
The following examples show some insufficient disk space errors that you may encounter:
ORA-01658: unable to create INITIAL extent for segment in tablespace
Cause: The existing schema tablespace does not have sufficient space to complete the upgrade.
Action: Make sure that the tablespace has sufficient room (space) for a successful upgrade. Oracle recommends that you add more data files to the existing database tablespaces, otherwise the upgrade will fail.
ORA-01114: IO error writing block to file block number
Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.
Action: Restore access to the device or remove unnecessary files to free up space.
ORA-09945: Unable to initialize the audit trail file
Cause: The system is unable to write header information to the file being used as the audit trail. The audit_trail_dest or audit trail destination is full for generation of audit file.
Action: Free up space and retry the operation.
Parent topic: Resolving Common Upgrade Assistant Errors
Resolving Database Connection Problems When Upgrading Schemas
If you have trouble connecting to a database when using the Upgrade Assistant to upgrade a component schema, try connecting to the database using another tool, such as SQL*Plus. This helps you troubleshoot the problem by verifying that the database is up and running and available on the network.
Parent topic: Resolving Common Upgrade Assistant Errors
Attempting to Upgrade an Unsupported Domain
Do not attempt to upgrade the schemas or domain configurations in an unsupported domain.
If you receive an error stating that the specified domain cannot be upgraded, you must first upgrade the domain to a supported version. Do not attempt to upgrade schemas or domain configurations in an unsupported domain.
Parent topic: Troubleshooting Your Upgrade
Restarting the Upgrade Assistant After a Failure
You must resolve errors before you restart the Upgrade Assistant.
If the Upgrade Assistant fails during the upgrade phase, or only partially upgrades your components, try to resolve the issues and then follow these steps:
Parent topic: Troubleshooting Your Upgrade