deprecated parameter not in spfile and cannot reset in memory [message #581966] |
Fri, 12 April 2013 04:55  |
 |
onkarbanerjee
Messages: 11 Registered: April 2013 Location: Bangalore
|
Junior Member |
|
|
Hi,
i try to startup a database, and get that obsolete/deprecated parameter specified(ORA-32004: obsolete and/or deprecated parameter(s) specified)
so i try to reset the parameter, but it seems it is already reset(not in spfile), so maybe this is in memory. SO now i try to reset with scope = memory or both, it gives this error(ORA-32029: resetting with SCOPE=MEMORY or SCOPE=BOTH is currently not supported).
Please advise , what to do, because now i cannot reset with scope = memory and in spfile it is not there but still it comes in deprecated parameter.
|
|
|
|
|
|
|
|
Re: deprecated parameter not in spfile and cannot reset in memory [message #581984 is a reply to message #581972] |
Fri, 12 April 2013 07:23   |
 |
onkarbanerjee
Messages: 11 Registered: April 2013 Location: Bangalore
|
Junior Member |
|
|
Hi John,
The DB is using SPFILE only and value of log_archive_start parameter was false only as i had mentioned previously, however i think i might have copied your sql wrongly in a hurry and posted that the v$spparameter not exist,whereas the it was existing, meaning to say the value was FALSE in it also, sorry for the miscommunication(was in a kind of a hurry for something).
Anyways, issue got resolved though by doing nothing about log_archive_start parameter value but now it got reset(did the same thing in the morning, but it wouldnt reset then, probably made a mistake then even)
>alter system reset log_archive_start scope=spfile sid='*';
ANyways, it solved now, and Thanks
|
|
|
|