Skip to Content
1
Former Member
Feb 03, 2015 at 01:18 PM

Problem with HANA System Replication Configuration

10221 Views

Hi everyone,

I'am trying to setup a system replication configuration between two developer HANA instances. (This should be a dry run on system replication to upgrade our HANA One Rev 74 to Rev 80 via replication takeover.)

The main specs

SITE_A :

# Developer HANA Rev 80 (1.00.80.00.391861) hosted on AWS (via SAP CAL)

SITE_B :

# Developer HANA Rev 80 (1.00.80.00.391861) hosted on Azure (via SAP CAL)

Main Problem

One registering SITE_B as secondary system (hdbnsutil -sr_register) I get the following error:

error: only system replication chains are allowed with an aditional async secondary site: [primary] <------- [secondary] <---async--- [additional secondary] failed

I think I am missing a very general piece because the message is about a replication chain though I am creating a basic instance to instance replication.

Any help or hint would be great.

The hole story

I followed the documentation:

* http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9049e009-b717-3110-ccbd-e14c277d84a3?QuickLink=index&…

* HANA System Replication - Take-over process

* HANA System Replication - Switching back and forth

Enable replication mode on SITE_A went without problem:

sid-hdb:/usr/sap/HDB/HDB00> hdbnsutil -sr_state

checking for active or inactive nameserver ...

System Replication State

~~~~~~~~~~~~~~~~~~~~~~~~

mode: primary

site id: 1

site name: AWSDEV80

Host Mappings:

~~~~~~~~~~~~~~

done.

2.Step is to register SITE_B as Secondary System. Therefor I stopped the system and afterwards tried this on SITE_B maschine:

vhcalhdbdb:/vap/usr/sap/HDB/HDB00> hdbnsutil -sr_register --remoteHost=54.77.xxx.yyy --remoteInstance=00 --mode=async --name=SITEB

adding site ...

checking for inactive nameserver ...

nameserver vhcalhdbdb:30001 not responding.

collecting information ...

error: only system replication chains are allowed with an aditional async secondary site: [primary] <------- [secondary] <---async--- [additional secondary]

failed. trace file nameserver_vhcalhdbdb.00000.000.trc may contain more error details.

The log contains:

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764448 i Basis TraceStream.cpp(00396) : ==== Starting hdbnsutil, version 1.00.80.00.391861 (NewDB100_REL), build linuxx86_64 not set 2014-05-23 12:00:36 ld7272.wdf.sap.corp gcc (SAP release 20130806, based on SUSE gcc47-4.7.2_20130108-0.15.45) 4.7.2 20130108 [gcc-4_7-branch revision 195014]

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764562 i Basis TraceStream.cpp(00401) : MaxOpenFiles: 1048576

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764592 i Memory MallocProxy.cpp(01181) : Installed malloc hooks

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764596 w Basis Timer.cpp(00660) : Fallback to system call for HR timer

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764599 i Memory AllocatorImpl.cpp(01219) : Allocators activated

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764601 i Memory AllocatorImpl.cpp(01235) : Using big block segment size 16777216

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764604 e Configuration ConfigStoreManager.cpp(00693) : Configuration directory does not exist.

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764607 e Configuration ConfigStoreManager.cpp(00693) : Configuration directory does not exist.

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764609 i Basis ProcessorInfo.cpp(00746) : Using GDT segment limit to determine current CPU ID

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764611 w Environment Environment.cpp(00286) : Changing environment set IMSLERRPATH=/usr/sap/HDB/HDB00/exe//

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764613 w Environment Environment.cpp(00286) : Changing environment set IMSLSERRPATH=/usr/sap/HDB/HDB00/exe//

[6748]{-1}[-1/-1] 2015-02-03 12:57:01.764617 w Environment Environment.cpp(00286) : Changing environment set SSL_WITH_OPENSSL=0

Again, any help or hint would be great.

Cheers,

Mathias