Physical Standby - Recovery error

Hi,
Windows XP, 10.2.0.1.0
I m getting the error like
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01103: database name 'PRIM' in control file is not 'STBY'
Please suggest me
Thanks
KSG
Edited by: KSG on Jun 15, 2010 1:15 PM

Hi,
Hope I have some issue with the parameter file. Please find my parameter files
initPRIM.ora
PRIM.__db_cache_size=411041792
PRIM.__java_pool_size=4194304
PRIM.__large_pool_size=4194304
PRIM.__shared_pool_size=163577856
PRIM.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/PRIM/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\PRIM\control01.ctl','C:\oracle\product\10.2.0\oradata\PRIM\control02.ctl','C:\oracle\product\10.2.0\oradata\PRIM\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='PRIM'
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=PRIMXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=197132288
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=591396864
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/udump'
*.log_archive_dest_1='location=C:\oracle\archiveprim'
*.log_archive_format='ARCH_%r_%t_%s.ARC'
initstby.ora
stby.__db_cache_size=411041792
stby.__java_pool_size=4194304
stby.__large_pool_size=4194304
stby.__shared_pool_size=163577856
stby.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/stby/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/stby/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\CONTROL_SB01.CTL'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/stby/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='stby'
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=stbyXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=197132288
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=591396864
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/stby/udump'
*.log_archive_dest_1='location=C:\oracle\archivestby'
*.log_archive_format='ARCH_%r_%t_%s.ARC'
*.standby_archive_dest='C:\oracle\archiveprim'
*.db_file_name_convert='C:\oracle\product\10.2.0\oradata\PRIM','C:\oracle\product\10.2.0\oradata\stby'
*.log_file_name_convert='C:\oracle\product\10.2.0\oradata\PRIM','C:\oracle\product\10.2.0\oradata\stby'
*.standby_file_management=AUTO
*.remote_archive_enable=TRUE

Similar Messages

Physical standby database error

Hi,
I try to create physical standby in my local machine using oracle 10g
version :10.2.0.1.0
Os: windows xp.
I followed steps and parameter files
on primary :-
sql>alter database force logging;
orcl.__db_cache_size=155189248
orcl.__java_pool_size=4194304
orcl.__large_pool_size=4194304
orcl.__shared_pool_size=75497472
orcl.__streams_pool_size=0
*.audit_file_dest='D:\oracle\product\10.2.0/admin/orcl/adump'
*.background_dump_dest='D:\oracle\product\10.2.0/admin/orcl/bdump'
*.compatible='10.2.0.1.0'
*.control_files='D:\oracle\product\10.2.0\oradata\orcl\control01.ctl','D:\oracl
e\product\10.2.0\oradata\orcl\control02.ctl','D:\oracle\product\10.2.0\orad
ata\orcl\control03.ctl'
*.core_dump_dest='D:\oracle\product\10.2.0/admin/orcl/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='orcl'
*.db_unique_name='orcl'
*.log_archive_config='DG_CONFIG=(orcl,stby)'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=80740352
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=244318208
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='D:\oracle\product\10.2.0/admin/orcl/udump'
*.log_archive_dest_1='LOCATION=D:\oracle\archive
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl'
*.log_archive_dest_2='SERVICE=stby LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stby'
*.log_archive_format=%t_%s_%r.arc
*.log_archive_dest_state_1=ENABLE
*.log_archive_dest_state_2=ENABLE
On standby
orcl.__db_cache_size=155189248
orcl.__java_pool_size=4194304
orcl.__large_pool_size=4194304
orcl.__shared_pool_size=75497472
orcl.__streams_pool_size=0
*.audit_file_dest='D:\stby\adump'
*.background_dump_dest='D:\stby\bdump'
*.compatible='10.2.0.1.0'
*.control_files='D:\stby\ctrl.ctl'
*.core_dump_dest='D:\stby\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='orcl'
*.db_unique_name='stby'
*.log_archive_config='DG_CONFIG=(orcl,stby)'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=80740352
*.processes=150
*.remote_login_passwordfile='NONE'
*.sga_target=244318208
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='D:\stby\udump'
*.db_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
*.log_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
*.log_archive_dest_1='LOCATION=D:\oracle\archive
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stby'
*.log_archive_dest_2='SERVICE=orcl LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=orcl'
*.standby_archive_dest='D:\stby\archive'
*.log_archive_dest_state_1=ENABLE
*.log_archive_dest_state_2=ENABLE
*.standby_file_management='AUTO'
*.fal_server='orcl'
*.fal_client='stby'
SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup pfile=D:\stby\initstby.ora nomount;
ORACLE instance started.
Total System Global Area 247463936 bytes
Fixed Size 1248332 bytes
Variable Size 79692724 bytes
Database Buffers 159383552 bytes
Redo Buffers 7139328 bytes
SQL> alter database mount standby database;
Database altered.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
SQL> recover managed standby database cancel;
Media recovery complete.
SQL> alter database open read only;
Database altered.
SQL> select sequence#,first_time,next_time from v$archived_log order by sequence
no rows selected
No archive s generated in standby ..
what i mistake.
Reagrds
S.Azar

