search

biemond / biemond-orawls

Puppet 3/4 module for WebLogic provisioning module ( Linux & Solaris )
Apache License 2.0
63 stars 104 forks source link

Patching OPatch - question #538

Open standagh opened 6 years ago

standagh commented 6 years ago

If this is a duplicate please ignore.

There is following line related to insetall WLS PSU 12.2.1.3.180717 Patch 27912627: Before Applying this PSU, please apply Opatch 13.9.4 Patch 28186730

But installation instructions for 28186730 are: Install the software via: java -jar /6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME

So - 2 differencis to regular patches installed via opatch apply:

Is it possible to apply this patch using puppet orawls module? I didn't found any option how to do it so far.

biemond commented 6 years ago

Hi,

Ok it looks like oradb and I need to add opatch upgrade just like in db where this is very common. https://github.com/biemond/biemond-oradb/blob/puppet4_3_data/manifests/opatchupgrade.pp

Thanks

aukebergsma commented 6 years ago

We had the same issue. Based on Edwin's tip, Maarten and I have endeavoured to fix this. The result is available in https://github.com/aukebergsma/biemond-orawls/tree/patch-1. For example, you can call this as:

orawls::opatchupgrade {'28186730':
  oracle_product_home_dir => $fwm_directory,
  patch_id                => 6880880,
  patch_file              => 'p28186730_139400_Generic.zip',
  opversion               => '13.9.4.0.0',
  os_user                 => 'oracle',
  os_group                => 'oinstall',
  require                 => Class['orawls::weblogic']
}

Since we are no fluent git / github users, we are no sure if we can create a (correct) pull request (we now have a branch with the commits in a reversed order compared to Edwin's branch). Maybe for the process it might also be better if you try it first.

biemond commented 6 years ago

nice, please make a PR, I can always fix it and improve it

aukebergsma commented 6 years ago

Ok, we created a PR.

userMar2017 commented 5 years ago

Hi Ed and folks,

Is this integrated into orawls already ? I am encountering the same and would like to use the fix instead of writing a script for it.

userMar2017 commented 5 years ago

ok, I was able to figure it out....I used the following form

Thanks everyone !

orawls::opatchupgrade {'28186730': .. ..