Itemized Upgrade Issues

The Access Manager pre61to62upgrade script does not handle DB based logging correctly (5042233)

After the Access Manager upgrade process from version 6.1 to version 6.2 is finished, the upgrade log indicates that the DB based logging was not handled correctly.

Solution None. The Access Manager upgrade process from version 6.1 to version 6.2 does not support backing up of the DB log tables.

JSP compilation errors in Application Server after other components are upgraded to Java ES 5 Update 1 (6388329)

After upgrading any Java ES component to Java ES 5 Update 1 on a system running Release 3 or Release 4 Application Server (version 8.1), Application Server reports errors when you compile JSP pages.

Solution Upgrade Application Server to Java ES 5 Update 1, or apply the following patch to Application Server 8.1:

• On Solaris: 119166–17

• On Linux: 119168–17

On Solaris and Linux, Portal Server upgrade fails — cannot find /opt/SUNWappserver7/bin/asadmin (6313972)

Solution Refer to the following publication for the latest upgrade documentation regarding this issue:Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX

On Linux, Access Manager stops working after upgrading Application Server from Java ES 3 (6447925)

After upgrading Application Server from Java ES 3 on Linux, Access Manager stops working, and the server.log file indicates there was an error staring amlcontroller.

Solution Install sun-jss (JSS 4) and sun-jss3 manually:

1. Enter the command rpm -qa | grep sun-jss to check for the presence of sun-jss and sun-jss3.

2. If sun-jss is missing, manually add it:

   rpm -Uhv download-root/Linux_x86/Product/shared_components/Packages/sun-jss-4.2.4-4.i386.rpm

3. If sun-jss3 is missing, manually add it:

   rpm -Uhv download-root/Linux_x86/Product/shared_components/Packages/sun-jss3-3.1.11-1.i386.rpm

After upgrading Portal Server 7.1 in non-English locales, some portal applications do not function correctly (6569515)

When upgrading Portal Server 7.1 to Portal Server 7.1 Update 2 using patches, various portal-related web applications might not function correctly after running psupdate in a non-English locale.

Solution Rerun the psupdate script in the English locale:

1. Display and note down the current values of the $LC_ALL and $LANG shell variables:

   echo $LC_ALL echo $LANG

2. Set these variables to values for the English locale:

   export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8

3. Rerun the psupdate script:

   psupdate -a -i

4. Restore the values of $LC_ALL and $LANG:

   export LC_ALL=value-noted-in-step-1 export LANG=value-noted-in-step-1

Web Server and Portal Server have a special upgrade dependency (no bug number)

If Portal Server is deployed to a version of Web Server that you are upgrading to Java ES 5 Update 1, you must also upgrade Portal Server.

Because there is no way on Windows to upgrade Portal Server to Java ES 5 Update 1, you cannot also upgrade Portal Server when upgrading Web Server. Instead, you must migrate Portal Server to useApplication Server as its container before you attempt to upgrade Web Server.

Upgrading Portal Server 7.0 deployed to Web Server follows an unconventional sequence (6507069)

When upgrading Portal Server IFR (Interim Feature Release) 7.0 2005Q4 deployed in Web Server, you must upgrade components in a nonstandard sequence. See the Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX for more information.

Cannot create a new community after upgrading Portal Server 7.0 deployed to Web Server (6562802)

After upgrading Portal Server 7.0 and Web Server, attempts to create a new community in the Portal Server console generate an error.

Solution Follow these steps:

1. Log in to the Web Server administration console.

2. Click Configurations.

3. Select the configuration of the Portal Server instance that is running.

4. Click the Java tab.

5. View the Path seetings for Class Path Prefix.

6. Replace /opt/SUNWcacao/lib/cacao_cacao.jar with /usr/lib/cacao/lib/cacao_caca0.jar.

7. Save changes and exit the administration console.

Previously existing communities in Developer Sample are unusable after upgrading Portal Server 7.0 (6591992)

After upgrading Portal Server 7.0, communities that existed in the Developer Sample are not longer usable.

Solution Change the file /var/opt/SUNWportal/portals/portal1/desktop/default/SearchProvider/dbMenu.jsp as follows:

com.sun.portal.desktop.util.OrderedMap dbs =
  (com.sun.portal.desktop.util.OrderedMap)pageContext.findAttribute(
  "availableDatabases");

java.util.Map dbs = (java.util.Map)pageContext.findAttribute(
  "availableDatabases");

Monitoring Framework 1.0 with Instant Messaging needs upgrading if enabled (6515859)

If you enabled the monitoring functionality of Instant Messaging in Java ES 2005Q1 or 2005Q4, you will need to manually upgrade your properties file after you upgrade to Java ES 5 Update 1.

Solution After you have upgraded your Instant Messaging instance on a given host, edit the new mfwk.properties file to include the configuration parameters you wish to preserve from your old agent.properties file.

When upgrading Java ES 3 on Solaris 9 for x86, psupgrade fails if two versions of cacao are running (6550198)

When upgrading from Java ES 3 on Solaris 9 for x86, it is possible to have two versions of cacao running: the Java ES 3 version in support of Instant Messaging, and the Java ES 5 Update 1 version in support of upgraded components. In this situation, the psupgrade script used to upgrade Portal Server fails.

Solution Stop the Java ES 3 version of cacao before running the psupgrade script:

/opt/SUNWcacao/bin/cacaoadm stop

After running psupgrade, restart the Java ES 3 version of cacao:

/opt/SUNWcacao/bin/cacaoadm start

On Windows, Upgrade Using Configure Manually After Installation Option Creates Message Queue and High Availability but no Application Server Program Group (6500958)

Whenever a product component is installed or upgraded in Configure Manually After Installation mode, the product's shortcuts are created only after the product is configured manually.

Message Queue is not affected by this problem.

Solution None.