Re: Clarification pls - Upgrade to 9205 with Security Patches Install Procedures (Solaris 9)

From: Mark Bole <makbo_at_pacbell.net>
Date: Sun, 12 Sep 2004 22:41:16 GMT
Message-ID: <gg41d.18799$gZ4.2369@newssvr27.news.prodigy.com>

John Hurley wrote:

 >>  4.  finally create database (catalog/catproc, etc)
 >>  5.  import full production 734 database into 9205 database with
 >> security patches (3811906 & 3835964)applied
 >> 5a.  finally, run 9205 patchset SQL scripts (catpatch.sql, etc)
 >> 5b.  finally, run Security Alert #68 patch SQL scripts

>

>>Verna

>
>
> Yes your steps look correct ...
>
> Now when you get to creating a database.
>

[...]

To confirm what Remigiusz, Peter, and John have said, your original outline is correct, and steps 5a and 5b are unnecessary.

The minor confusion regarding DBCA comes from this: in Oracle terminology, there are two types of templates: seed and non-seed. The seed type contains "both the structure and the physical datafiles of an existing (seed) database", so if that existing seed database were at a lower patch level, then you would have to run all the migrate (catpatch) scripts against it. If you use a non-seed template, or otherwise create your database "from scratch", then you do not need to do anything extra, it will already reflect the patch updates to your Oracle software installation. Note that DBCA is "not recommended for database creation in larger environments" due to limits on the number of options you can use - but it is good to run it in a test environment, save off the scripts it generates, and then study them to see what new features you might want to use.

I'm pretty sure the catpatch.sql script for most if not all patches is idempotent, meaning you could run it in either scenario and it wouldn't hurt anything (assuming "startup migrate", of course!), but it's only necessary if you patch your software installation after the original database (seed or otherwise) was created.

--Mark Bole Received on Sun Sep 12 2004 - 17:41:16 CDT