Solaris

Just want to add this. At least this is how I understand it. I hope someone on this forum who actively works with C++ or C application development can validate or correct me.

It is a shared library patch for C++. If your application is dynamically linked against this shared library, you will only need to restart your application. In this case restarting your oracle DB or any other app that uses the shared library will make sure it will start using this new patched library or the next time you reboot, it will use the new library. Hence patch notes are missing any indication to reboot or apply in single user etc.

But if you are using an in house or custom app, which is statically linked, you may run into issues, if the patch deprecates any option that your custom app was using. In that case you may need to back out the patch or recompile against the patched library.

Having said, that, I would still go with some of the above suggestions on applying in single user :-), just to minimize any errors.

If you value your job in the slightest, you should test the patch on a test system first and not on critical production systems.

and back out plan should also be prepared. in case you will face problems on the production systems.

best is to do live upgrade if your system can meet the requirements for a new boot environment. else, do a full backup first of the system before implementing any change. these are the best way to go should you need to roll back the patch.

@frank_rizzo Thanks a lot for your comments.

@dude2cool These media servers are Oracle DB with RAC or Sun Cluster only, no in house app installed on these servers

Thanks a lot for your comments.

@fpmurphy Sure, I will test in our Dev first but my question was about installing this patch in normal mode or single mode.

Thanks a lot for your comments.

@tamitot we have a weekly backup for our systems so backup is not an issue

Thanks a lot for your comments.

I really appricate your help guys.