Gathering version and patch details for issues in OIM 11g:
These steps assume Linux variables and pathing. For Windows environments, adjust your steps accordingly. For OIM 11g clustered domains which are *not* using shared storage, these commands must be run on each cluster nodes installation location.
- For the WLS home, set the domain environment variables using the script in the $DOMAIN_HOME/bin directory, then check the list of applied patches using the BSU utility, printing the results to a text file for readability:
[oracle@machine1 bin] . setDomainEnv.sh
[oracle@machine1 oim_domain]$ cd $MW_HOME/utils/bsu
[oracle@machine1 bsu]$ ./bsu.sh -view -status=applied -prod_dir=$WL_HOME > WLSpatches.txt - From the same terminal window, set the ORACLE_HOME to use the
oracle_common home and set the path to include the path to OPatch, then
run the opatch lsinventory -detail command, printing the output to a text file for readability:
[oracle@machine1 bsu]$ export ORACLE_HOME=$COMMON_COMPONENTS_HOME
[oracle@machine1 bsu]$ export PATH=$PATH:$ORACLE_HOME/OPatch
[oracle@machine1 bsu]$ opatch lsinventory -detail > ASdetail.txt - From the same terminal window, perform similar steps for the SOA
home, setting the ORACLE_HOME to use the soa home and running the opatch lsinventory -all command, printing the output to a text file for readability:
[oracle@machine1 bsu]$ export ORACLE_HOME=$SOA_ORACLE_HOME
[oracle@machine1 bsu]$ opatch lsinventory -all > SOAall.txt - From the same terminal window, use similar steps for the OIM home:
[oracle@machine1 bsu]$ export ORACLE_HOME=$OIM_ORACLE_HOME
[oracle@machine1 bsu]$ opatch lsinventory > OIMinv.txt - Verify the files from steps 1 - 4 contain the component version and patch details, then copy the files for upload to Oracle Support.
- Save these files to a location of your choice and be sure to keep the current version of these files available for future uploads to Oracle Support.