ORA-16831: operation disallowed on this standby database type

Om my primary database, i am getting this error when i give ADD database command. How i can resolve. The difference between primary & secondary is that primary is 64bit OS and secondary is 32bit OS. Both have 12gr2 and linux.
DGMGRL> ADD DATABASE tbdb AS CONNECT IDENTIFIER IS tbdb MAINTAINED AS PHYSICAL;
Error: ORA-16831: operation disallowed on this standby database type

It's supported till 10g. But data guard broker is not supported if you use different binaries. See support note 414043.1
Also http://emrebaransel.blogspot.com/2010/12/dataguard-on-different-operating.html

Similar Messages

ORA-01666: controlfile is for a standby database - My DB Doesn't OPEN

dear Gurus,
I've created a Standby, and Configured the Dataguard no issues.
I've start a swtchover into Site 2
After half an Hour without responding I cancle the operation.
Now I'm facing this Situation, My Standby Site still Ok but my Prod Database shows ORA-01666: controlfile is for a standby database
What shall i do?
When I check the Config in the Dataguard Broker everything seems ok for SITE 2
DGMGRL> show site verbose 'CFMP_SITE2';
Site
Name: 'CFMP_SITE2'
Hostname: 'srvsdmwebp02'
Instance name: 'CFMP'
Service Name: 'CFMP_SITE2'
Standby Type: 'physical'
Number Built-in Processes: '2'
Number Generic Processes: '0'
Enabled: 'yes'
Required: 'yes'
Default state: 'STANDBY'
Intended state: 'STANDBY'
PFILE: ''
Number of resources: 1
Resources:
Name: CFMP_SITE2 (default) (verbose name='CFMP_SITE2')
Current status for "CFMP_SITE2":
SUCCESS
DGMGRL>
But in Site 1 it's different
DGMGRL>
DGMGRL> show site verbose 'CFMP_SITE1';
Site
Name: 'CFMP_SITE1'
Hostname: 'srvsdmwebp01'
Instance name: 'CFMP'
Service Name: 'CFMP_RW.world'
Standby Type: 'physical'
Number Built-in Processes: '2'
Number Generic Processes: '0'
Enabled: 'yes'
Required: 'yes'
Default state: 'PRIMARY'
Intended state: 'PRIMARY'
PFILE: ''
Number of resources: 1
Resources:
Name: CFMP_SITE1 (default) (verbose name='CFMP_SITE1')
Current status for "CFMP_SITE1":
Warning: ORA-16609: one or more resources have failed
How shall I proceed ?
Thxs

Dear Gurus,
Thxs for all your replys,
You really help Me, anyhow, now i could Start at Least one database, the Secondary SITE is Up and running
But when I check the Dataguard Broker I get
DGMGRL> show resource verbose 'CFMP_SITE2';
Resource
Name: CFMP_SITE2
Manager Type: internal
Standby Type: PHYSICAL
Online States:
ONLINE
PHYSICAL-APPLY-READY
PHYSICAL-APPLY-ON
READ-ONLY
LOGICAL-APPLY-READY
LOGICAL-APPLY-ON
READ-WRITE
READ-WRITE-XPTON
Properties:
INTENDED_STATE = 'PHYSICAL-APPLY-ON'
ENABLED = 'yes'
IGNORE_STATUS = 'no'
LogXptMode = 'ASYNC'
Dependency = ''
Alternate = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
ReopenSecs = '300'
AsyncBlocks = '16384'
LogShipping = 'ON'
ApplyNext = '0'
ApplyNoDelay = 'NO'
ApplyParallel = '1'
StandbyArchiveDest = '/u03/archive/CFMP'
LogArchiveTrace = '0'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '1800'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ' , '
LogFileNameConvert = ' , '
LogArchiveFormat = 'CFMP_%s.arc'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
SbyLogQueue = '(monitor)'
Properties for 'PRIMARY' state:
DEFAULT_STATE = 'READ-WRITE-XPTON'
EXPLICIT_DISABLE = 'no'
REQUIRED = 'yes'
Properties for 'STANDBY' state:
DEFAULT_STATE = 'PHYSICAL-APPLY-ON'
EXPLICIT_DISABLE = 'no'
REQUIRED = 'yes'
Current status for "CFMP_SITE2":
Error: ORA-16762: Invalid database state
I don't get ???? Can we really seriouslly trust this DATAGUARD stuff ????

ORA-00230: operation disallowed: snapshot control file enqueue unavailable

Hi,
on 10g R2, on Win 2003
my rman backup failed (just at the end) with :
release channel 000
ORA-00230: operation disallowed: snapshot control file enqueue unavailable1-should I rerun the back up task ?
2-how to verify if this backup is correct/good ?
PS : I use nocatalog (controlfile for repository)
Thank you.

1-should I rerun the back up task ?appear its failed during controlfile backup if database backup log fine than just take controlfile backup.
2-how to verify if this backup is correct/good ?in 10g ,we can see status in v$rman_status view,it also show any other running job as well.
select * from (select SID ,recid ,STATUS,operation,MBYTES_PROCESSED/1024 "GB",START_TIME,END_TIME from v$rman_status order by start_time desc) where rownum <11

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-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

Standby database 10.2

HI , I have problem with my standby database, all parameters are good work but in my alert log file have following error;
ORA-16401: archivelog rejected by RFS, pls help me what the problem???
On Primary: spfileORCL.ora
*.control_files='/u01/oracle/oradata/orcl/control01.ctl','/u01/oracle/oradata/orcl/control02.ctl','/u01/oracle/oradata/orcl/control03.ctl'
*.db_recovery_file_dest='/u01/oracle/flash_recovery_area'
*.db_unique_name='BAKI'
*.remote_login_passwordfile='EXCLUSIVE'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(BAKI,LONDON)'
*.LOG_ARCHIVE_DEST_1='LOCATION=/u02 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=BAKI'
*.LOG_ARCHIVE_DEST_2='SERVICE=LONDON LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=LONDON'
*.LOG_ARCHIVE_DEST_STATE_1=enable
*.LOG_ARCHIVE_DEST_STATE_2=enable
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.FAL_SERVER=LONDON
*.FAL_CLIENT=BAKI
*.STANDBY_FILE_MANAGEMENT=AUTO
*.SERVICE_NAMES=BAKI
ON my standby database spfileORCL.ora
*.control_files='/u01/oracle/oradata/orcl/stanctl.ctl'
*.db_recovery_file_dest='/u01/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.remote_login_passwordfile='EXCLUSIVE'
*.db_unique_name='LONDON'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(BAKI,LONDON)'
*.LOG_ARCHIVE_DEST_1='LOCATION=/u02 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=BAKI'
*.LOG_ARCHIVE_DEST_2='SERVICE=BAKI LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=BAKI'
*.LOG_ARCHIVE_DEST_STATE_1=enable
*.LOG_ARCHIVE_DEST_STATE_2=enable
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.FAL_SERVER=BAKI
*.FAL_CLIENT=LONDON
*.STANDBY_FILE_MANAGEMENT=AUTO
*.SERVICE_NAMES=LONDON
all connections work well:
SQL> conn sys/sys@BAKI as sysdba
Connected.
SQL>
SQL> conn sys/sys@LONDON as sysdba
Connected.
SQL>
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
OS: SUSE 10

Primary :
alert_log:
Errors in file /u01/oracle/admin/orcl/bdump/orcl_arc0_8465.trc:
ORA-16401: archivelog rejected by RFS
orcl_arc0_8465.trc:
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: work to do 0x2 (end)
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
*** 2009-09-08 12:32:06.342
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0xa)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0xa)
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x2)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x2)
kcrrwkx: work to do 0x2 (end)
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: work to do 0x2 (end)
Error 16401 creating standby archive log file at host 'LONDON'
ORA-16401: archivelog rejected by RFS
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
kcrrwkx: nothing to do (end)
Standby:
alert_log
Tue Sep 8 12:19:28 2009
Errors in file /u01/oracle/admin/orcl/udump/orcl_rfs_5463.trc:
ORA-16401: archivelog rejected by RFS
RFS[4]: Archivelog thread 1 sequence 7 cannot be reused
Tue Sep 8 12:19:28 2009
Errors in file /u01/oracle/admin/orcl/udump/orcl_rfs_5463.trc:
ORA-16401: archivelog rejected by RFS
Tue Sep 8 12:19:31 2009
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 6 (4)
orcl_rfs_5463.trc:
ORA-16401: archivelog rejected by RFS
*** 2009-09-08 12:20:28.159
KCRRFLAS
KCRRSNPS
*** 2009-09-08 12:20:28.162 60679 kcrr.c
RFS[4]: Archivelog thread 1 sequence 6 cannot be reused
This problem can occur as the result of multiple primary and/or
standby database(s) trying to archive to this standby database.
This is not allowed, since successfully completed archivelogs
would be overwritten.
ORA-16401: archivelog rejected by RFS
*** 2009-09-08 12:20:28.165 60679 kcrr.c
RFS[4]: Archivelog thread 1 sequence 7 cannot be reused
This problem can occur as the result of multiple primary and/or
standby database(s) trying to archive to this standby database.
This is not allowed, since successfully completed archivelogs
would be overwritten.
ORA-16401: archivelog rejected by RFS

Configuring DG's Standby database in 10g Grid Control monitoring.

Hi.
I am facing issues to configure "for monitoring" the standby instance of a 10g database. If someone on this forum have experience, please share, will be greatly appreciated.
Thanks
/SKH

FYI we have a tar open on this "standby databases not monitored correctly" ie grid is trying to collect metric from a sb db when it can not b/c its only mounted. The fix will be in 10.2.0.4. We are pushing for a back port to 10.2.0.3 b/c we missed a corruption in our sb db b/c we could not monitor the values and apply different templates.

GG on Physical Standby database

Hi All,
Could anyone please let me know whether we can create extract of physical standby database Archive logs? This is oracle 9i physical standby database and I want to configure the primary extracts on standby database instead of primary production database. Also please consider that this standby database is always in recovery mode in mount stage. Is this possible?
Thanks in Advance.
Raghav

Run a test by creating an extract that creates an ASCII file. It's simple, you don't need to have a replicat or data pump. If you can read the ORLs of the standby, you'll pick up the statements from the redo apply. The problem, though, is that the physical standby is mounted, so any connections/queries requiring access to fixed tables is going to fail. Also, what DBLOGIN can be used to add trandata for a table?

Add standby database to crs?

Hi,
I have te latest Oracle version 11.2.0.3.0.
I've created a physical standby database with OEM, when I reboot the servers the primary goes down and up automaticly, but the standby doesn't... I have to start this one up manually.
How can I add this standby database to the Oracle High availability Services to auto stop and start ?
BR
Mark

Hi,
Use the srvctl add database command with the following syntax:
srvctl add database -d db_unique_name -o oracle_home [-m domain_name]
[-n db_name] [-p spfile] [-s start_options] [-t stop_options]
[-r {PRIMARY | PHYSICAL_STANDBY | LOGICAL_STANDBY | SNAPSHOT_STANDBY}]
[-y {automatic | manual}] [-a disk_group_list]HTH,
Levi Pereira

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-01403: no data found on LOGICAL STANDBY database

Hi ,
Logical Standby issue :
Oracle 10.2.0.2 enterprise edition .
M Working on LOGICAL Standby since 1 yrs but still i havent got this ......................................
I m getting countinuously no data foud errror on logical standby database .
I found the table causing the proble(db_logstdby_events) and skipped that table and instanciated table using bwlow package:
exec dbms_logstdby.instantiate_table (.......................................
but when i start apply process on logical standby it again give no data found for new table :
Even i tried to instantiate the table using EXPORT/IMPORT during down time but the same facing same problem .
As much as i known abt the error that is :
table1
id
10
20
30
Now if sql apply process on logical standby tries to performe the update transaction(for example) as belows
update table1 set id=100 where id=50;
above query will not be completed cos it will never find the values 50 which is not in table .Thts why this error comming ..
Now my worry is ... no users dare to change/make such changes on Logical standby .So if there is no changes in tables then sqll apply should get all the values to be needded for an update ......
watingggg guyssss/......

Troubleshooting ORA-1403 errors with Flashback Transaction
In the event that the SQL Apply engine errors out with an ORA-1403, it may be possible to utilize flashback transaction on the standby database to reconstruct the missing data. This is reliant upon the undo_retention parameter specified on the standby database instance.
ORA-1403: No Data Found
Under normal circumstances the ORA-1403 error should not be seen in a Logical Standby environment. The error occurs when data in a SQL Apply managed table is modified directly on the standby database, and then the same data is modified on the primary database.
When the modified data is updated on the primary database and received by the SQL Apply engine, the SQL Apply engine verifies the original version of the data is present on the standby database before updating the record. When this verification fails, an ORA-1403: No Data Found error is thrown by Oracle Data Guard: SQL Apply.
The initial error
When the SQL Apply engine verification fails, the error thrown by the SQL Apply engine is reported in the alert log of the logical standby database as well as a record being inserted into the DBA_LOGSTDBY_EVENTS view. The information in the alert log is truncated, while the error is reported in it's entirety in the database view.
LOGSTDBY stmt: update "SCOTT"."MASTER"
set
"NAME" = 'john'
where
"PK" = 1 and
"NAME" = 'andrew' and
ROWID = 'AAAAAAAAEAAAAAPAAA'
LOGSTDBY status: ORA-01403: no data found
LOGSTDBY PID 1006, oracle@staco03 (P004)
LOGSTDBY XID 0x0006.00e.00000417, Thread 1, RBA 0x02dd.00002221.10
The Investigation
The first step is to analyze the historical data of the table that threw the error. This can be achieved using the VERSIONS clause of the SELECT statement.
SQL> select versions_xid
, versions_startscn
, versions_endscn
, versions_operation
, pk
, name
from scott.master
versions between scn minvalue and maxvalue
where pk = 1
order by nvl(versions_startscn,0);
VERSIONS_XID VERSIONS_STARTSCN VERSIONS_ENDSCN V PK NAME
03001900EE070000 3492279 3492290 I 1 andrew
02000D00E4070000 3492290 D 1 andrew
Depending upon the amount of undo retention that the database is configured to retain (undo_retention) and the activity on the table, the information returned might be extensive and the versions between syntax might need to be changed to restrict the amount of information returned.
From the information returned, it can be seen that the record was first inserted at scn 3492279 and then was deleted at scn 3492290 as part of transaction ID 02000D00E4070000. Using the transaction ID, the database should be queried to find the scope of the transaction. This is achieved by querying the flashback_transaction_query view.
SQL> select operation
, undo_sql
from flashback_transaction_query
where xid = hextoraw('02000D00E4070000');
OPERATION UNDO_SQL
DELETE insert into "SCOTT"."MASTER"("PK","NAME") values
('1','andrew');
BEGIN
Note that there is always one row returned representing the start of the transaction. In this transaction, only one row was deleted in the master table. The undo_sql column when executed will restore the original data into the table.
SQL> insert into "SCOTT"."MASTER"("PK","NAME") values ('1','andrew');
SQL> commit;
The SQL Apply engine may now be restarted and the transaction will be applied to the standby database.
SQL> alter database start logical standby apply;

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

ORA-01157: cannot identify/lock data file error in standby database.

Hi,
i have a primary database and standby database (11.2.0.1.0) running in ASM with different diskgroup names. I applied an incremental backup on standby database to resolve archive log gap and generated a controlfile for standby in primary database and restored the controlfile in standby database.But when i started the MRP process its not starting and thows error in alert log ORA-01157: cannot identify/lock data file. When i queried the standby database file it shows the location on primary database datafiles names not the standby database.
PRIMARY DATABASE
SQL> select name from v$datafile;
NAME
+DATA/oradb/datafile/system.256.788911005
+DATA/oradb/datafile/sysaux.257.788911005
+DATA/oradb/datafile/undotbs1.258.788911005
+DATA/oradb/datafile/users.259.788911005
STANDBY DATABASE
SQL> select name from v$datafile;
NAME
+STDBY/oradb/datafile/system.256.788911005
+STDBY/oradb/datafile/sysaux.257.788911005
+STDBY/oradb/datafile/undotbs1.258.788911005
+STDBY/oradb/datafile/users.259.788911005
The Actual physical location of standby database files in ASM in standby server is shown below
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
ASMCMD>
ASMCMD> ls
SYSAUX.259.805921967
SYSTEM.258.805921881
UNDOTBS1.260.805922023
USERS.261.805922029
ASMCMD>
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
i even tried to rename the datafiles in standby database but it throws error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Regards,
007

Hi saurabh,
I tried to rename the datafiles in standby database after restoring it throws the below error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Also in my pfile i have mentioned the below parameters
*.db_create_file_dest='+STDBY'
*.db_domain=''
*.db_file_name_convert='+DATA','+STDBY'
*.db_name='ORADB'
*.db_unique_name='11GDB'
Regards,
007

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

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-16831: operation disallowed on this standby database type

Similar Messages

Maybe you are looking for