Ora-1666 on standby database

Hi All,
I have configured data guard on windows server 2003 platform with primary on 1 server and standby on another server. Oracle is of version 9i with exact release 9.2.0.6.0. I have enabled archived log on primary, modified init file with log_destinations, created password file, created control file and copied all these dbf files, redo log files, archived log files, control file, password files to standby server while the primary db is down. After copying all the required files on standby i tried to mount the standby but getting an error as ORA-01666: controlfile is for a standby database on the standby.
Where as in the primary db alert log file an error is logged as Errors in file d:\oracle\admin\primary\bdump\primary_arc0_4240.trc: ORA-12500: TNS:listener failed to start a dedicated server process but i can do tnsping successfully from primary to standby and vice-versa and on standby ORA-1666 signalled during: ALTER DATABASE MOUNT...
The things I suspect are Standby redo logs, Instance_name. I haven't created any standby logs on primary and i doubt whether it's mandatory to create on primary and standby db's or only in primary db pls let me know, i am confused of the standby logs because of these lines in document +(CREATE STANDBY REDO LOG FILES, IF NECESSARY (PRI+SEC)
In this customer’s case, the customer chose not to use standby redo logs (SRLs), which are not required in Maximum Performance mode. However, if you decide to use SRLs, you would create them on both sites. You cannot create them on the primary database prior to the backup used to create the standby database because the SRLs on the standby must be empty of primary database redo data.)+.
Instance_name parameter: we don't have this parameter in oracle10g where db_name and db_unique_name plays the role. Here in oracle9i is this Instance_name needs to be same on both primary and standby db's (i.e. primary on both db's or primary for primary and standby for standby?)
Earlier i have configured this dataguard setup in solaris platform of oracle version 10g where i have created standby logs on primary db alone and logs are applying on standby and it's working fine.
* please review the below parameters and let me know if i am missing something*
tnsping from primary
C:\Documents and Settings\Administrator>tnsping standby
TNS Ping Utility for 32-bit Windows: Version 9.2.0.6.0 - Production on 25-JAN-20
12 20:15:48
Copyright (c) 1997 Oracle Corporation. All rights reserved.
Used parameter files:
D:\oracle\ora92\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
(HOST = standbyIP )(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = standby)))
OK (110 msec)
tnsping from standby
C:\Documents and Settings\Administrator>tnsping primary
TNS Ping Utility for 32-bit Windows: Version 9.2.0.6.0 - Production on 25-JAN-20
12 20:17:17
Copyright (c) 1997 Oracle Corporation. All rights reserved.
Used parameter files:
D:\oracle\ora92\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
(HOST = primaryIP )(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = primary)))
OK (110 msec)
Primary init file
*.aq_tm_processes=0
*.background_dump_dest='D:\oracle\admin\primary\bdump'
*.compatible='9.2.0.0.0'
*.control_files='D:\oracle\oradata\primary\control01.ctl','D:\oracle\oradata\primary\control02.ctl','D:\oracle\oradata\primary\control03.ctl'
*.core_dump_dest='D:\oracle\admin\primary\cdump'
*.db_block_size=16384
*.db_cache_size=83886080
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_files=96
*.db_name='primary'
*.dg_broker_start=TRUE
*.enqueue_resources=2000
*.fal_client='primary'
*.fal_server='standby'
*.fast_start_mttr_target=300
*.hash_join_enabled=TRUE
*.instance_name='primary'
*.java_pool_size=115343360
*.job_queue_processes=10
*.large_pool_size=0
*.log_archive_dest_1='LOCATION=D:\oracle\archive-logs\primary\archivelog'
*.log_archive_dest_2='SERVICE=standby LGWR ASYNC'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='log_%t_%s.arc'
*.max_enabled_roles=128
*.nls_date_format='DD-MON-RRRR'
*.nls_date_language='AMERICAN'
*.nls_language='AMERICAN'
*.nls_numeric_characters='.,'
*.open_cursors=200
*.optimizer_mode='CHOOSE'
*.os_authent_prefix='OPS$'
*.pga_aggregate_target=25165824
*.processes=150
*.query_rewrite_enabled='FALSE'
*.remote_login_passwordfile='EXCLUSIVE'
*.remote_os_authent=TRUE
*.shared_pool_size=115343360
*.sort_area_size=3000000
*.star_transformation_enabled='FALSE'
*.timed_statistics=TRUE
*.undo_management='AUTO'
*.undo_retention=10800
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='D:\oracle\admin\primary\udump'
*.utl_file_dir='*'
* standby init file*
*.aq_tm_processes=0
*.background_dump_dest='D:\oracle\admin\standby\bdump'
*.compatible='9.2.0.0.0'
*.control_files='D:\oracle\oradata\standby\standby.ctl'
*.core_dump_dest='D:\oracle\admin\standby\cdump'
*.db_block_size=16384
*.db_cache_size=83886080
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_files=96
*.db_name='primary'
*.dg_broker_start=TRUE
*.enqueue_resources=2000
*.fal_client='standby'
*.fal_server='primary'
*.fast_start_mttr_target=300
*.hash_join_enabled=TRUE
*.instance_name='standby'
*.java_pool_size=115343360
*.job_queue_processes=10
*.large_pool_size=0
*.log_archive_dest_1='LOCATION=D:\oracle\archive-logs\standby\archivelog'
*.log_archive_dest_2='SERVICE=primary LGWR ASYNC'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_format='log_%t_%s.arc'
*.max_enabled_roles=128
*.nls_date_format='DD-MON-RRRR'
*.nls_date_language='AMERICAN'
*.nls_language='AMERICAN'
*.nls_numeric_characters='.,'
*.open_cursors=200
*.optimizer_mode='CHOOSE'
*.os_authent_prefix='OPS$'
*.pga_aggregate_target=25165824
*.processes=150
*.query_rewrite_enabled='FALSE'
*.remote_login_passwordfile='EXCLUSIVE'
*.remote_os_authent=TRUE
*.shared_pool_size=115343360
*.sort_area_size=3000000
*.star_transformation_enabled='FALSE'
*.timed_statistics=TRUE
*.undo_management='AUTO'
*.undo_retention=10800
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='D:\oracle\admin\standby\udump'
*.utl_file_dir='*'
Regards
Hari

