Skip to Main Content
  • Questions
  • Changing Oracle initialisation parameter - approachI

Breadcrumb

Question and Answer

Tom Kyte

Thanks for the question.

Asked: September 11, 2004 - 4:49 pm UTC

Last updated: September 13, 2004 - 1:40 am UTC

Version: 9.2

Viewed 1000+ times

You Asked

Hi Tom,
There are some Oracle initialisation parameters which still (9ir2) can not be changed dynamically, like parallel_max_servers etc. If I am using spfile, Is the approach below right?
1) create pfile from spfile (not required if spfile and pfile were in sync. before)
2) Change parameter in pfile
3) Bounce DB
4) Start instance, and mount DB with pfile=...
5) create spfile from pfile
6) Bounce Instance
7) Start instance, and mount DB with spfile=....
8) Open DB
Thanks

and Tom said...



how about:

alter system set foo=bar SCOPE=SPFILE;
startup force;

much easier...


Rating

  (5 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Please correct me

Pravesh Karthik from chennai, September 11, 2004 - 6:51 pm UTC

Tom,

Please correct me if i am wrong.

what you mean to say is ...

any new non-dynamic init parameter can be done like above?
for a safer side, can i follow this ...

1) make changes to pfile or alter system scope=spfile
2) create pfile from spfile
3) startup force

is this ok?

startup force? -- using this will not have any adverse effect?

Thanks,
Pravesh Karthik


Tom Kyte
September 12, 2004 - 10:44 am UTC

lose the pfile

use the spfile

startup force is just shorthand for

shutdown abort
startup



TO: Pravesh Karthik from chennai

Marcio, September 11, 2004 - 10:45 pm UTC

PMFJI,

As per change non-dynamic parameters all you need to do is 
SQL> alter system set foo=bar scope=spfile;

Forget about pfile, if you need one just create pfile from spfile.

1) alter system ... scope=spfile;
2) for your script backup yes -- you want to save pfile.
3) You need understand what startup force does:
If an instance is running, STARTUP FORCE shuts it down with mode ABORT before restarting it.

When Tom advices you startup force, I suppose he means "restart your database" as you've felt comfortable.
eg.
shutdown <your safer option>; 
startup; 

Once again sorry for jump in -- just want to help.
Regards, 

Thanks

Pravesh Karthik from chennai, September 12, 2004 - 12:46 pm UTC

Tom,

Thanks, i appreciate your considweration to clear my doubt.
a little surprise to me here - i think shutdown abort is not recommended. but you have you suggested here. not sure why.

Thanks again.
Pravesh Karthik

Tom Kyte
September 12, 2004 - 4:37 pm UTC

shutdown abort is ok. it won't hurt your database. it won't cause loss of data. It is just rather "rude", "crude" and very effective.

Thanks for your confirmation

Pravesh Karthik from chennai, September 13, 2004 - 12:01 am UTC


simple but cleared many things

Mehmood, September 13, 2004 - 1:40 am UTC

Tom's answer is very good. Don't know how Tom think in this manner! :)