Skip to main content

Determining the Patch Set Update(PSU) Version

By Unknown
When checking for the latest PSU you might want to know what the current PSU is. I also keep a list of PSU updates and latest CPU updates on the Critical Patch Updates page. If the below returns nothing you are on the base level, e.g. 11.2.4.0

opatch lsinventory -bugs_fixed | egrep -i 'PSU|DATABASE PATCH SET UPDATE' 

10248523 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.1
11724916 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.2 (INCLUDES CPUAPR2011)
12419331 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.3 (INCLUDES CPUJUL2011)
12827726 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.4 (INCLUDES CPUOCT2011)
13343424 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PATCH SET UPDATE 11.2.0.2.5 (INCLUDES CPUJAN2012)
13696224 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PATCH SET UPDATE 11.2.0.2.6 (INCLUDES CPUAPR2012)

Reference:

Labels:

Comments

Post a Comment

Popular posts from this blog

Cancel or abort adop session

By Unknown
ADOP is in my opinion still pretty half baked. This is a critical tool that just isn't as intuitive as the old adpatch was. However we move with the times and get the hang of the new way of doing things. Along the way you might want to abort or cancel a patching cycling. With the two file systems and db editioning this can be a bit more to manage. I have learnt the hard way so you need to use the full cleanup after aborting a session. adop phase=abort adop phase=cleanup cleanup_mode=full
Post a Comment
Read more

Creating new WLS domain ends with exit code 255

By Unknown
Cloning the instance I ran into this weird error. Was not sure what to do but after learning my lesson I dug through the error logs after seeing this in the adcfgclone log file. START: Creating new WLS domain. Running /u03/APPLYES/YES/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /u03/APPLYES/YES/fs2/EBSapps/comn/util/jdk64 -al /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /u03/APPLYES/YES/fs2/FMW_Home/user_projects/domains/EBS_domain_YES -tmw /u03/APPLYES/YES/fs2/FMW_Home -mpl /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/tempinfo.txt Script Executed in 1903 milliseconds, returning status 255 ERROR: Script failed, exit code 255 Dig a bit deeper into the log files cd /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply cat CLONE2016-01-10_04-37-...
Post a Comment
Read more

Launching a Concurrent with Form Personalization on EBS 11i

By Unknown
There are two methods when it comes to running a concurrent from a Form Personalization in Oracle. The thing you need to do in either case is create a menu option for the form in question. This is generally done on a WHEN-NEW-FORM-INSTANCE Trigger Event. If you already have an event like this then you can add it there. I personally like to group my customizations together so there is not much overlap. Whichever catches your fancy will work. Setup the menu with the name: You now have a menu item for the launching of the concurrent program. This is where the two methods separate and you may choose which ever is more appropriate to you. Launch FNDRSRUN (Submit Request) This will use the zoom feature of Oracle Form Personalization to open the Submit Request Form, and pass the parameters to it. This involves personalization in two forms. The sending form needs to call the Form Function and pass the parameters and the Submit Request form needs to receive and process those parameters....
2 comments
Read more