Anand... wrote:
Firstly you can use "*select sequence#,first_time,next_time from v$archived_log order by sequence#;"* command in mount stage itself.No need to open the standby database in ready only mode.
No rows selected in mount stage also.
The V$ARCHIVED_LOG fixed view on the physical standby database shows all the archived redo log files received from the primary database.
sql> select * from v$archived_log;
no rows selected.
and No archived logs received from primary database to physical standby . i think here i wrongly configure parameter file.
sql> RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; -- > start Redo Apply
When you do log switch on the primary are the archive logs getting transferred to the standby database???Is there some error in the alert log file in the primary database.
No..
>
[http://advait.wordpress.com/2007/06/12/setting-up-oracle-dataguard-for-10g/]
Regards
S.Azar

Physica standby recovery problem

Hi,
I am trying to recover physical standby database manually
I am getting below error:
alter database recover standby database parallel (degree 32);
alter database recover standby database parallel (degree 32)
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
I have tried to cancel managed recovery, but no managed recovery is active.
alter database recover managed standby database cancel;
alter database recover managed standby database cancel
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active
select distinct recovery_mode from v$archive_dest_status;
RECOVER
IDLE
Please help me to resolve this. Thanks in advance.
regards,
Narendra

Apparently this is bug 5084496, related to parallel recovery on 10.1 and below (ML note 361883.1). You may avoid this bug if you don't use parallel recovery. It looks like there are no one-off patches available, so you are stuck with either serial recovery or upgrade to 10.2 or higher :-(
Regards,
Jeremiah Wilton
ORA-600 Consulting
http://www.ora-600.net

Standby recovery error on data guard

Hi,
I am creating data guard of Oracle 9i in windows server 2003. I have copied all the primary datafiles with created standby control file to standby server and issued
recover automatic standby database I am getting the below error.
SQL> recover automatic standby database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'.
File is present at OS level and since these are standby i have changed the directory name to orcl1 to orcl2.
Db version: 9.2.0.6.0
OS version: windows server 2003
Edited by: user10724679 on Feb 1, 2012 1:16 PM

I am creating data guard of Oracle 9i in windows server 2003. I have copied all the primary datafiles with created standby control file to standby server and issued
recover automatic standby database I am getting the below error.
SQL> recover automatic standby database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'.
File is present at OS level and since these are standby i have changed the directory name to orcl1 to orcl2.
Db version: 9.2.0.6.0
OS version: windows server 2003
Edited by: user10724679 on Feb 1, 2012 1:16 PMWell, As per the primary/source controlfile , All datafile location points to ORCL1, But now you copied them to ORCL2, Then how oracle knows that you have changed location? So before starting MRP, you have rename all those files as
SQL> alter database rename file 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF' to 'D:\ORACLE\ORADATA\ORCL2\SYSTEM01.DBF';
Like that rename all the datafiles & log files.
Then start MRP. Post if any errors.

Error while trying to open physical standby database - (DATA GUARD)

Hi Everyone,
I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
Primary Database spec: (2 Node Rac on ASM)
Oracle Version : 10.2.0.3.0
O/s : HP-UX B.11.23
Standby Database spec: (Single Node)
Oracle Version : 10.2.0.3.0
O/s: HP-UX db01 B.11.23
Error:
alter database recover managed standby database cancel;
Database altered.
SQL> alter database open
2 ;
alter database open
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DATA/dprod/datafile/system01.dbf'
Parameters :
log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
FOR=(ONLINELOGFILES,PRIMARY_
ROLE) DB_UNIQUE_NAME=PROD
remote_archive_enable string true
fal_client string DPROD
fal_server string PROD1, PROD2
Steps tried so far:
Changed log_archive_dest_2 = DEFER on both the primary nodes
Standby :
startup nomount
alter database mount standby database;
alter database recover managed standby database disconnect;
alter database recover managed standby database cancel;
alter database open/readonly (tried both)
Same error.
On Primary:
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
55702
on Standby:
MAX(SEQUENCE#)
33289
Primary Database:
SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
55700 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55702 13-JUN-11 13-JUN-11
60824 rows selected.
Standby Database:
SEQUENCE# FIRST_TIME NEXT_TIME
55698 13-JUN-11 13-JUN-11
55699 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
15206 rows selected.
Additional Information :
There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
Any help will be highly appreciated. Thanks in advance
Sadiq

Hi,
Primary Database:
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
STATUS CHECKPOINT_COUNT
ONLINE 57717
ONLINE 57717
57 rows selected.
Standby Database;
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
STATUS CHECKPOINT_COUNT
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
STATUS CHECKPOINT_COUNT
ONLINE 30723
ONLINE 30723
57 rows selected.
Archieve log list :
Primary database:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 49111
Current log sequence 49111
Standby Database:
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 0
Current log sequence 49111
I tried log switch multiple times in primary database i saw that its getting highlighted in standby database.

Corrupting the block to continue recovery in physical standby

Hi,
Just like to inquire how I will be able to corrupt the block to be able to continue the recovery in the physical standby.
DB Version: 11.1.0.7
Database Type: Data Warehouse
The setup we have is primary database and standby database, we are not using dataguard, and our standby setup is another physical copy of production which act as standby and being sync using script that being run from time to time to apply the archive log came from production (its not configured to sync using ARCH or LGWR and its corresponding configurations).
Then, the standby database is not sync due to errors encountered while trying to apply the archive log, error is below:
Fri Feb 11 05:50:59 2011
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /u01/archive/<sid>/1_50741_651679913.arch
Fri Feb 11 05:52:06 2011
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0, kdr9ir2rst0()+326]
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc (incident=631460):
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Incident details in: /u01/app/oracle/diag/rdbms/<sid>/<sid>/incident/incdir_631460/<sid>pr0028085_i631460.trc
Fri Feb 11 05:52:10 2011
Trace dumping is performing id=[cdmp_20110211055210]
Fri Feb 11 05:52:14 2011
Sweep Incident[631460]: completed
Fri Feb 11 05:52:17 2011
Slave exiting with ORA-10562 exception
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc:
ORA-10562: Error occurred while applying redo to data block (file# 36, block# 1576118)
ORA-10564: tablespace <tablespace name>
ORA-01110: data file 36: '/u02/oradata/<sid>/<datafile>.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 14877145
ORA-00607: Internal error occurred while making a change to a data block
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Based on the error log it seems we are hitting some bug from metalink (document id 460169.1 and 882851.1)
my question is, the datafile # is given, block# is known too and the data object is also identified. I just verified that object is not that important, is there a way to set the block# to corrupted to be able the recovery to continue? Then I will just drop the table from production so that will also happen in standby, and the block corrupted will be gone too. Is this feasible?
If its not, can you suggest what's next I can do so the the physical standby will be able to sync again to prod aside from rebuilding the standby?
Please take note that I also tried to dbv the file to confirm if there is marked as corrupted and the result for that datafile is also good:
dbv file=/u02/oradata/<sid>/<datafile>_19.dbf logfile=dbv_file_36.log blocksize=16384
oracle@<server>:[~] $ cat dbv_file_36.log
DBVERIFY: Release 11.1.0.7.0 - Production on Sun Feb 13 04:35:28 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = /u02/oradata/<sid>/<datafile>_19.dbf
DBVERIFY - Verification complete
Total Pages Examined : 3840000
Total Pages Processed (Data) : 700644
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 417545
Total Pages Failing (Index): 0
Total Pages Processed (Other): 88910
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 2632901
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 3811184883 (1.3811184883)
Any help is really appreciated. I hope to hear feedback from you.
Thanks

damorgan, i understand the opinion.
just new with the organization and just inherit a data warehouse database without rman backup. I am still setting up the rman backup thats why i can't use rman to resolve the issue, the only i have is physical standby and its not a standby that automatically sync using dataguard or standard standby setup, i am just checking solution that is applicable in the current situation

Creating physical standby using rman fails with ORA-19558: error de-allocat

Dear All,
We are creating physical stadnby database from 2 node RAC ( 2 node RAC to standalone physical standby).
While in the rman duplicate process we are getting below error, we were not able to sorted out..
No third party storage has been used ....
DB version : 11gR2 and the OS is RHEL5
Appreciate if any one hepl us to resolve this issue ...
Thanks in advance ...
RMAN-03009: failure of backup command on prmy1 channel at 10/05/2011 17:59:26
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03113: end-of-file on communication channel
Edited by: 889828 on 2011/10/06 2:17 AM

The problem is well decribed in your alert log.....you are using Oracle Managed File names which means you will not be able to duplicate the database as RMAN won't be able to automatically generate new names for the files using the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT initialization parameters.
Youll have to use the SET NEWNAME command to specify the names of the database files. Done this a few times , and I don't recommend using OMF specifically beacuse of this hassle.
WARNING: OMF is enabled on this database. Creating a physical standby controlfile, when OMF is enabled on the primary database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures describing how to manually resolve OMF datafile pathnames.
Problem handling is described in
Oracle® Database Backup and Recovery Reference
10g Release 2 (10.2)
Part Number B14194-03

Error raised when opening physical standby in read only

Hi,
I've a physical standby 11.2.0.2 created using RMAN duplicate from active database which is configured with data guard. When I open the database in READ ONLY mode
SQL> alter database open read only;
Database altered.
SQL> select open_mode from v$database;
OPEN_MODE
READ ONLY
I get this error in the alert log
Physical standby database opened for read only access.
Fri Aug 12 15:14:01 2011
db_recovery_file_dest_size of 256000 MB is 4.72% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Errors in file /oradata/admin/ORAINT/diag/diag/rdbms/oraintsb/oraintsb/trace/ora intsb_ora_8692.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00931: missing identifier
ORA-06512: at "SYS.DBMS_UTILITY", line 156
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 72
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 84
ORA-06512: at "SYS.PROC_PKGS_KEEP", line 26
ORA-06512: at line 2
Completed: alter database open read only
the tracefile is showing this,
Trace file /oradata/admin/ORAINT/diag/diag/rdbms/oraintsb/oraintsb/trace/oraintsb_ora_8692.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /opt/oracle/product/11.2.0/ORAINT
System name: Linux
Node name: c4p-db01
Release: 2.6.18-194.0.0.0.3.el5xen
Version: #1 SMP Mon Mar 29 18:27:00 EDT 2010
Machine: x86_64
VM name: Xen Version: 3.4 (PVM)
Instance name: oraintsb
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 8692, image: oracle@c4p-db01 (TNS V1-V3)
*** 2011-08-12 15:14:03.367
*** SESSION ID:(24.1) 2011-08-12 15:14:03.367
*** CLIENT ID:() 2011-08-12 15:14:03.367
*** SERVICE NAME:(SYS$USERS) 2011-08-12 15:14:03.367
*** MODULE NAME:(sqlplus@c4p-db01 (TNS V1-V3)) 2011-08-12 15:14:03.367
*** ACTION NAME:() 2011-08-12 15:14:03.367
Error in executing triggers on database startup
*** 2011-08-12 15:14:03.367
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)
----- Error Stack Dump -----
ORA-00604: error occurred at recursive SQL level 1
ORA-00931: missing identifier
ORA-06512: at "SYS.DBMS_UTILITY", line 156
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 72
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 84
ORA-06512: at "SYS.PROC_PKGS_KEEP", line 26
ORA-06512: at line 2
if I disable the system triggers using
ALTER SYSTEM SET "_system_trig_enabled"=FALSE scope=both;
The error doesn't appear but when trying to switch to active dataguard the open_mode goes from READ ONLY to MOUNTED rather than READ ONLY WITH APPLY
Any help much appreciated
Edited by: phil74 on 12-Aug-2011 07:22

Have you checked what your guard status is set to?
SQL> SELECT guard_status from v$database;I've had a similar issue before but with a standby, whereby the status was set to ALL. This means all users apart from SYS are unable to make changes on the database.
My resolution was to set the status to standby:
SQL> ALTER DATABASE GUARD STANDBY;You may wish to set the guard status to NONE however.
I took some notes:
http://juniororacledba.wordpress.com/2011/07/17/oracle-logical-standby-dataguard-error However, I do not have a link to any Oracle documentation on the subject to hand. But might give you a head start.

Oracle 10g physical standby error

Hi all,
We been frequently getting this error on our standby DB and not sure if it's network related or a possible configuration tuning.
RFS[425]: Assigned to RFS process 3640
RFS[425]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[425]: No standby redo logfiles created
Mon Nov 23 09:47:28 2009
Fetching gap sequence in thread 1, gap sequence 35418-35418
Mon Nov 23 09:48:02 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 35418-35418
DBID 3292763437 branch 615642223
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Mon Nov 23 09:48:17 2009
RFS[384]: No standby redo logfiles created
Mon Nov 23 09:48:21 2009
RFS[425]: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 35419
EOF located at block 1201 low SCN 0:-1055223653 next SCN 0:-1055223015
Latent archivelog 'E:\ORACLE\ARCH\xxxxx\LOG_615642223_1_35419.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE 'E:\ORACLE\ARCH\xxxxx\LOG_xxx615642223_1_35419.ARC';
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[426]: Assigned to RFS process 3200
RFS[426]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[426]: No standby redo logfiles created
Any ideas?
thx

I've inherited this DB and never really looked at the settings.
The error I see in the primary DB is
FAL[server]: Fail to queue the whole FAL gap
Protection level on primary is
SQL> SELECT PROTECTION_MODE, PROTECTION_LEVEL FROM V$DATABASE;
PROTECTION_MODE PROTECTION_LEVEL
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
Edited by: jrmtl on Nov 23, 2009 7:32 AM

Recovery very very slow on the physical standby recently

The standby was running fine for over a year. But recently the recovery became very slow. It took over an hour to apply one archivelog causing the standby falling behind. What could be the cause and solution?
Thanks!

Before I go further with my comment, I would recommend to open a SR with Oracle and have them help you to resolve the problem.
You said that the archive logs are being applied, however the apply rate is slow? Is this true?
Since you are applying the archive logs, it looks like your protection mode is set to ASYNC Maximum Performance.
Can you check if all the logs are being shipped to the standby without any problem?
There are couple of DG healthcheck scripts available on Metalink.
Metalink Note 241438.1 Script to Collect Data Guard Physical Standby Diagnostic Information
Metalink Note 241374.1 Script to Collect Data Guard Primary Site Diagnostic Information
Can you run those scripts? If you feel comfortable, publish the output of the scripts on this tread, otherwise review them. They may give you some clue on what might be going on.
Also check v$dataguard_status view.
select *
from v$dataguard_status
where severity in ('Error','Fatal')
order by timestamp; If you are not able to run the scripts due to database hanging state, as you described in your last post, try to determine why the database is hanging.
In this kind of situations I usually use HANGANALYZE that will generate trace files for all the running processes. It may take a while until you review these files. Especially pay attention to the RFS process.
SQL>oradebug setmypid
SQL>oradebug unlimit;
SQL>oradebug hanganalyze 266For more information on how to use HANGANALYZE refer to Metalink Notes: 175006.1, 452358.1 and 61552.1
However, if you haven't used oradebug before or don't feel comfortable using it, you better don't do that and wait on instructions from Oracle.
Also, as always, check the alert log file and the data guard log file (drc<sid>.log).
Cheers,
Edited by: tekicora on Dec 31, 2008 10:22 AM

Cancelling recovery on Physical standby.

Hi ALL,
recovery is cancel and i am looking following error in alert log file
how can solve this problem
database version 11gr2
aix 6.1 64 bit
physical standby datbase
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:27 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:47 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)

ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:27 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:47 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)You cancelled recovery or it is terminated?
Try to start once again, I have seen some listed bugs with the same error but those are applicable for 11gR1, but you are in 11gR2.
Refer ORA-03170: Deadlocked on Readable Physical Standby [ID 846324.1], better you submit an SR to Support.
Thanks.

