Gathering version and patch details for issues in OIM:

These steps assume Linux variables and patching.
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@identity bin] ./setDomainEnv.sh
    [oracle@identity oim_domain]$ cd $WL_HOME
    [oracle@identity wlserver_10.3]$ cd ../utils/bsu
    [oracle@identity 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 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:
    [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 -detail > OIMinv.txt