Home > Archive > Oracle Server > July 2005 > Primary instandce terminated in max performance mode.









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Primary instandce terminated in max performance mode.
ennarr

2005-07-27, 9:23 am

We have a standby database setup on DB version 9.2.0.4.0.
Primary init.ora setting for standby destination is

log_archive_dest_2='
SERVICE=STBY LGWR ASYNC=40960'
log_archive_dest_sta
te_2='ENABLE'
log_archive_min_succ
eed_dest is not set but by default it is 1.
SQL> show parameter min_succ

NAME TYPE VALUE
------------------------------------ -----------
------------------------------
log_archive_min_succ
eed_dest integer 1
SQL>

We had 4 redo log files on the Primary.
We took the Shutdown of the standby with out setting the
log_archive_dest_sta
te_2 to DEFER.

SQL> select PROTECTION_MODE,PROT
ECTION_LEVEL from v$database;

PROTECTION_MODE PROTECTION_LEVEL
-------------------- --------------------
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE

The primary database stopped after completing one cycle of the redo
logs with the error
PMON: terminating instance due to error 16024 in the alert log.

When the database is with the above settings the primary instance
should not be terminated is it not?

By default log_archive_dest_2 is OPTIONAL when "MANDATORY" is not set.
Then why should the instance halt?
Am I missing any parameters?

Thanks
Ravi

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com