test

Sun Connection 1.1 Release Notes

Upgrade Issues

This section describes issues that you might encounter while upgrading your Sun Connection software.

Cannot Use the Upgrade Scripts to Upgrade From Version 1.1 to 1.1.1

Description:

The Sun Connection upgrade scripts fail when upgrading from version 1.1 to version 1.1.1.

Workaround:

Use one of the following agent upgrade methods to upgrade from 1.1 to 1.1.1:

  • If you have a Solaris 10 agent, use the special upgrade mode in the console.

    -update_director_mode

  • If you have a Solaris 8 or 9, or Linux agents, contact Sun Support to get the upgrade scripts and procedures to launch a job for upgrade.

Cannot Use the Upgrade Scripts to Upgrade Solaris 10 Agents

Description:

The Sun Connection upgrade scripts fail when upgrading Solaris 10 from version 1.0.x to version 1.1.x.

Note –

The upgrade script does work when upgrading from version 1.1 to 1.1.1.

Workaround:

Contact Sun Support to get the upgrade scripts and procedures to launch a job for upgrade.

Upgrading from Sun Connection 1.0.x to 1.1.x Fails Without Manual Intervention (CR 6531803)

Description:

Upgrading from Sun Connection version 1.0.3 to version 1.1 or 1.1.1 fails and results in a cpio error in the /logs directory.

The failure is caused by a change in the /logs directory between the two releases.

Workaround:

  1. Contact Sun Support to get the upgrade scripts and procedures to launch a job for upgrade.

  2. Rename the server/logs/ directory to server/logs.old

  3. Use the upgrade scripts and procedures to launch the upgrade job.

If you receive the error message, rename the directory and then re-run the job.

Missing Credentials After an Upgrade From Sun Aduva OnStage 439 to Sun Connection

Description:

The credentials you entered to access software directly from a vendor, such as for the Solaris patches, are not saved as part of the backup process.

Workaround:

Add these credentials after the upgrade is complete by using the Sun Connection Authentication window.

Missing Cached Public Components After an Upgrade From Sun Aduva OnStage 439 to Sun Connection

Description:

The cached public components that were downloaded with Sun Aduva OnStage are not saved as part of the backup process.

Workaround:

Download the cached public components after the upgrade is complete.

Attempts to Install Solaris Packages Fail After an Upgrade From Sun Aduva OnStage 439 to Sun Connection (CR 6464386)

Description:

When attempting to install Solaris packages, the package install fails with an error regarding the parameter CLIENT_BASEDIR.

Workaround:

    Do the following:

  1. Copy the Sun Connection agent tar ball to the host.

  2. Remove the ADVagent package.

  3. Unpack the Sun Connection agent tar ball.

  4. Install the Sun Connection agent.

Download the cached public components after the upgrade is complete.

Job Logs not Available After Upgrade From Sun Aduva OnStage 439 to Sun Connection (CR 6454745)

Description:

After the upgrade, job logs from the previous release are no longer available

Workaround:

Backup the logs before the upgrade and restore them after the upgrade.

Before the upgrade, backup the OnStage agent log directory content located at: /opt/local/aduva/director_agent/log .

After the upgrade, restore the saved data into the /opt/local/uce/agent/log directory, which is Sun Connection's agent log directory.