Primary output
SQL> select error_code,message from v$dataguard_status;
ERROR_CODE
MESSAGE
0
ARC0: Archival started
0
ARC1: Archival started
0
Creating archive destination LOG_ARCHIVE_DEST_2: 'standby'
ERROR_CODE
MESSAGE
12500
LGWR: Error 12500 creating archivelog file 'standby'
0
LGWR: Completed archiving log 3 thread 1 sequence 7
0
ARC0: Evaluating archive log 2 thread 1 sequence 6
ERROR_CODE
MESSAGE
0
ARC0: Beginning to archive log 2 thread 1 sequence 6
0
Creating archive destination LOG_ARCHIVE_DEST_1: 'D:\ORACLE\ARCHIVE-LOGS\primary\A
RCHIVELOG\LOG_1_6.ARC'
0
ARC0: Completed archiving log 2 thread 1 sequence 6
ERROR_CODE
MESSAGE
9 rows selected.
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
THREAD# MAX(SEQUENCE#)
1 6
standby
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
no rows selected
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group
by thread#;
no rows selected
SQL>
trace file:
Dump file d:\oracle\admin\primary\bdump\primary_arc0_4240.trc
Wed Jan 25 19:45:07 2012
ORACLE V9.2.0.6.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Instance name: primary
Redo thread mounted by this instance: 1
Oracle process number: 11
Windows thread id: 4240, image: ORACLE.EXE
*** 2012-01-25 19:45:07.598
*** SESSION ID:(11.1) 2012-01-25 19:45:07.364
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 19:45:07.676
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 19:51:07.987
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 19:51:08.049
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 19:57:08.261
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 19:57:08.355
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 19:59:08.563
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 19:59:08.626
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 20:01:08.820
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 20:01:08.883
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 20:06:09.190
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 20:06:09.253
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 20:12:09.698
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 20:12:09.776
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 20:18:10.069
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 20:18:10.132
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process
*** 2012-01-25 21:02:11.811
Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 12500.
*** 2012-01-25 21:02:11.889
kcrrfail: dest:2 err:12500 force:0
ORA-12500: TNS:listener failed to start a dedicated server process

