Applying Patches using adpatch

**********************

Steps overview:
**********************

1. bring down instance
2. Enable Maintenance mode
3. Apply Patch
4. Disable Maintenance

**********************
Steps in detail:
**********************

1^st –Research patch (check prereqs and settings)

2^nd- check that it hasn’t been applied already

            SQL> select * from ad_bugs where bug_number = ‘’;

3^rd – FTP the patch from oracle

            >ftp updates.oracle.com (coresys/coredba)

            >cd

            >bin

            > ls –         ex. ls –linux

            >get .zip    ex. get p3948369_11i_linux.zip

            >bye

4^th – go the patch directory

            >cd /patch/patches or solaris or generic

5^th -  unzip the patch in /patch/patches/SOLARIS/XXXX/

6^th -  bring down the instance and email everyone(opsdesk, dbadesk and functional)

            -Run the shut script in home directory

            - Make sure all processes are dead

7^th – go to adpatch (all defaults except size = 12,000 and sys pwd = manager)

            Apply patches in order (‘c,d,g’ in that order – or just ‘u’ if only one)

(“adpatch flags=hidepw options=noprereq” if it doesn’t work successfully? Only sometimes?)

Here are the prompts you will get, step by step:

- Is this the correct APPL_TOP [Yes] ?

- Filename [adpatch.log] :  XXXX_c/d/g/u#.log, i.e. - INST_c3358343.log

- You can be notified by email if a failure occurs.

Do you wish to activate this feature [No] ?

- Please enter the batchsize [1000] : 12000

- Is this the correct database [Yes] ?

- Enter the password for your 'SYSTEM' ORACLE schema: manager

- Enter the ORACLE password of Application Object Library [APPS] : - sometimes apps

- The default directory is [/patch/patches/SOLARIS/INTT/3358343] :

- Please enter the name of your AutoPatch driver file - c/d/g#.drv i.e. - d3358343.drv

ON d DRIVERS:

AD utilities can support a maximum of 999 workers. Your

current database configuration supports a maximum of 222 workers.

Oracle recommends that you use between 20 and 40 workers.

Enter the number of parallel workers [20] :

Watch it go!

            * * if error occurs asking to change the maintenance mode- change mode using

                        adadmin and re-run the patch and press no to the question asking to start

                        where patch last left of and then yes to confirm answer. Once the patch is

                        done- go back to adadmin and disable maintenance mode.

8^th – bring up the instance  :  start

9^th – bounce apache server

            - log into application and submit active users before releasing the instance.

10^th – compile invalid objects after patching

11^th - run the above query and check file version to make sure patch has been applied.