cancel
Showing results for 
Search instead for 
Did you mean: 

Rman Channel Failover

Former Member
0 Kudos

I'm aware of the Rman channel failover note that says in point 16...

16. Support for RMAN Channel Failover in BR*Tools

-


(implemented only in BR*Tools 7.20 patch 15)

RMAN error messages that are reported during the Channel Failover are now considered only as warnings. Therefore, these backups are marked as "successful with warnings" and can be used directly in the case of a recovery.

To activate this function, set the following init<DISID>.sap parameter:

rmanchan_failo = yes

...however, some of my systems are using this and later versions of brtools, but the new parm is only working in 'some' places and not recognized at all in others.

What version of the SAP kernel is compatible with this parameter and version of BRTools?

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks again, but again, my problem seems to be not that brtools isn't working but that, though the new parameter is compatible (supposedly) with v15 or later, the SAP kernel apparently disagrees. I'm trying to find out what kernel level is also compatible with rmanchan_failo=yes parameter.

former_member213250
Active Participant
0 Kudos

Hell Jesse

rmanchan_failo = yes

Make sure that the appropriate BRTOOLS version is used.

coming to supported Kernel versions for BR*TOOLS 7.20 is explained in SAP Note : 12741

> SAP KERNEL 64-BIT [UNICODE]

> SAP KERNEL 7.00/7.10/7.20/7.20_EXT 64-BIT

> AIX 64bit HP-UX on IA64 64bit ...

> ORACLE

> DBATL7000O10_nn/DBATL7100O10_nn/DBATL7200O10_nn

Hope it helps

Former Member
0 Kudos

Thanks for the reply; however, that information does not help me.

Let me be a bit more clear.

I have several systems; some running 10g, some 11g oracle/sap.

Some on aix, others on linux.

I go to a system, upgrade brtools to either 15 or 40.

I go to the initSID.sap file and add the parm and run a backup.

On at least 1 linux and 1 aix system, this worked as desired.

On all the others, the backup ends immediately complaining of an unknown parameter... even tho brtools was upgraded.

In the latter case, we restore brtools to previous version, fyi.

What I need to understand and resolve is why on some systems, though brtools is upgraded, the parm is still not recognized at backup time.

Anyone?

volker_borowski2
Active Contributor
0 Kudos

You are right, I misunderstood this

Sounds like the build is not the same throughout different OS Versions?!?!?

Or you've got garbage chars inside the configfile.

May be you should give PL16 a try. It works at least on AIX.

Can't say for other OS.

Volker

volker_borowski2
Active Contributor
0 Kudos

Hi,

we are using 7.20 EXT PL 16 brtools and have been in fact involved with getting this feature activated.

Since we updated it just happened one time, and at least the backup did work, was successfully completed

with warnings, and an incremental backup based on this backup could been taken succesfully as well.

But we had no need to restore this one yet.

We did only test the useability uf such a backup yet with a quite small database (< 100G).

(Ya, you are right, there is stuff left to be tested ...)

Did you check out the logs?

Channel failover needs at least one channel to survive, to tackle the rest of the work.

If you loose all channels, failover will not succeed, because there is no guy left to do the work.

So if you have 4 channels, and loose 4.... busted.

Volker