Similar Messages

ORA-16821: logical standby database dictionary not yet loaded

Dear all,
I have a dataguard architecture with a primary and a standby database (for reporting stuffs). Since I upgraded physical standby to logical standby, I receive this error !
ORA-16821: logical standby database dictionary not yet loaded
If someone has an idea, should be great !!
Thanks
oldschool

Hi,
Ok I applied :
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> alter database start logical standby apply immediate;
Database altered.
SQL>
And now I received this :
ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
What does it mean to check the status report.....
I found this about monitorable status report !!
DGMGRL> show database 'M3RPT' 'StatusReport';
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16821: logical standby database dictionary not yet loaded
DGMGRL>
What can I do ?
Thanks a lot
oldschool
Edited by: oldschool on Jun 4, 2009 2:37 AM

ORA-01578 about standby database in read only mode

Hi,
I have an ORA-05178 (data block corrupted) about a standby database which in read-only mode. About production database, there is no problem.
After analyze, this is an index segment :
SELECT segment_name , segment_type , owner , tablespace_name
FROM sys.dba_extents
WHERE file_id = 58
AND 218173 BETWEEN block_id and block_id + blocks -1
SEGMENT_NAME SEGMENT_TYPE OWNER TABLESPACE_NAME
SICINHIS01 INDEX MOWIN IDX_DATA01
There is no constraint.
How can I repair this problem ?
Nicolas

Hi,
I have an ORA-05178 (data block corrupted) about a standby database which in read-only mode. About production database, there is no problem.
After analyze, this is an index segment :
SELECT segment_name , segment_type , owner , tablespace_name
FROM sys.dba_extents
WHERE file_id = 58
AND 218173 BETWEEN block_id and block_id + blocks -1
SEGMENT_NAME SEGMENT_TYPE OWNER TABLESPACE_NAME
SICINHIS01 INDEX MOWIN IDX_DATA01
There is no constraint.
How can I repair this problem ?
Nicolas

How to clear Error alerts ORA-01219 on standby databases

Hello all
I'm using EM 10.1.0.5. Some weeks ago, we did an upgrade of our standby databases to 10.2.0.4. At that moment, we got many alerts of type Error: ORA-0219: database not open, queries allowed on fixed tables/views only. That's right, these databases are not open. Now I'm getting tired of seeing these 130 messages every day, I would like to delete them. But I cannot ! I removed several alerts of type Warning by setting the threshold value of the metric to NULL and then back again. This works fine. But I cannot use the same procedure for Error alerts, because I do not find these metrics. Example: the metric Streams Capture Message Statistics is displayed on the All Metrics page, but NOT on the Metric and Policy Settings page (selecting All Metrics in the drop down list). Apart from upgrading the EM to 10.2.0.4, is there a way to remove these Error alerts ?
Thank you for any advice
pher

I have checked my 10.2.0.4 OMS and the "Streams Capture Message Statistics" metrics are not displayed on the Metric and Policy Settings page either. This looks like it could be a bug. You might bnefit from raising an SR with Oracle support. In the meantime I will continue to seek a resolution.

Ora-38500 physical standby database not started

hiiii,
When i executed the command at physical standby database server.
it give error:
To start real-time apply:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
Error at line 1:
ORA: 38500 using current logfile option not available without stand.
please help me how could i start physical standby database
Regards
Vaibhav Dixit

Hi Vaibhav,
What exactly do you want to do?
Alter database recover managed standby database; --->it will be in Manged Recovery mode.
Alter database mount standby database; ----> it will be mounted, but no log files applies.
Alter database open read only; ----> it will be open with read only option, but archeive logs will NOT be applied
If you want to apply the Archive logs which are trasfered from Primary, then you need to fire the below commands
Alter database recover managed standby database;
Alter database recover managed standby database using current logfile;
Alter database recover managed standby database using current logfile disconnect from session;
To stop applying archives then,
Alter database recover managed standby database cancel;
Thanks and Regards.
tnaresh1982