Physical standby error

Hi friends,
I configured a physical standby database for my primary database. I am able to switchover successfully to physical standby database. So the roles are now changed. Primary is physucal standby, and physical standby is primary.
Now when Iam switching back (now primary to physical standby), there is error at the physical standby which states media recovery needed. I have checked the archives are present at this location. I tried to recover....but thats not working.
Both the databases are 10.2.0.1.0 on windows platform.
Any comments??

Iam sorry for the delay.... here's the alert log
ORA-16139 signalled during: alter database commit to switchover to primary...
Sat Jun 23 14:55:29 2007
alter database commit to switchover to primary
Sat Jun 23 14:55:32 2007
If media recovery active, switchover will wait for completion
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Switchover: Media recovery required - standby not in limbo
ORA-16139 signalled during: alter database commit to switchover to primary...
Sat Jun 23 14:59:26 2007
alter database commit to switchover to primary with session shutdown
Sat Jun 23 14:59:39 2007
If media recovery active, switchover will wait for completion
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Switchover: Media recovery required - standby not in limbo
-Nand

Error, creating physical standby ASM to ASM

Greetings !!!!!!
I am trying to create a single instance physical standby for 2 node RAC. I am getting the following error. The backup of standby controlfile exist and even RMAN can see it. Can someone tell me what I am missing?
Regards
dg01:/u01/app/oracle>rman
Recovery Manager: Release 10.2.0.3.0 - Production on Sun May 11 01:53:39 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target sys/xxxx@RACDB
connected to target database: RACDB (DBID=633531597)
RMAN> connect auxiliary /
connected to auxiliary database: RACDB (not mounted)
RMAN> duplicate target database for standby dorecover;
Starting Duplicate Db at 2008-05-11 01:54:36
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=156 devtype=DISK
contents of Memory Script:
set until scn 8620555;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 2008-05-11 01:54:38
using channel ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/11/2008 01:54:38
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN> list backup of controlfile;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
156 Full 15.11M DISK 00:00:11 2008-05-10 15:47:47
BP Key: 156 Status: AVAILABLE Compressed: NO Tag: TAG20080510T154736
Piece Name: /software/backup/new_db_backup/c-633531597-20080510-09
Control File Included: Ckp SCN: 8620566 Ckp time: 2008-05-10 15:47:36
BS Key Type LV Size Device Type Elapsed Time Completion Time
157 Full 15.08M DISK 00:00:07 2008-05-10 15:48:08
BP Key: 157 Status: AVAILABLE Compressed: NO Tag: TAG20080510T154801
Piece Name: +FLASH/racdb/backupset/2008_05_10/ncnnf0_tag20080510t154801_0.385.654494215
Standby Control File Included: Ckp SCN: 8620602 Ckp time: 2008-05-10 15:48:01
BS Key Type LV Size Device Type Elapsed Time Completion Time
158 Full 15.11M DISK 00:00:11 2008-05-10 15:48:20
BP Key: 158 Status: AVAILABLE Compressed: NO Tag: TAG20080510T154809
Piece Name: /software/backup/new_db_backup/c-633531597-20080510-0a
Control File Included: Ckp SCN: 8620608 Ckp time: 2008-05-10 15:48:09
RMAN>

