Friday, 8 January 2016

CRIMA1174E ERROR There is already a package installed

I saw this one today: -

CRIMA1154E ERROR: Error installing.

  CRIMA1174E ERROR:   There is already a package installed at "/opt/IBM/ODM851" in the "Operational Decision Manager" package group.  The installation directory for the new "Operational Decision Manager V8.5.1" package group must not be the same as a previously used installation directory.

  CRIMA1174E ERROR:   There is already a package installed at "/opt/IBM/ODM851" in the "Operational Decision Manager" package group.  The installation directory for the new "Operational Decision Manager V8.5.1" package group must not be the same as a previously used installation directory.


whilst trying to update IBM Operational Decision Manager Rules from 8.5.1.0 to 8.5.1.2 

This came as a surprise, as I'd run through this process on my own environment a number of times, and was re-using a response file that I'd prepared earlier.

I fired up the IBM Installation Manager command line tool: -

/opt/IBM/InstallationManager/eclipse/tools/imcl -c

=====> IBM Installation Manager

Select:
     1. Install - Install software packages
     2. Update - Find and install updates and fixes to installed software packages
     3. Modify - Change installed software packages
     4. Roll Back - Revert to an earlier version of installed software packages
     5. Uninstall - Remove installed software packages

Other Options:
     L. View Logs
     S. View Installation History
     V. View Installed Packages
        ------------------------
     P. Preferences
        ------------------------
     A. About IBM Installation Manager
        ------------------------
     X. Exit Installation Manager

——>

and chose V. View Installed Packages : -

=====> IBM Installation Manager> Installed Packages

View the following installed packages and fixes. Enter the number to see the details of a package group, package, or fix.
     1-. IBM WebSphere Application Server V8.5
       2. IBM WebSphere Application Server Network Deployment 8.5.5.0
     3-. Operational Decision Manager
       4. Decision Center 8.5.1000.20131113_1624
       5. Decision Server 8.5.1000.20131113_1713
       6. Profile templates for WebSphere Application Server 8.5.1.0

Other Options:
     O. OK

-----> [O] 


and realised where I was going wrong.

I had ODM installed in the package group Operational Decision Manager whereas my response file ( created on a different system ) had: -

  <profile id='Operational Decision Manager V8.5.1' installLocation='/opt/IBM/ODM851'>
    <data key='eclipseLocation' value='/opt/IBM/ODM851'/>
    <data key='user.import.profile' value='false'/>
    <data key='cic.selector.os' value='linux'/>
    <data key='cic.selector.arch' value='x86_64'/>
    <data key='cic.selector.ws' value='gtk'/>
    <data key='user.wodm_express' value='false'/>
    <data key='cic.selector.nl' value='en'/>
    <data key='user.wodm_was_home' value='/opt/IBM/WebSphere/AppServer'/>
  </profile>
  <install modify='false'>
    <offering profile='Operational Decision Manager V8.5.1' id='com.ibm.websphere.odm.dc.v85' version='8.5.1002.20150119-1502' features='jdk,base,Decision Center' installFixes='none'/>
    <offering profile='Operational Decision Manager V8.5.1' id='com.ibm.websphere.odm.ds.v85' version='8.5.1002.20150119-1502' features='com.ibm.wds.jdk.feature,base,com.ibm.wds.rules.studio.feature,com.ibm.wds.rules.res.feature' installFixes='none'/>
  </install>


Once I changed the response file, all went well.

PS It's also worth noting that it's important to change the references to the Package Group THROUGHOUT the response file, or one ends up with a NEW copy of ODM installed under, say, /opt/IBM/ODM851_1 :-)


No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...