Logical standby database keeps displaying ORA-16768

I have a logical standby database setup on a remote host to accept cascaded logs from a physical standby. Everything was working fine until yesterday when I get the above error and log apply services stopped. When I go into Grid Control to Data Guard I see the error and it displays the failed SQL statement which is a create index statement. I have the option of clicking the SKIP button. When I click SKIP it appears to have processed it as the error goes away but then a few minutes later the error comes back, log apply stops and the failed SQL statement is the same create index statement. I guess the Skip doesn't mean Skip, it means Retry... My question is how do I get past this? Logs have been piling up.

Hi,
Ok I applied :
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> alter database start logical standby apply immediate;
Database altered.
SQL>
And now I received this :
ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
What does it mean to check the status report.....
I found this about monitorable status report !!
DGMGRL> show database 'M3RPT' 'StatusReport';
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16821: logical standby database dictionary not yet loaded
DGMGRL>
What can I do ?
Thanks a lot
oldschool
Edited by: oldschool on Jun 4, 2009 2:37 AM

Data Guard Broker connecting to standby database fails

Hello everybody
I checked lots of pages but I'm not able to find a solution für my problem. I already set up a primary and a standby database (prim = ALPHA1 / standby = ALPHA2).
After enabling my dgmgrl configuration I got two errors:
DGM-17016: failed to retrieve status for database "alpha2"
ORA-16664: unable to receive the result from a database
The dg log from ALPHA1 says:
06/04/2013 16:06:57
Site alpha2 returned ORA-16664.
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration alphadgb Warning ORA-16607
Primary Database alpha1 Success ORA-00000
Physical Standby Database alpha2 Error ORA-16664
While the dg log from ALPHA2 (standby) says:
06/04/2013 16:43:28
SPFILE is missing value for property 'LogArchiveFormat' with sid='ALPHA2'
Warning: Property 'LogArchiveFormat' has inconsistent values:METADATA='arch_ALPHA2_%S_%t_%r.arc', SPFILE='(missing)', DATABASE='arch_ALPHA2_%S_%t_%r.arc'
Failed to connect to remote database alpha1. Error is ORA-12514
Failed to send message to site alpha1. Error code is ORA-12514.
How can I solve this issue? Every type of tnsping is successfull. The sqlplus login from the primary to the standby database works, the other way round works too! Therefore the tnsnames and listener data seems to be correct.
My configuration for ALPHA1 (primary db):
Listener
LISTENER_ALPHA1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
SID_LIST_LISTENER_ALPHA1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = ALPHA1_DGMGRL)
(ORACLE_HOME = /oracle/ALPHA1/orahome)
(SID_NAME = ALPHA1)
tnsnames.ora
ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SID = ALPHA1)
ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SID = ALPHA2)
DG_ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA1_DGMGRL)
DG_ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA2_DGMGRL)
Parameters
archive_lag_target integer 0
log_archive_config string DG_CONFIG=(ALPHA2,ALPHA1)
log_archive_dest string
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles) DB_UNIQUE_NAME=ALPHA2
log_archive_dest_2 string SERVICE=ALPHA1 SYNC valid_for=(online_logfiles,primary_role) DB_UNIQUE_NAME=ALPHA1
log_archive_format string arch_ALPHA2_%S_%t_%r.arc
log_archive_local_first boolean TRUE
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
standby_archive_dest string ?/dbs/arch
For the DG Broker configuration
DGMGRL>     connect sys/dgalpha42@DG_ALPHA1
DGMGRL>     create configuration ALPHADGB
DGMGRL>     primary database is ALPHA1
DGMGRL>     connect identifier is DG_ALPHA1
DGMGRL>     ;
DGMGRL>     add database ALPHA2
DGMGRL>     connect identifier is DG_ALPHA2
DGMGRL>     maintained as physical
DGMGRL>     ;
There were no errors.
DGMGRL> show database verbose ALPHA1
Database - alpha1
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose ALPHA2
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'SYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DGM-17016: failed to retrieve status for database "alpha2"
ORA-16664: unable to receive the result from a database
Can anybody help me to find a solution for this?

