Problem with archive_log_format parameter in SPFILE [message #405329] |
Wed, 27 May 2009 06:54 |
dave_keyur
Messages: 5 Registered: May 2009
|
Junior Member |
|
|
Hi all,
My database is running of oracle 10g. My archive log sequence crossed the 5 digits. Now to make it of 6 digits i modified my parameter in init.ora and spfile using following steps:
shutdown immediate
set parameter in init.ora to log_archive_format='%t_dbname_%s_%r.ARC'
startup pfile='path\init.ora'
create spfile from pfile='path\init.ora';
shutdown immediate
startup
Now when I start the database it generates archive log sequence with 6 digits. But when I again restart the database it again start generating archive log sequence with 5 digits.
And parameter in spfile shows parameter automatically converted to '%T_CWHODDB_%S_%R.ARC'
So how to stop database to automatically convert the log_archive_format in spfile? I do not want to open database with resetlogs.
Help is appriciated.
Thanks and regards
Keyur Dave
|
|
|
|
|
|
Re: Problem with archive_log_format parameter in SPFILE [message #405756 is a reply to message #405371] |
Fri, 29 May 2009 06:04 |
dave_keyur
Messages: 5 Registered: May 2009
|
Junior Member |
|
|
I had done following steps earlier to remove this parameter but was not succeded:
1)
In my parameter file I had removed parameter:
cwhoddb.log_archive_format='%T_CWHODDB_%S_%R.ARC'
and kept only *.log_archive_format='%t_CWHODDB_%s_%r.ARC'
2)
Shut down the database and started with pfile
startup pfile='D:\oracle\product\10.2.0\admin\cwhoddb\pfile\init.ora'
create spfile='D:\oracle\product\10.2.0\db_1\database\SPFILECWHODDB.ORA' from pfile='D:\oracle\product\10.2.0\admin\cwhoddb\pfile\init.ora';
shutdown immediate;
3)
Then started with spfile
startup
This time its generating sequence number with 6 digits.
4)
Then my server was down due to power failure and I restarted the server and database automatically starts as server starts with spfile
And the sequence now generating with 5 digits.
This is the whole scenario I gone through.
But here are some questions from me.
When I check in OEM -> All Initialization Parameter -> spfile -> log_archive_format,
it shows me two values as below:
log_archive_format "%t_dbname_%s_%r.ARC"
log_archive_format "%T_CWHODDB_%S_%R.ARC"
here CWHODDB is our dbname. So in first parameter is shows dbname which dynamically takes database name and in second parameter its taking hardcoded values. So why this two parameter is shown in spfile?
And also when I create pfile from spfile it is containing two values for log_archive_parameter which are as follows:
*.log_archive_format='%t_CWHODDB_%s_%r.ARC'
cwhoddb.log_archive_format='%T_CWHODDB_%S_%R.ARC'
So why spfiel is having this two formats? And how to remove the second parameter cwhoddb.log_archive_format='%T_CWHODDB_%S_%R.ARC'?
Help is appreciated.
Thanks and regards,
Keyur Dave
|
|
|
|
Re: Problem with archive_log_format parameter in SPFILE [message #405853 is a reply to message #405758] |
Sat, 30 May 2009 06:13 |
dave_keyur
Messages: 5 Registered: May 2009
|
Junior Member |
|
|
Hi,
I have serched through whole system there is only one spfile. And I am damne sure its not the issue of multiple spfile. Because I created spfile from pfile, after removing capital lettered parameter from pfile, and resterted and then restart with spfile, and create pfile from spfile, the pfile contains the parameter with capital letters as well as with small letters i.e. two same parameter with small and capital letter value.
Regards,
Keyur
|
|
|
|
Re: Problem with archive_log_format parameter in SPFILE [message #406060 is a reply to message #405858] |
Tue, 02 June 2009 00:18 |
dave_keyur
Messages: 5 Registered: May 2009
|
Junior Member |
|
|
HI,
Thanks for discriptive help.
But there are two log_archive_format parameter in one spfile with different values. So its not the issue of different spfile. I have implemented standby database using data guard. And I think this is the cause for the second parameter which is automatically generated even after removed from spfile. I am also using RMAN. But it should be the cause from standby database only.
Regards,
Keyur Dave
|
|
|