Physical Standby Switchover issue

Links

Frequent Oracle Errors

•	TNS:could not resolve the connect identifier specified
•	Backtrace message unwound by exceptions
•	invalid identifier
•	PL/SQL compilation error
•	internal error
•	missing expression
•	table or view does not exist
•	end-of-file on communication channel
•	TNS:listener unknown in connect descriptor
•	insufficient privileges
•	PL/SQL: numeric or value error string
•	TNS:protocol adapter error
•	ORACLE not available
•	target host or object does not exist
•	invalid number
•	unable to allocate string bytes of shared memory
•	resource busy and acquire with NOWAIT specified
•	error occurred at recursive SQL level string
•	ORACLE initialization or shutdown in progress
•	archiver error. Connect internal only, until freed
•	snapshot too old
•	unable to extend temp segment by string in tablespace
•	Credential retrieval failed
•	missing or invalid option
•	invalid username/password; logon denied
•	unable to create INITIAL extent for segment
•	out of process memory when trying to allocate string bytes
•	shared memory realm does not exist
•	cannot insert NULL
•	TNS:unable to connect to destination
•	remote database not found'>ora-02019
•	exception encountered: core dump
•	inconsistent datatypes
•	no data found
•	TNS:operation timed out
•	PL/SQL: could not find program
•	existing state of packages has been discarded
•	maximum number of processes exceeded
•	error signaled in parallel query server
•	ORACLE instance terminated. Disconnection forced
•	TNS:packet writer failure
•	see ORA-12699
•	missing right parenthesis
•	name is already used by an existing object
•	cannot identify/lock data file
•	invalid file operation
•	quoted string not properly terminated

Physical Standby Switchover issue

Physical Standby Switchover issue

2005-09-04 - By Sami Seerangan

Reply: 1 2 3 4

While doing switchover in physical standby database which is operating in
Maximum Availability mode, I got into this error.
I do have standby logfiles.

SQL> select switchover_status from v$database;

SWITCHOVER_STATUS
-- ---- ---- -----
SESSIONS ACTIVE

SQL> alter database commit to switchover to primary with session shutdown;
alter database commit to switchover to primary with session shutdown
*
ERROR at line 1:
ORA-16139 (See ORA-16139.ora-code.com): media recovery required

SQL> recover standby database;
ORA-00279 (See ORA-00279.ora-code.com): change 318016 generated at 09/04/2005 13:57:41 needed for thread
1
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u07/oradata/dgtest/0001S0000000056.ARC
ORA-00280 (See ORA-00280.ora-code.com): change 318016 for thread 1 is in sequence #56

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00279 (See ORA-00279.ora-code.com): change 318016 generated at 09/03/2005 21:06:49 needed for thread
2
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u07/oradata/dgtest/0002S0000000009.ARC
ORA-00280 (See ORA-00280.ora-code.com): change 318016 for thread 2 is in sequence #9

ORA-00328 (See ORA-00328.ora-code.com): archived log ends at change 317689, need later change 318016
ORA-00334 (See ORA-00334.ora-code.com): archived log: '/u07/oradata/dgtest/0002S0000000009.ARC'

Thanks
Sami

While doing switchover in physical standby database which is operating in
Maximum Availability mode, I got into this error. 
I do have standby logfiles. 
 
SQL> select switchover_status from v$database; 
  
SWITCHOVER_STATUS 
-- ---- ---- ----- 
SESSIONS ACTIVE 
  
  
SQL> alter database commit to switchover to primary with session shutdown;
 
alter database commit to switchover to primary with session shutdown 
* 
ERROR at line 1: 
ORA-16139 (See ORA-16139.ora-code.com): media recovery required 
  
  
SQL> recover standby database; 
ORA-00279 (See ORA-00279.ora-code.com): change 318016 generated at 09/04/2005 13:57:41 needed for thread 1
 
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u07/oradata/dgtest/0001S0000000056.ARC 
ORA-00280 (See ORA-00280.ora-code.com): change 318016 for thread 1 is in sequence #56 
  
  
Specify log: {<RET>=suggested | filename | AUTO | CANCEL} 
AUTO 
ORA-00279 (See ORA-00279.ora-code.com): change 318016 generated at 09/03/2005 21:06:49 needed for thread 2
 
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u07/oradata/dgtest/0002S0000000009.ARC 
ORA-00280 (See ORA-00280.ora-code.com): change 318016 for thread 2 is in sequence #9 
  
  
ORA-00328 (See ORA-00328.ora-code.com): archived log ends at change 317689, need later change 318016 
ORA-00334 (See ORA-00334.ora-code.com): archived log: '/u07/oradata/dgtest/0002S0000000009.ARC' 
 
Thanks 
Sami