Hey
thanks for the answer. I followed you recommendations but I got the same error again. I restored/recovered the old status and looked deeper into the dgmgrl configuration before enabling. I found an interesting point. (show database verbose ALPHAx)
Database - alpha1
Role: PRIMARY
Intended State: OFFLINE
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: OFFLINE
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
As the listener are configured ALPHA1 (prim) should be on port 1521 while ALPHA2 (stby) should work on 1522. In the configuration of DGMGRL only appears port 1521 (look at StaticConnectIdentifier). Is this maybe the reason of the networking problems with DG Broker? How can I fix this?
Regards Mirko
Edited by: 1009733 on 04.06.2013 09:22

Redo log files are not applying to standby database

Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar Lapani

Thank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks

ORA-600 in standby alert log

We have recently migrated our database from Solaris to Linux (RHEL5) and since this migration we are seeing weird errors related to archive log shipping to the remote standby site and a corresponding ORA-600 in the standby site.
What's interesting is everything gets resolved by itself, it always seems to happen during the heavy database load when there is frequent log switch happening (~3 min). So initially it tries to archive to the remote site and it fails with the following error in the primary alert log.
Errors in file /app/oracle/admin/UIIP01/bdump/uiip01_arc1_9772.trc:
ORA-00272: error writing archive log
Mon Jul 14 10:57:36 2008
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Jul 14 10:57:36 2008
Errors in file /app/oracle/admin/UIIP01/bdump/uiip01_arc1_9772.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Jul 14 10:57:36 2008
ORACLE Instance UIIP01 - Archival Error. Archiver continuing.
And then we see a ORA-600 on standby database related to this which complains about redo block corruption.
Mon Jul 14 09:57:32 2008
Errors in file /app/oracle/admin/UIIP01/udump/uiip01_rfs_12775.trc:
ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
Mon Jul 14 09:57:36 2008
And the trace file has this wonderful block corruption error..
Corrupt redo block 424432 detected: bad checksum
Flag: 0x1 Format: 0x22 Block: 0x000679f0 Seq: 0x000006ef Beg: 0x150 Cks:0xa2e5
----- Dump of Corrupt Redo Buffer -----
*** 2008-07-14 09:57:32.550
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
So ARC tries to resend this redo log again and it succeeds, end of the day all we have is a bunch of these ORA- errors in our alert logs, triggering off our monitors and these errors resolve themselves without any manual intervention, opened a tar with Oracle support as this is not affecting our primary database, they are in no hurry to get this one prioritized and also they are reluctant to accept that it's a bug that resolves itself.
Just wanted to get it out here to see if anyone experienced a similar problem, let me know if you need any more details.
As I said earlier this behaviour happens only during peak loads espceially when we have full 500M redo logs that are being archived.
Thanks in Advance.

Thanks Madrid!..
I scoured thru these metalink notes before looking for possible solutions and almost all of them were closed citing a customer problem related to OS, firewall, network, etc or some were closed saying requested data not provided.
Looks as if they were never successfully closed with a resolution.
I just want to assure myself that the redo corruption that standby is reporting will not haunt me later, when I am doing a recovery or even a crash recovery using redo logs?..
I have multiplexed my logs, just in case and have all the block checking parameters enabled on both primary and standby databases.
Thanks,
Ramki

[b]STANDBY DATABASE[/b]

DEAR PARTICIPANTS
I am creating a standby database and it works on the same computer in different location.
but when created control file with
ALTER DATABASE CREATE STANDBY CONTROLFILE AS '\\TCP/IP\\LOCATION';
IT SAYS CANNOT CREATE FILE (SKGCRFRE)AND CANNOT OPEN FILE
AND (OS5) ACCESS DENIED.
CAN YOU HELP ME OUT ON THIS PROBLEM WHICH MAY BE WINDOWS
ERROR. I HAVE GIVEN ALL PERMISSIONS TO USER WHICH IS A ADMINISTRATOR ON WINDOWS ON BOTH THE COMPUTERS.
PLEASE reply on this site or on my email address
[email protected]