Check Metalink Note:466321.1
-Amit
http://askoracledba.wordpress.com/

Error while creating physical standby database using Oracle Grid 10.2.0.5

Hi All,
I am setting up data guard using oracle grid.
Primary database version: - 10.2.0.4
Standby database version: - 10.2.0.4
Primary OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
Standby OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
I am creating physical standby database using EM. But it is getting failed with error message in sqlnet.ora file
Fatal NI connect error 12533, connecting to:
(DESCRIPTION=(ADDRESS_LIST=)(CONNECT_DATA=(SERVICE_NAME=INPRDSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=indb50.oii.com)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 10.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 17-AUG-2010 02:40:07
Tracing not turned on.
Tns error struct:
    ns main err code: 12533
    TNS-12533: TNS:illegal ADDRESS parameters
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0As we can see, address_list is empty.
Can anyone suggest what could be the reason behind this?

Dear user13295317,
Here is the error explanation;
Oracle Error :: TNS-12533
TNS:illegal ADDRESS parameters
Cause
An illegal set of protocol adapter parameters was specified.
In some cases, this error is returned when a connection cannot be made to the protocol transport.
Action
Verify that the destination can be reached using the specified protocol.
Check the parameters within the ADDRESS section of TNSNAMES.ORA.
Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform.
Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.Hope That Helps.
Ogan

Getting errors when creating physical standby.

Hello All,
i am getting following error when i creating a physical standby for production,
i used below command to do it
duplicate target database to standby dorecover;
after some time it throwed this error.
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DATA/solfho2/datafile/system.382.764328493'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/12/2011 13:04:06
RMAN-03015: error occurred in stored script Memory Script
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/arch/SOLFHO2/PROLHO01_1_25224_740461103.arc'
ORA-16145: archival for thread# 1 sequence# 25224 in progress

Hello;
Looks like a do over.
I have my short notes here:
http://www.visi.com/~mseberg/duprman2.html
This has been tested several times.
Best Regards
mseberg

Physical Standby - Recovery error

Similar Messages

Maybe you are looking for