There is an easier way to be informed of new patches - Just register your OTN account to be informed of security bulletins and alerts:
You will get an email alert when new patches and upgrades are available and there will be links to drill down and read the details.
That is the easy part.
Now, if you want to decide if you actually need to install the patch that will require research and discussion within your company. I doubt there is any quick way to assess if you need a patch without carefully looking at the list of fixes, risk matrix and your own setup.
There are several ways to handle patches - some patch religiously, some apply only the patchsets at semi-regular intervals, some never patch until they encounter a bug that needs a specific bugfix. You decide which method suits your organization's comfort level.
I have lots of email alerts in my mailbox all mixed-up because I have lots of membership to different orq. Sometimes I delete all without reading. I can not segregate which one is for oracle patches now.
I think it would be easier if I just go to the MOSC. So where is it located in the MOSC? The one that is emailed to the OTN account?
How do I get into the MOSC if my boss give me only our SCI Nos. <removed by moderator>
You SCI numbers are private to your company and should not be published on a public forum.
I've edited them out of your post.
Be very careful not to post private information on public forums as there will not always be a moderator around to clean up for you. It could lose you your job.
Which of the following to I need to apply to be able to pass the auditor/isso requirement which is "to be in the latest patch update".
Do I need to apply all PSU, SPU, and GI PSU?
I got this list of latest patch groups:
Description PSU SPU(CPU) GI PSU Bundle Patch(Windows64bit) Bundle Patch(Windows32bit) OCT2013 16902043 (22.214.171.124.8) 17082364 17272731 (126.96.36.199.8) 17363850 17363844
17082364 is the CPU_OCT_2013 patch - if you install 17272731 for GRID Infrastructure the patch includes the RDBMS patch and the CPU_OCT_2013 as well.
Following the readme (Apply GI first than DB or use auto option to patch both). We have installed 17272731 already - the only thing was that ASM can't start by internal error.
(Oracle Support analyze the internal error but think it was the sudo su command)
This was solved by full relink the GI HOME - after them all things was fine. ;-)
You are on AIX maybe investigate into:
17403540 AIX bundel patch#2, too - small RDBMS patch but usefull for us.