hi..
SOLUTION:
1.Startup the database using:
STARTUP PFILE=C:\Oracle\Admin\SID\PFile\init.ora
2.Create standby database controlfile using:
ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'c:\stbycf.f';
(If u r Creating on the Same System..ok)

Getting errors while creating a Standby database

Hi,
I have Oracle 9.0.2 installed on windows xp machine , the sid of the database is oradata. Now i am trying to create a standby database on same machine and the sid of the database is oratest. i have followed the required steps.
a. Firstly i have configured the required parameters in the init.ora parameters of standby database
b. Secondly , i created the standby control file on primary database.
c. while mounting the standby database i am getting the following error.
Database name "ORADATA" its should be "ORATEST"
Could you please help me in resolving this issue? and also if possible. please jot down the procedure for creating the standby database.
Thanks
Vj0011590

Hi,
I have Oracle 9.0.2 installed on windows xp machine ,
the sid of the database is oradata. Now i am trying
to create a standby database on same machine and the
sid of the database is oratest. i have followed the
required steps.
a. Firstly i have configured the required parameters
in the init.ora parameters of standby database
b. Secondly , i created the standby control file on
primary database.
c. while mounting the standby database i am getting
the following error.
Database name "ORADATA" its should be "ORATEST"I didn't see you copy the cold backup db from primary to standby.
and the error is coming from init.ora in your standby db. check it again.

How standby database works

Hi!!
I have created standby database (testcat) for primary database (test) using Duplicate Command of RMAN on same server (windows XP) on Oracle 11.2 . I know how to create standby database But i don't know how and when standby database works. I checked init.ora file of standby database it contains all parameters prefixed with *. as follow
*.db_create_file_dest='F:\app\Administrator\oradata'
*.db_domain=''
*.db_recovery_file_dest='F:\app\Administrator\flash_recovery_area'
*.db_recovery_file_dest_size=10737418240
*.db_unique_name='testcat'
*.DB_NAME='test'
*.control_files="D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘'
While init.ora file of primary database contains entries like
db_create_file_dest=F:\app\Administrator\oradata
db_recovery_file_dest=F:\app\Administrator\flash_recovery_area
db_recovery_file_dest_size=4039114752
control_files="F:\APP\ADMINISTRATOR\ORADATA\TEST\CONTROLFILE\O1_MF_8TXW6QN0_.CTL"
So I want to know is
          1. IS there any difference between parameter that start with .* and start without .*
          2. Can i set db_create_file_dest parameter in init.ora of standby database to another location.
           3. How redo log will be applied to standby database when I run ALTER DATABASE RECOVER ..... command
          4. where archived log files of standby database will stored?

1. Fetch Archive Log (FAL) Client :- It requests for archived redo log files from the primary site.
That means FAL Client is required (should exist) on standby database server. Am i right here?
FAL Client is Standby database, FAL Client requre archived log from FAL Server (primary, Cascading standby database ) for Gap Resolution.
2. Fetch Archive Log (FAL) Server:- It requests for archive redo logs from FAL Client (Standby database).That means FAL Server is required (should exist) on primary database server.
If yes then, why it is required because FAL Server request for archived redo logs from standby database while on other side standby database can not have redo logs as it runs in READ ONLY Access mode (So no DML and DDL) ?.
Also primary database will be always one step ahead in terms of archive logs than standby database and hence there is no need to request for archived logs from stanby. Am i right here?
Yes you are right. Primary is newer require archived log from standby. You asked and answered.
Regards
Mahir M. Quluzade

ORA-279 signalled during recovery of standby database

Hi All,
I am preparing standby database after taking hot backup and copying those datafiles to standby,
taken controlfile standby controlfile backup from primary
mounted the standby database using standby controlfile using
startup nomount pfile='/u01/stand.ora'
alter database mount standby database;
Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
recover standby database;
But I am getting the below warning on the recovery screen...
ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
ORA-00280: change 51667629050 for thread 1 is in sequence #55118
ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
ORA-00280: change 51667703096 for thread 1 is in sequence #55119
ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
ORA-00280: change 51667767649 for thread 1 is in sequence #55120
ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
ORA-00280: change 51667831821 for thread 1 is in sequence #55121
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
needed for this recovery
and I am getting the below warning on the alert log..........
Sun Jul 5 18:37:36 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:37:36 2009
Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
Sun Jul 5 18:40:31 2009
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Sun Jul 5 18:40:31 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:40:31 2009
Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
Please suggest what to do now.............
Thanks in Advance,
Sukanta Paul.

