Post installation stpes after upgrading the patch 10.2.0.4

[former_member185031]

HI,

i am following the guide Oracle Upgrade 10g Release 2 on UNIX, and i have upgraded the Oracle patch from 10.2.0.2 to 10.2.0.4 after the SAP installation. But i am not sure about the post installation steps which i need to perform, becuase this guide describe the database upgrade from 9i to 10g, but i was already in 10g so i am not sure what exaclty i need to follow. Could you please suggest me.

Regards,

Subhash

[Former Member · Accepted solution]

Hi Subhash,

till what point you have done now ?

Like if you are just finished with @?/rdbms/admin/catupgrd.sql, then

1. do startup, and SQL> @?/rdbms/admin/utlrp.sql

2. SQL>select count(*) from dba_objects where status<>u2019VALIDu2019; should show invalid objects as zero

3. Run the sql u201Cselect * from dba_scheduler_jobs;u201D

If ORA-01882 occurs then you have to run fix1882.sql supplied with the CPU patch

4. SQL> SELECT count(1) FROM dba_objects WHERE status = 'INVALID'

5. do shudown immediate and then startup

6. Now to disable some of the dba_scheduler jobs:

SQL> select owner, job_name, enabled from dba_scheduler_jobs;

7.

SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');

SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');

SQL>exec dbms_scheduler.disable('SYS.AUTO_SPACE_ADVISOR_JOB');

Then Check the current version of the Oracle time zone definitions

SQL> SELECT version FROM v$timezone_file;

If doesn't return the value 4, then Information about 'Daylight Saving Time' (DST) is available in the 10.2.0.4 patch set README, in SAP Note 1019133, or in the MetaLink Notes 553812.1 or 412160.1

[Former Member · Accepted solution]

and then you should apply all the interim patches like MOPatch, OPatch, CPUJan2009 or CPUApr2009

1027012 u2013 MOPatch, version 19

839182 u2013 Oracle Database 10g: OPatch, version 57

1137346 u2013 Oracle Database 10g: Patches for Release 10.2.0.4, version 55

1233304 u2013 CPU patches version 5

and should not forget the recompilation. Check whether view recompilation has already been performed for the database, execute the following statement

SQL>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

If need to do recompilation, then you have to run recompile_precheck script and then recompilation script included with cpu patch

[Former Member]

HI Subhash,

See README file which is available in PatchSet if You in Windows .For Unix flavour see userGuide in

Patch.For 10.2.0.4 CPU set is required.

If you have any confusion then write

Bye

surendrajain