[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-oracle
Subject:    FW: [suse-oracle] Installation 9.2.0.4 on SLES8 SP3
From:       Greg Wallace <gregwallace () alaska ! com>
Date:       2004-04-21 9:14:38
[Download RAW message or body]



-----Original Message-----
From: Greg Wallace [mailto:gregwallace@alaska.com] 
Sent: Tuesday, April 20, 2004 3:03 PM
To: 'hforbic_suse@telus.net'
Cc: 'suse-oracle@suse.com'
Subject: FW: [suse-oracle] Installation 9.2.0.4 on SLES8 SP3

Hans:

     Point well taken.  I've only been in these forums for a couple of weeks
and need to get used to how to respond (i.e., to forum).  I'm ccing this
over to suse-oracle.

Greg

-----Original Message-----
From: Hans Forbrich [mailto:hforbric_suse@telus.net] 
Sent: Tuesday, April 20, 2004 6:38 AM
To: Greg Wallace
Subject: Re: [suse-oracle] Installation 9.2.0.4 on SLES8 SP3

On Tuesday 20 April 2004 03:14, you wrote:
> My approach, when changing parameters, is to change them in my historical
> pfile and then do a STARTUP PFILE=.  If there is some problem, I see it
> right away and don't have to struggle with correcting the corrupted
SPFILE,
> which can happen if you do ALTER SYSTEM SCOPE=SPFILE (or BOTH).  If there
> are problems with my new parameters, I can then clean that up and repeat
> the process without having to worry about getting the new SPFILE corrected
> in the database. Once I'm satisfied with the stability, I simply do the
> CREATE SPFILE FROM PFILE=... to make the changes permanent, leaving me
with
> the pfile that is the basis for the newly created SPFILE.

Reasonable approach.

My post .... The OP didn't ack SPFILE or understand why it's used.  

(Not sure why you responded to me rather than list though - your comments
are 
good enough to share.)

/Hans



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

[prev in list] [next in list] [prev in thread] [next in thread]