CPU patch July 2010 on Oracle 11.1.0.7 database

Question

Hi,
I want to install the July2010 CPU patch (9655014) on a 11.1.0.7 database which was initially created with version 11.1.0.6.
The README file of the patch states the following about recompiling views:
3.2.2.2 Recompiling Views in the Database
You may skip this section if you have recompiled views for this database during the installation of a previous CPU or if the database was created with Release 11.1.0.6 or later.
So I assumed that I do not need to recompile the views but a little further in the README file I read:
If you want to check whether view recompilation has already been performed for the database, execute the following statement.
SELECT * FROM registry$history where ID = '6452863';
If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows.
When I execute the select it returns no rows. So this is confusing. Should I perform a view recompilation or not?
And when I execute recompile_precheck_jan2008cpu.sql (strange name for a July 2010 CPU) it says:
SQL> @recompile_precheck_jan2008cpu.sql
Running precheck.sql...
Number of views to be recompiled :1969
Number of objects to be recompiled :4019
Please follow the README.txt instructions for running viewrecomp.sql
PL/SQL procedure successfully completed.
thanks in advance.
regards,
Ivan

Answer 1

Short answer: you dont need to run view_recompile_jan2008cpu.sql
Long answer:
>
SELECT * FROM registry$history where ID = '6452863';
If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows.
When I execute the select it returns no rows. So this is confusing. Should I perform a view recompilation or not?
>
You will only get an entry in registry$history if you had a database that you had actually run the view_recompile_jan2008cpu.sql script which inserts a row into the table at the end of the script:
view_recompile_jan2008cpu.sql
Rem =======================================================================
Rem Insert values for patch into registry.
Rem =======================================================================
INSERT INTO registry$history (action_time, action, id, comments)
        values ( SYSTIMESTAMP, 'CPU', &&PATCH_NUMBER, '&&PATCH_DESC' );
COMMIT; In your case, you will get no entries in the table BUT you do not have to run the view recompilation so long as the database was created using a patched Oracle home of a release where Oracle says the view recompilation is not required.
>
SQL> @recompile_precheck_jan2008cpu.sql
Running precheck.sql...
Number of views to be recompiled :1969
>
This script has a very simple logic that just generates count of views and dependant objects that would need recompilation. The selection criteria does not include actually checking whether you actually need to apply the view recompilation script.
You can test this yourself:
Case#1: Run the recompile_precheck_jan2008cpu.sql on a database where you have applied the view recompilation script. You will find the count shows a non-zero value.
SQL> col action_time format a32
SQL> col version format a15
SQL> col version format a15
SQL> select action_time, version, id from registry$history where ID=6452863;
ACTION_TIME                      VERSION                 ID
24-JUL-10 12.52.15.390000 PM                        6452863
SQL> @recompile_precheck_jan2008cpu.sql
Running precheck.sql...
Number of views to be recompiled :1637
Number of objects to be recompiled :3487
Please follow the README.txt instructions for running viewrecomp.sql
PL/SQL procedure successfully completed.Case#2: Create a new database using a version that does not require the view recompilation patch. Run the recompile_precheck_jan2008cpu.sql. You will find the view count shows a non-zero value even though you do not need to recompile the views as mentioned in the Oracle patch notes.