Oracle Patching – PSU or CPU ?
Any clue don’t use PSU (Patch Set Updates) ?
As described in Oracle Metalink Note 854428.1 switch back to CPU “…would require significant effort, and so is not advised”.
Please comment.
Any clue don’t use PSU (Patch Set Updates) ?
As described in Oracle Metalink Note 854428.1 switch back to CPU “…would require significant effort, and so is not advised”.
Please comment.
During the daily database check i found error ORA-0600 [17059] in the alert log of the repository database (Release 10.2.0.3, Linux x86].
Error occured during weekend and a high amount of trace- and dump-files are generated and fill up the file system.
Investigation at Oracle Support show me that the Oracle Bug 5705795 (Doc ID 4167271) caused the problem.
I download Patch 5705795 for our linux system.
(You need Patch 5731535 if using windows).
Stopped agent, opmn and iasconsole, shutdown the repository database and applied the patch.
After restart all oracle processes and the repository database the error no longer occured in the alert log.
But this time i found another error in the log (ORA-07445 [lstclo()+45] [SIGSEGV] [Address not mapped to object].
In my case the error occured because i don’t shutdown ALL databases which shared the same ORACLE_HOME.
The second database was open and caused the problem.
After bouncing and restart this database the error was cleared.