SAP Opatch

Embed Size (px)

Citation preview

  • 7/31/2019 SAP Opatch

    1/3

    Oracle Bundle Patch

    How to Apply Oracle Bundle Patch

    Download the dump from SAP service market place to your system.

    1.PRE INSTALLATION INSTRUCTIONS

    Copy the dumps of patch at below mentioned path.

    Drive/oracle/"SID"/"oracle version"/OPatch

    Stop SAP & DB along with all services of SAP & DB.

    Back up the current database that is installed, the %ORACLE_HOME% directory and

    Oracle inventory under c:\Program files\oracle directory. (This will help if there are

    problems applying the patch, and to restore the Inventory in case of an issue with thepatch.)

    Now apply bundle patch.

    OPatch>opatch apply patch no

    Installation may be interrupted coz. of error in overwriting an existing .dll file giving

    following error file already in use.

    In case of above error dont rename the file and RETRY(It doesnt work) instead cancel the

    installation then and there rename the .dll file and start patch application again.

    3. POST INSTALLATION INSTRUCTIONS

    Start all services of DB & DB

    Run script catcpu.sql

    sqlplus /nolog

    SQL> CONNECT / AS SYSDBA

    SQL> STARTUP

    SQL> @%ORACLE_HOME%\Bundle\Patch17\catcpu.sql

    SQL> QUIT

    If above script reports any error then

  • 7/31/2019 SAP Opatch

    2/3

    Inspect the logfile %ORACLE_HOME%\Bundle\Patch17\Apply__.log for any errors.

    If catcpu.sql reports any Invalid Objects, compile the invalid objects as follows.

    sqlplus /nolog

    SQL> CONNECT / AS SYSDBA

    SQL> @%ORACLE_HOME%\rdbms\admin\utlprp.sql 0

    Above script will compile the invalid objects.

    To check for any invalid objects still there or not, execute the following statement:

    SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID';

    Recompiling Views in the Database

    To recompile the views for each database instance running out of the ORACLE_HOME being

    patched , follow these steps:

    Run the pre-check script, which reports the maximum number of views and objects that

    may be recompiled:

    sqlplus /nolog

    SQL> CONNECT / AS SYSDBA

    SQL> @%ORACLE_HOME%\Bundle\view_recompile\ recompile_precheck_jan2009cpu.sql

    SQL> QUIT

    Run the view recompilation script. Note that this script is run with the database in upgrade

    mode, which restricts connections as SYSDBA.

    sqlplus /nolog

    SQL> SHUTDOWN

    SQL> CONNECT / AS SYSDBA

    SQL> STARTUP UPGRADE

    SQL>@%ORACLE_HOME%\Bundle\view_recompile\

    view_recompile_jan2008cpu.sql

    SQL> SHUTDOWN;

  • 7/31/2019 SAP Opatch

    3/3

    SQL> STARTUP;

    Check the log file for any errors. The log file is in the current directory and is named:

    vcomp__.log

    If any invalid objects were reported, run the utlrp.sql script as follows:

    sqlplus /nolog

    SQL> CONNECT / AS SYSDBA

    SQL> @%ORACLE_HOME%\rdbms\admin\utlrp.sql

    If still any invalid objects are there then recompile those manually.

    SQL> alter schemaname. compile;

    Verify that the view recompilation has been performed for the database, by executing thefollowing statement:

    SELECT * FROM registry$history where ID = '6452863';

    TO VIEW ALL PATCHES APPLIED ISSUE BELOW COMMAND:-

    \ORACLE\"SID"\"oracle version"\OPATCH>OPATCH LSINVENTORY