collecting lsinventory information using opatch

Applies to: Identity Manager - Version 11.1.1.3.0 and later Details 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@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_IDM1 in case used default name) [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 > 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. OPTIONAL:  Gathering JDeveloper version, extension and patch details for issues with custom task flows, SOA Composites or WebService Connectors deployed to the OIM11g domain: These steps assume Linux variables and pathing.  For Windows environments, adjust your steps accordingly. Open JDeveloper.  From the top menu bar, select Help > About. This will open the About JDeveloper window.  Click to activate the Export drop down button near the top right of the page and select Save to File.  Browse to your desired location for this export and provide a name for the file using, for example:  JDevExport.txt.  Do not close the About JDeveloper window yet. From the About JDeveloper window, select the Properties subtab and scroll down to view the value of the java.home property.  You'll use this value in the next steps.   Close the About JDeveloper window and exit JDeveloper. Open a new terminal window which does not have the environment variables from the section above.  Set the environment variable ORACLE_HOME to your JDeveloper home and include the path to JDevelopers Opatch in the PATH variable.  For example, if JDeveloper is installed in a Middleware Home at /opt/oracle/JDevMW: [oracle@machine1 ~]$ export ORACLE_HOME=/opt/oracle/JDevMW/jdeveloper [oracle@machine1 ~]$ export PATH=$PATH:$ORACLE_HOME/OPatch From the same terminal window, you'll use the value you found for the java.home property in step 4 to determine the -jdk and -jre parameters, then run the opatch lsinventory command, printing the output to a text file for readability.  For example, if your java.home property value was /usr/java/jdk1.6.0_43/jre: [oracle@machine1 ~]$ opatch lsinventory -jdk /usr/java/jdk1.6.0_43 -jre /usr/java/jdk1.6.0_43/jre > JDevInv.txt Verify the files from steps 3 and 7 contain the text output and JDeveloper 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.