Today I've installed patch 10.2.0.3 for Oracle on Windows on top of 10.2.0.2 database. I've noticed that my spool file generated by upgrade script was 33 MB big. It occurred that source of all oracle build-in packages were spooled. It was terrible experience to search for errors in this log file, as searching for 'ORA-' give hundreds results and I had to figure out if it is in comment of package, or real error.
Fortunately patch was installed successfully and everything runs fine.
Cheers, Paweł
Subscribe to:
Post Comments (Atom)
4 comments:
Hi,
I was also trying to install 10.2.0.3 on top of my 10.2.0.2 db.. just a question though... part of the instruction in the readme files talks about running rman> upgrade catalog did you run this ONLY to the catalog database or to all other databases that is being managed by rman and has meta data information on the catalog database? I hope I did not confuse you with my question :)
Looking forward to your reply.
Hi,
"upgrade catalog" is needed to be run only to catalog database.
I am trying to install the 10.2.0.3 patch on the Oracle Rel 2 DB ie 10.2.0.1 on XP SP 2. And I am having no luck at all. The moment I apply the patch the service just ceases to run. I cannot restart the service without getting a Error 1503 "Service timed out in a .. fashion"!
Does this mean that I have to upgrade to 10.2.0.2 before I can upgrade it to 10.2.0.3?
Hi,
I do not know the answer to your question. In my case I've applied 10.2.0.2, work with it for few months and then apply 10.2.0.3.
You can try to shutdown all services manually before applying patch.
And remember to run catupgrd.sql after installing patch.
You should contact Oracle support for help.
Post a Comment