100% rely on SPFILE in 9i?
To change the following parameter, you have to update the init.ora first and re-start the db. Right?
NAME VALUE ISSES_MODI ISSYS_MODI
------------------ ---------- ---------- ----------
log_archive_start FALSE FALSE FALSE
Is this the only way to change this parameter "permanently"? I just wonder if you can use SPFILE to do it? If not, it looks like you cannot 100% rely on SPFILE in 9i. You still need to have a init file updated all the time. Am I right?
Re: 100% rely on SPFILE in 9i?
Quote:
Originally posted by dba_admin
To change the following parameter, you have to update the init.ora first and re-start the db. Right?
NAME VALUE ISSES_MODI ISSYS_MODI
------------------ ---------- ---------- ----------
log_archive_start FALSE FALSE FALSE
Is this the only way to change this parameter "permanently"? I just wonder if you can use SPFILE to do it? If not, it looks like you cannot 100% rely on SPFILE in 9i. You still need to have a init file updated all the time. Am I right?
ISSYS_MODIFIABLE=FALSE and ISSES_MODIFIABLE=FALSE does not mean that you can not change this parameter in SPFILE with ALTER SYSTEM command. It simply means that the only scope you can specify with ALTER SYSTEM command is "SPFILE". So you can easily change the above parameter in your spfile with the following command:
ALTER SYSTEM SET log_archive_start=TRUE SCOPE=SPFILE;
Of course the effects will be activated only after the next startup with your spfile.
You don't need any init.ora file to change any parameter in spfile. SPFILE offers you anything you can do with init.ora files and more. You don't need old init.ora files any more if you are using spfile, you can rely 101% on it. The only time you will still need to have init.ora in combination with spfile is when you want to activate your spfile that is stored in non-default location.