I can managed to startup the secondary with nomount mode and startby database successfully but not the primary database.
I have following error message when I start primary DB :
SQL> startup pfile=d:\oracle\admin\mydb\pfile\initmydb.ora
LRM-00101: unknown parameter name 'SERVICE'
LRM-00101: unknown parameter name 'SERVICE'
LRM-00111: no closing quote for value '30"
log_ar'
ORA-01078: failure in processing system parameters
SQL> startup pfile=D:\oracle\admin\mydb\pfile\initmydb.ora
LRM-00111: no closing quote for value 'STBY"
log_'
ORA-01078: failure in processing system parameters
I had change as follow
log_archive_start = true
log_archive_max_processes = 10
log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
# log_archive_dest=d:\oracle\oradata\mydb\archive\
log_archive_dest_1="LOCATION=d:\oracle\oradata\mydb\archive\"
log_archive_dest_state_1=ENABLE
log_archive_dest_2="SERVICE=STBY"
log_archive_dest_state_2=ENABLE
After I changed the log_archive_dest_2 = 'SERVICE=STBY'
LRM-00111: no closing quote for value 'LOCATION=d'
LRM-00113: error when processing file 'd:\oracle\admin\mydb\pfile\initmydb.ora'
ORA-01078: failure in processing system parameters
I get this error then I also modify the log_archive_dest_1
to become log_archive_dest_1 = 'LOCATION=d:\oracle\oradata\mydb\archive\'
I get another error
LRM-00101: unknown parameter name 'SERVICE'
ORA-01078: failure in processing system parameters
it seems quite 'challenge' to setup the standby database.
Originally posted by ckwan
I get this error then I also modify the log_archive_dest_1
to become log_archive_dest_1 = 'LOCATION=d:\oracle\oradata\mydb\archive\'
I belive that last backslash is the culprit of all your troubles! It shouldn't be there. I belive Oracle is interpreting it as an escape character, so the following quote character does not act as an enclosing quote. So Oracle is interpreting path for the LOCATION way down to the next quote chaqracter, which is before SERVICE keyword in log_archive_dest_2 parameter. So it is interpreting the word SERVICE as the next parameter, which of course is unknown and invalid as a parameter.
Remove that backslash and let us know if it has solved your problem.
Originally posted by ckwan
it seems quite 'challenge' to setup the standby database
I've setup standby at least 10 times and never had any major problems .
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Originally posted by ckwan SQL> startup
ORA-00439: feature not enabled: Managed Standby
This is becoming a bit teasing . My guess is you are using Oracle Standard Edition. To use LOG_ARCHIVE_DEST_n parameters (in other words, to implement managed standby configuration) you need Enterprise Edition.
Can you provide details about the database release and type (Enterprise, Standard, Personal) you are using?
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Bookmarks