Hi Sukanta,
I didn't really understand what the problem is...
Let me explain, hope it will be clear.
You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
The messages you see say the following:
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

ORA-10458: standby database requires recovery

hi
kindly help me... i got error when standby open in read only mode
SQL*Plus: Release 11.2.0.3.0 Production on Sat Jan 19 14:37:46 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 5344731136 bytes
Fixed Size 2237776 bytes
Variable Size 1275071152 bytes
Database Buffers 4060086272 bytes
Redo Buffers 7335936 bytes
Database mounted.
SQL> Alter Database Recover Managed Standby Database Disconnect;
Database altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ ONLY
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'

hi CKPT
I executed the action plan as you recommend and got below information;
SQL> recover standby database;
ORA-00279: change 5983485554580 generated at 01/01/2013 19:27:17 needed for
thread 1
ORA-00289: suggestion : /archive/PROD_1_750568044_45027.ARC
ORA-00280: change 5983485554580 for thread 1 is in sequence #45027
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'/archive/PROD_1_750568044_45400.ARC'
ORA-00310: archived log contains sequence 45400; sequence 45027 required
ORA-00334: archived log: '/archive/PROD_1_750568044_45400.ARC'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01666: control file is for a standby database
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
---------------------------------- and some other activity but still not found any solution-------------
RMAN> recover database until sequence
2> 45026;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:47
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484595990
RMAN> recover database until sequence 45027;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:59
RMAN-06556: datafile 22 must be restored from backup older than SCN 5983485554580
RMAN> recover database until sequence 45025;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:43:09
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484160276
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 01/23/2013 16:43:25
ORA-01666: control file is for a standby database

Ora 00364,ora 00305 ora 00312 errors in standby database

