Applying the GI PSU 2 on a vanilla database is fairly easy. However, patching a standalone database in an Oracle Restart and ASM configuration, which uses Role Separation, and running OPatch in auto mode is a little more challenging. At some point the OPatch auto mode will be clear sailing, but given this configuration there were bumps in the road.
The notes provided in the following link may save you from a sleepless night if your database does not come up after applying the patch.
Good luck, and let me know if you have comments.
GI PSU 2 Apply
The notes provided in the following link may save you from a sleepless night if your database does not come up after applying the patch.
Good luck, and let me know if you have comments.
GI PSU 2 Apply
Thanks for sharing. I think some part is missing on your GIpsuApply.pdf at page 5 "Run the same OPatch command but this time ??????" Did you patched GRID_HOME and DB_HOME separately? I was trying to apply this on DB_HOME and it still pointing to GRID_HOME after changing the env variables.
ReplyDeleteSorry about that.
ReplyDeleteThere are two homes and two software owners following the 'role separation' approach. These accounts are typically the oracle and the grid accounts.
The home, and the account should be set to 'oracle' for applying the database patch.
To insure that you have the correct environment set do a "optach lsinventory" once for the grid user and once logged in as the oracle user. The output should show differences for...
Oracle Home
Lsinventory Output file location
---FOR THE ORACLE ACCOUNT -----------------------------------
Installed Top-level Products (1):
Oracle Database 11g 11.2.0.3.0
There are 1 products installed in this Oracle Home.
-----FOR THE GRID ACCOUNT --------------------------
Installed Top-level Products (1):
Oracle Grid Infrastructure 11.2.0.3.0
There are 1 products installed in this Oracle Home.