Last week I had to apply the patch 11.2.0.2 on a development team. When I entered and searched metalink the patch applied to my OS (Solaris SPARC) I was struck by the size of the patch. The last patches installed memory that will not weigh much more than 1Gb. 11.2.0.2 patch on the platform weighs 5.1Gb needed!, And AIX over 6Gb. Recently when I read the documentation I understood why. The issue is that Oracle changed the policy of patching from 11.2.0.2. Now there are more incremental, but also total and contain all the bundle, ie server, client, gateway, grid, etc.
9i remember that everything came together, if a customer wanted to install only need to download 3 files that contained everything, which was cumbersome. Facilities in their independence 10g client, server, grid, etc. Now it seems that you have to download everything again and then choose to install what we need.
is mandatory to use a separate home for the installation, the total can not be patched on the current home. In my case this new requirement does not bother me because I always consider as a good practice to install patches on a copy in a new home, to minimize risks if the patch fails partway through the installation and requires backtracking support binaries above. If you are very short of space, is a bit complicated to create a separate home so in that case you must download the bases, support binaries, remove them and install the new home.
Installation on Solaris SPARC had no setbacks. I had to upgrader an Oracle 11g R1 (11.1.0.7) and Oracle 11g R2 (11.2.0.1). Both updates were made perfectly and without any mishap.
0 comments:
Post a Comment