hii friends i got a problem in my standby database yesterday i performed database restoration activity, restoration is done and database is in MRM modemout stage, archive gap sequence is completed and is in synchronize with primary but suddenly after some time i got in alertlog media recovery waiting for thread one and from there its is showing nothing in alert log after stoping mrm and restarting database i got few errors please check them and suggest me some solution
alert log file
RFS[87]: Assigned to RFS process 7912
RFS[87]: Identified database type as 'physical standby'
Tue Jan 4 17:12:14 2011
RFS[87]: Archived Log: '/backup/standby_archivelogs/1_87532_622555682.dbf'
Tue Jan 4 17:12:17 2011
Media Recovery Log /backup/standby_archivelogs/1_87532_622555682.dbf
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:55:35 2011
alter database recover managed standby database cancel
Tue Jan 4 17:55:38 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:55:38 2011
Errors in file /oracle/app/oracle/admin/****/bdump/*******mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:55:39 2011
Waiting for MRP0 pid 3017 to terminate
Tue Jan 4 17:55:39 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:55:39 2011
MRP0: Background Media Recovery process shutdown (****)
Tue Jan 4 17:55:40 2011
Managed Standby Recovery Canceled (****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:55:56 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:55:56 2011
Attempt to start background Managed Standby Recovery process (****)
MRP0 started with pid=16, OS id=9300
Tue Jan 4 17:55:56 2011
MRP0: Background Managed Standby Recovery process started (****)
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp09300.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:56:02 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:57:56 2011
alter database recover managed standby database cancel
Tue Jan 4 17:57:56 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:57:56 2011
Errors in file /oracle/app/oracle/admin/APMBDRDB/bdump/apmbdrdb_mrp0_9300.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:57:57 2011
Waiting for MRP0 pid 9300 to terminate
Tue Jan 4 17:57:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:57:57 2011
MRP0: Background Media Recovery process shutdown (*****)
Tue Jan 4 17:57:58 2011
Managed Standby Recovery Canceled (*****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:58:10 2011
Shutting down instance: further logons disabled
Tue Jan 4 17:58:10 2011
Stopping background process CJQ0
Tue Jan 4 17:58:10 2011
Stopping background process MMNL
Tue Jan 4 17:58:11 2011
Stopping background process MMON
Tue Jan 4 17:58:12 2011
Shutting down instance (immediate)
License high water mark = 3
Tue Jan 4 17:58:12 2011
Stopping Job queue slave processes
Tue Jan 4 17:58:12 2011
Job queue slave processes stopped
Tue Jan 4 17:58:12 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Tue Jan 4 17:58:12 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Tue Jan 4 17:58:17 2011
ARCH shutting down
ARC1: Archival stopped
Tue Jan 4 17:58:22 2011
ARCH shutting down
ARC0: Archival stopped
Tue Jan 4 17:58:24 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Jan 4 17:58:33 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =242
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 2000
sga_max_size = 3221225472
__shared_pool_size = 1006632960
shared_pool_size = 637534208
__large_pool_size = 503316480
large_pool_size = 503316480
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 3221225472
control_files = /dev/vg01/rCTRLR1, /dev/vg01/rCTRLR2, /dev/vg01/rCTRLR3
db_block_size = 8192
__db_cache_size = 1677721600
db_cache_size = 637534208
compatible = 10.2.0.1.0
log_archive_config = DG_CONFIG=(APMBPROD,APMBDRDB)
log_archive_dest_1 = LOCATION=/archive/archivelogs/ valid_for=(ONLINE_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=APMBDRDB
log_archive_dest_2 =
log_archive_dest_4 = service=APMBPROD LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=APMBPROD
log_archive_max_processes= 2
standby_archive_dest = /backup/standby_archivelogs
fal_client = APMBDRDB
fal_server = APMBPROD
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
job_queue_processes = 10
background_dump_dest = /oracle/app/oracle/admin/APMBDRDB/bdump
user_dump_dest = /oracle/app/oracle/admin/APMBDRDB/udump
core_dump_dest = /oracle/app/oracle/admin/APMBDRDB/cdump
audit_file_dest = /oracle/app/oracle/admin/APMBDRDB/adump
db_name = APMBPROD
db_unique_name = APMBDRDB
open_cursors = 300
pga_aggregate_target = 1703936000
PMON started with pid=2, OS id=9371
PSP0 started with pid=3, OS id=9373
MMAN started with pid=4, OS id=9375
DBW0 started with pid=5, OS id=9377
LGWR started with pid=6, OS id=9380
CKPT started with pid=7, OS id=9382
SMON started with pid=8, OS id=9384
RECO started with pid=9, OS id=9386
CJQ0 started with pid=10, OS id=9388
MMON started with pid=11, OS id=9390
MMNL started with pid=12, OS id=9392
Tue Jan 4 17:58:35 2011
ALTER DATABASE MOUNT
Tue Jan 4 17:58:39 2011
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=9395
Tue Jan 4 17:58:39 2011
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Tue Jan 4 17:58:39 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
ARC1 started with pid=15, OS id=9397
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Tue Jan 4 17:58:39 2011
Successful mount of redo thread 1, with mount id 3471861451
Tue Jan 4 17:58:39 2011
Physical Standby Database mounted.
Completed: ALTER DATABASE MOUNT
Tue Jan 4 17:58:51 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:58:51 2011
Attempt to start background Managed Standby Recovery process ()
MRP0 started with pid=16, OS id=9400
Tue Jan 4 17:58:51 2011
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:58:57 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 19:37:24 2011
alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:24 2011
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
Completed: alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:27 2011
Media Recovery Log /backup/standby_archivelogs/1_87533_622555682.dbf
Tue Jan 4 19:37:43 2011
Media Recovery Waiting for thread 1 sequence 87534
from here it is showing no errors or nothing in my alert log file from yesterday evening

No version number, no definition of what you mean by "standby database" and not a clue as to what you mean by "restore" or why you did it.
No help is possible at this time.
PS: We do not guess at what someone means by "MRM modemout stage" ... you need to define your terms.

Ora-1666 on standby database

Similar Messages

Maybe you are looking for