6 - 8 minutes readHow to Apply a Grid Infrastructure Patch Before Grid Infrastructure Configuration

Configuring Oracle HTTP Server to Use SSL in Fusion Middleware 11g (11.1.1.X) (Doc ID 1226933.1)

Implement Self Signed Certificate

Step 1: create a Password Protected Wallet(ewallet.p12 and cwallet.sso)

$MIDDLEWARE_HOME/oracle_common/bin/orapki wallet create -wallet <path> -auto_login

2. Create a Self-Signed Certificate:

This Wallet is ready to use with Application Server or Fusion Middleware for testing purposes.

How to Generate a Wallet Containing a Self Signed Certificate Using ORAPKI in Oracle Application Server and Fusion Middleware (Doc ID 560982.1)   How To Create a Java Keystore via Keytool in FMW 11g/12c (Doc ID 1230333.1) 1. Create a directory, for example: $MIDDLEWARE_HOME/keystores /u03/WLSPayroll/Oracle/Middleware/keystore 2 Run the following to set the environment on UNIX cd /u03/WLSPayroll/Oracle/Middleware/wlserver_10.3/server/bin . ./setWLSEnv.sh 3. Create a keystore and private key, by executing the following command: go to /u03/WLSPayroll/Oracle/Middleware/keystore keytool -genkey -alias server_cert -keyalg RSA -keysize 2048 -sigalg SHA256withRSA -dname “CN=fcisit-apps01.nic.in,OU=IT, O=FCI, L=DELHI, ST=DEL, C=IN” -keypass welcome123 -keystore keystore.jks -storepass welcome123 To view the contents of the keystore created, execute the following command: keytool -list -v -keystore eystore.jks -storepass welcome123 a) If you are happy using a self signed certificate then this keystore must be exported, then imported into the keystore again as a trusted cert before weblogic can use the keystore. This is done with these commands: keytool -export -alias server_cert -file root.cer -keystore /u03/WLSPayroll/Oracle/Middleware/keystore/keystore.jks -storepass welcome123 keytool -import -v -noprompt -trustcacerts -alias server_root_cert -file root.cer -keystore keystore.jks -storepass welcome123 Note: Import command alias should be different from export command alias. Otherwise the error occurs

12.1.0.1 only:

1: Do not apply any patches to 12.1.0.1 home before executing root script (root.sh or rootupgrade.sh), instead configure GI first. Once GI is up and running from 12.1.0.1 home, a patch can be applied.

OR

2. Install 12.1.0.1 with software only option on all nodes, apply a patch to 12.1.0.1 home with “opatch apply” command, and execute <GI_HOME>/crs/config/config.sh to configure/upgrade to 12.1.0.1. Reference Document:1354258.1

11.2.0.x or 12.1.0.2

Since “opatch auto” relies on running Oracle Clusterware to identify the configuration, it can not be used to apply a GI patch to the new GI home before root.sh or rootupgrade.sh is executed.

It’s recommended to apply latest GI PSU, refer to Document:756671.1 for the patch#.

The steps below describe how to apply 11.2.0.2.3 GI PSU (GI PSU 3) to a newly installed GI home prior to executing the root script but the procedure will be the same (with the exception of the release and patch numbers) for any 11.2 GI installation.

1. When prompted by the OUI to run root.sh (new install) or rootupgrade.sh (upgrade), DO NOT run the root.sh or rootupgrade.sh scripts but leave the installer GUI window open (and root scripts prompt)

2. Install the 11.2.0.2.3 GI PSU (12419353) to the newly installed (but unconfigured) 11.2.0.2 GI home as follows (DO NOT follow the readme, the instructions in the readme will cause the patch install to fail for an unconfigured GI home).

3. Install the latest version of OPatch 11.2 (available under Patch 6880880) into the GI home as described in Document:1339140.1 under “How do I install the latest OPatch release?”

4. Create an EMPTY directory to stage the GI PSU as the GI software owner (our example uses a directory named gipsu):

5. Extract the GI PSU into the empty stage directory as the GI software owner:

6. Apply patch to the newly installed 11.2.0.2 GI home as the GI software owner using OPatch apply:

Go to each of the subdirectory in the unzipped location, and execute “opatch apply|napply” command.

For example:

7. Repeat the above steps 3-6 on ALL cluster nodes

8. Once the 11.2.0.2.3 GI PSU has been applied to the newly installed GI home (on ALL nodes), you can now execute the root.sh or rootupgrade.sh script one node at a time (allowing the current node to complete prior to moving on to the next) as instructed in the OUI popup window.

9. Once the root script has completed successfully on all nodes, complete the upgrade/installation by clicking okay in the root script popup OUI window that was left open in step 1.

18.1 and above

1. Unzip Grid Infrastructure Gold Image to the Desired GI Home Location on the Local Node as the Grid user

2. Download and Install the latest OPatch Version (Patch 6880880) to the extracted GI Gold Image as the Grid user:

3. Install/Upgrade the 18c GI and apply the patch to the Gold Image at the same time by running the following as the Grid user:

For Windows,  applyRU option is not supported. Install/configure the base Goldimage Software first (without -applyRU), and then install the RU using standard opatch/opatchauto process.