You must upgrade clusterware (separately from Oracle), then Oracle.

My experiment ended in full Oracle reinstallation - 10.2.0.2 killed SLES9
SP3 x86_64 (something looped inside kernel time to time) - I still can count
it on HugeTLB or wrong system setting, but I was not able to find any
difference (and downgrade top 10.2.0.1 helped).


----- Original Message -----
From: "Silviu Marin-Caea" <silviu_marin-caea@(protected)>
To: <suse-oracle@(protected)>
Sent: Thursday, June 08, 2006 7:06 AM
Subject: [suse-oracle] Upgrading to 10.2.0.2, problem with using the right
spfile


> On a test cluster we're experimenting with upgrading to 10.2.0.2.
>
> We have upgraded Clusterware to 10.2.0.2 and everything went fine. It
started
> the database (not patched yet), all ok.
>
> Then we upgraded the database software too.
>
> Now things are not so well anymore.
>
> When we start the database manually, with sqlplus from the oracle user, it
> works fine, it reads the spfile
> from /opt/oracle/product/10gr2/db/dbs/initprod1.ora This is what we
expect.
>
> But when we leave it to Clusterware to start the database, it reads a
wrong
> spfile from /srv/database/data/prod (where we keep the datafiles). In
alert
> log appears as "parameter with non-default value".
>
> Why would it want to use that spfile after the upgrade?
>
> If we rename the wrong spfile, Clusterware does not start the database at
all.
>
>
> --
> To unsubscribe, email: suse-oracle-unsubscribe@(protected)
> For additional commands, email: suse-oracle-help@(protected)
> Please see http://www.suse.com/oracle/ before posting
>
>


--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting