I then created an spfile from the pfile with only the dynamic parameters corrected.
create pfile from spfile;
But I was looking at an out of date article which put the had an error about the default location of the spfile.
SELECT name, value FROM v$parameter WHERE name = 'spfile';
gave me the actual location of my spfile, which being in the default location was in
$ORACLE_HOME/dbs/spfileSID.ora
Then bounced the database and brought it up with the spfile.
But, of course, the static parameters need a bounce to the database.
I altered the parameters scope = spfile eg:
ALTER SYSTEM SET processes = 300 SCOPE=SPFILE;
and then rebounced the database to apply the dynamic changes also to the current instance.
THEN I BACKED UP THE SPFILE!
(now if only I could control the fonts on this blog, all would be well.)
2 comments:
we had a similar case recently, for us alert.log was the savior, we copied the parameters from the last successful startup of alert.log and pasted into a pfile, created an spfile from that pfile and started the instance.
Thanks Tonguc, I'll remember that one. -Claudia
Post a Comment