Previous Contents Index Next |
Sun Java System Application Server 7 2004Q2 Troubleshooting Guide

> ## Chapter 9
> Upgrade Problems

> This chapter addresses problems that you may encounter while upgrading from one version of the Application Server to another.

> The following sections are contained in this chapter:

> - Upgrade Log
> - Package-based installation consistently fails.
> - User ID errors occur.
> - Errors occur during the backup.
> - Errors occur during reconfiguration.
> - Upgrade interrupted; server is in inconsistent state.
> - Doing a partial online upgrade of a cluster causes problems.

> Full instructions for upgrading can be found in the upgrading chapter of the Sun Java System Application Server 7, Standard Edition Installation Guide.

> ##

> Upgrade Log

> Upgrade events and errors are captured in the Application Server upgrade log file (upgrade.log) during the active upgrade process. For commonly-encountered errors, the most likely action needed is included in this file for your convenience.

> ##

> Package-based installation consistently fails.

> Examine the package installation logs to determine what is happening.

> ##

> User ID errors occur.

> Errors specific to the user ID (for tarball installations) usually have to do with permissions not being set correctly.

> ##### Solution

> Verify that your permissions for the installation directory and the backup directory are correct.

> ##

> Errors occur during the backup.

> The most likely error in this phase is related to permissions and space limitations.

> ##### Solution

> - Verify that your permissions for the directory specified are correct.
> - Resolve any space problems, then restart the upgrade program where it left off.

> ##

> Errors occur during reconfiguration.

> Problems in this phase are usually caused by a system crash or other interruption.

> ##### Solution

> After resolving any problems, restart the upgrade program where it left off.

> ##

> Upgrade interrupted; server is in inconsistent state.

> You can restart an upgrade process for any reason by removing the .audit_upgrade file in the directory where the setup script is located, then restarting the upgrade. However, until you have completed the upgrade, the server instance you are upgrading is in an inconsistent state, so it is important that you complete any upgrade you have started.

> Solution

> Complete the upgrade as quickly as possible to resolve the inconsistent state of the server.

> ##

> Doing a partial online upgrade of a cluster causes problems.

> You must upgrade all application server instances in a cluster together. Otherwise there is a risk of version mismatch caused by a session failing over from one instance to another where the instances have different versions of components running.

> Note | You cannot perform an online upgrade of a cluster if the upgrade involves a change to the application database schema or the HADB schema. This requires a full reinstall.

> ##### Solution

> Upgrade all instances in a cluster identically and in as short a time period as possible.

> Additional information on upgrading a cluster online is contained in the Sun Java System Application Server Administrator’s Guide.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.