Error while installing patch 9.0.1.4

Printable View

03-31-2003, 02:35 AM
pnrdba

Error while installing patch 9.0.1.4

Hi
I'm trying to install a patch p2517300_9014_LINUX on Redhat Linux 7.1 with kernel 2.4.2-2enterprise verion on Oracle 9.0.1.0 to upgrade to 9.0.1.4 version. But when it's asking to check for required OS Specific patches are already installed or not. Can any one let me know how to check in Linux for the patches which are already installed?? any commands/file which tells us about the installed patches ?? If the required patches are not available, then should i download it from linux.com and install? Please help me, i've to do it on production machine... I'm in the mid way

Many Thanks in advance
03-31-2003, 03:25 AM
pando

why you dont check Metalink...?
03-31-2003, 04:15 AM
pnrdba

Hi Pando
I did that already, but couldn't get any info from that. So i posted here...
03-31-2003, 04:21 AM
hrishy

Hi

The command to check what patches are installed is

what oracle

regards
Hrishy
03-31-2003, 04:29 AM
adewri

Quote:

Originally posted by hrishy
Hi

The command to check what patches are installed is

what oracle

regards
Hrishy

i don't think so...

use as root user

Code:

# rpm -q OS_PATCH (to find if its installed or not.) # rpmlocate OS_PATCH (to find where its installed.)

you can also do man rpm to see all the options available with rpm

HTH
03-31-2003, 04:41 AM
adewri

Re: Error while installing patch 9.0.1.4

Quote:

Originally posted by pnrdba
If the required patches are not available, then should i download it from linux.com and install? Please help me, i've to do it on production machine... I'm in the mid way

Many Thanks in advance

Find the rpms at

http://fr2.rpmfind.net/

after downloading the rpm files use

Code:

rpm -ivh|Uvh OS_PATCH.rpm
03-31-2003, 05:11 AM
hrishy

Hi Amar

I am sorry i completely misunderstood the question..PNRDBA please follow amars suggestion..

regards
Hrishy
03-31-2003, 06:27 AM
pnrdba

Hi Amar/Hrishy,
Thanks a lot for your help. Here i'm pasting the document plan for installing patch on prod box. Kindly go thru this once and can you please tell me any thing i'm missing out or any thing need to be addeed??

1. Take a backup of $ORACLE_HOME , i.e. Oracle Software to disk , Just in case if some thing happens, we can fall back on it.

2. Stop the listener.

3. Shutdown the database and take a cold backup of production database on to tape .

4. Check whether the database backup is successful or not.

5. Download the patch from metalink and apply it on our production box.

6. After sucessful installation of the patch start the database and start the listener.

7. Check whether any errors are notified in alert log or not.

8. Check from the fornt-end application for the successful connectivity by connecting from CMS application from different desktops.

10. Check whether all the functionalities are working in the CMS application or not.
03-31-2003, 06:50 AM
hrishy

Hi PNRDBA

well you should first apply the patch to a development box..do you have a test or a development box ?Your plan sounds okay to me..but you should try out a test box first

regards
Hrishy
03-31-2003, 06:51 AM
julian

Quote:

Originally posted by pnrdba
Hi Amar/Hrishy,
Thanks a lot for your help. Here i'm pasting the document plan for installing patch on prod box. Kindly go thru this once and can you please tell me any thing i'm missing out or any thing need to be addeed??

1. Take a backup of $ORACLE_HOME , i.e. Oracle Software to disk , Just in case if some thing happens, we can fall back on it.

2. Stop the listener.

3. Shutdown the database and take a cold backup of production database on to tape .

4. Check whether the database backup is successful or not.

5. Download the patch from metalink and apply it on our production box.

6. After sucessful installation of the patch start the database and start the listener.

7. Check whether any errors are notified in alert log or not.

8. Check from the fornt-end application for the successful connectivity by connecting from CMS application from different desktops.

10. Check whether all the functionalities are working in the CMS application or not.

The order of 3 and5 is sort of strange. I would personally first download the patch, FTP it, untar it, and onlt then shutdown the database :-)