| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: spfile help needed
Alan
If you have started the instance without an spfile (i.e. you're using a pfi= le) and then create the spfile, you will need to restart the instance for t= he spfile to be used.
For those parameters that are not system modifiable, you can use the scope=3D= spfile clause to make the changes there. Since you are not changing the me= mory value, that change will only take effect on next startup.
The alter system reset clause is really only for use in a RAC environment.
=
Pete
=
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
=
"Oh no, it's not. It's much harder than that!" Bruce Pihlamae, long-term Oracle DBA
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] =
On Behalf Of Martin, Alan (Contractor) (DLIS)
Sent: Friday, 21 May 2004 5:50 AM
To: 'oracle-l_at_freelists.org'
Subject: spfile help needed
The docs say that once an spfile is generated, all changes to the DB
parameters occur via "ALTER SYSTEM SET <param>=3D<value> [comment] [scope]
[sid]", and the pfile is out of the loop. Based on my observations, please
comment on the following:
1) Is it true that immediately after "create spfile from pfile", the spfile=
is not actually used until the first bounce?
Using an spfile or the old pfile, trying to ALTER SYSTEM on AUDIT_FILE_DEST=
yields:
ORA-02095: specified initialization parameter cannot be modified.
2) Does this mean you must first "create pfile from spfile", edit the pfile=
,
and then recreate the spfile?
3) Since AUDIT_FILE_DEST is not system modifiable, why doesn't "alter syste=
m
set AUDIT_FILE_DEST =3D '<my_dir>' scope=3Dspfile" work? That would avoid h=
aving
to perform (2) above.
4) Has anyone had any luck using "ALTER SYSTEM RESET <param>"? alter system reset timed_statistics
*
Any insight would be appreciated.
Thanx,
Alan Martin
Northrop Grumman IT
Battle Creek, MI
 |
 |