Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2148274.1
Update Date:2016-07-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  2148274.1 :   MaxRep: Software Upgrade from 3.0.2 to 3.0.3 Fails with Message "Script failed with error"  


Related Items
  • Pillar Axiom Replication Engine (MaxRep)
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: MaxRep-2x
  •  




In this Document
Symptoms
Cause
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: To understand why 3.0.2 to 3.0.3 upgrade failed
Created from <SR 3-12751337331>

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Information in this document applies to any platform.

Symptoms

During a software upgrade from 3.0.2 to 3.0.3 using patch 3.0.3.GA.347.003 when the MaxRep engine has been previously installed to 3.0.3, then uninstalled and then re-installed, you may see a "Script failed with error" message when viewing the Task Details.

Cause

When using /root/Oracle-MaxRep_ReplicationEngine/uninstall.sh to uninstall the software, the utility does not remove 3 or 4 rpm packages and they must manually be removed in order for the 3.0.3.GA.347.003 patch to install without the script error. The issue is in the installer included with the 3.0.3.003 patch, and will fail if certain fixes have already been applied. The issue only happens if 3.0.3.003 patch was already installed on a system, even if uninstall is run afterwards.

Solution

The solution is to manually remove the installed rpm's.

Log into the MaxRep host console as root user, and confirm the following maxrep-*rpms are applied:

# rpm -qa | grep maxrep
maxrep-online-help-<version>-<release>.noarch
maxrep-mrcli-allclients-<version>-<release>.noarch
maxrep-oss-sources-<version>-<release>.noarch
maxrep-user-agents-<version>-<release>.noarch
#

The version and release #'s do not matter, if these RPM packages exist they need to be removed using the following commands:

# rpm -e maxrep-online-help-<version>-<release>.noarch
# rpm -e maxrep-mrcli-allclients-<version>-<release>.noarch
# rpm -e maxrep-oss-sources-<version>-<release>.noarch
# rpm -e maxrep-user-agents-<version>-<release>.noarch

Confirm no maxrep-*rpms exist:

# rpm -qa | grep maxrep
<no rpms should exist>

Log out of the MaxRep console.

From the Support UI, apply patch 3.0.3.GA.3547.003 again.

 

References

<BUG:23480403> - LOST POWER DURING UPGRADE CANNOT LOG INTO UI
<NOTE:1936501.2> - Information Center: Oracle FS1-2 Flash Storage System
<NOTE:166650.1> - Working Effectively With Oracle Support - Best Practices
<NOTE:2048914.1> - MaxRep: How to Unconfigure and Uninstall MaxRep Release 2 and 3
<NOTE:2003726.1> - MaxRep: How to Download Oracle MaxRep Release 3 and Higher
<NOTE:2146964.1> - MaxRep: Uninstall and Reinstall MaxRep 3.x Software

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback