ansaurus

Question

Dataguard broker reporting ORA-16801: redo transport-related property is inconsistent with database setting.

Answer 1

+1 A:

It looks to me that you don't actually have any standby redo logs defined in the standby database - all your logfiles are ONLINE. You will need to create the standby logfiles on the standby databases as well. See the Data Guard Concepts and Administration Guide.

EDIT:

Alternatively, you could drop the standby logs from the primary. Strictly speaking you don't have to operate with standby redo logs - they're only required for Real-Time Apply and maximum protection and maximum availability levels of data protection in Data Guard. Oracle does recommend using standby redo logs, and there's really no reason not to (and several reasons why you should). You really aren't using them at the moment anyway - the ones defined on the primary are only used if you switchover and make the primary a standby.

DCookie 2009-12-14 22:47:07

Thanks, this is the conclusion I was coming to, I think I do need the systems in maximum protection so I will disable the dataguard confuration and add the standby logs to the primarys.Am I right to assume that because I didnt have SRLs on the standbys it was not doing Async dataguarding but resorting to applying the logs instead?.Thanks for your help.

2009-12-15 08:26:17

Hi, one more thing, I have tried the following to disable the configOn the primary instanceSQL> alter database add standby logfile group 6('/oracle/ELBEMS1/mirrarch/redostby06a.log','/oracle/ELBEMS1/mirrarch/redostby06b.log') size 100M*ERROR at line 1:ORA-01156: recovery in progress may need access to filesAny ideas, on how I can allow me to add these standby logs while database is in physical standby mode?

2009-12-15 09:37:27

Sorry there are some problems with the above comment.On primary I disabled using DGMGRL Conect internaldisable configuration;And then did the above on the standby, and received that message.

2009-12-15 09:38:34

Solved the problem. For anyone Interested, its this. I ran the following to fix the issue:on primarydgmgrlconnect /disable configuration;got to each standby and run :alter database recover managed standby database cancel;---- Create 1 more additional group then you have redo log groups on primary (so primary had 3, I am going to create 4.alter database add standby logfile group <n> (<filename>) size <size>; alter database recover managed standby database disconnect; Back on primarydgmgrlconnect /enable configuration;

2009-12-15 12:55:12

You are correct - ASYNC log transfer mode requires standby logfiles. If you are using Grid Control, there are some pretty nice Data Guard tools in there, and it gives you immediate feedback that you can't do ASYNC without them.

DCookie 2009-12-15 14:48:31

ansaurus

tags:

views:

answers:

Dataguard broker reporting ORA-16801: redo transport-related property is inconsistent with database setting.

related questions