Scribd
Upload
10 views4 pages

FNQ DB Upgrade

Uploaded by

Sharanu Hosamani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views4 pages

FNQ DB Upgrade

Uploaded by

Sharanu Hosamani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Enable replication:

To enable system replication, enter the following command: (On Primary)

hdbnsutil -sr_enable --name=WDF

To register the secondary, enter the following command:

hdbnsutil -sr_register -–name=ROT --remoteHost=hanahost-xyz --remoteInstance=00 --


replicationMode=[sync|syncmem|async] --operationMode=[delta_datashipping|logreplay|
logreplay_readaccess]
Replication Disable:

hdbnsutil -sr_unregister -–name=ROT

hdbnsutil -sr_disable
Takeover:

Alternatively, to perform a takeover on the command line, execute the following command:

hdbnsutil -sr_takeover [--comment=”Some text”]

The secondary system must be fully initialized (system view M_SERVICE_REPLICATION) and all services
active. Optionally, you can add a comment that will be persisted in the system view
M_SERVICE_REPLICATION_TAKEOVER_HISTORY.

To perform a takeover with handshake, execute the following command:

hdbnsutil -sr_takeover –suspendPrimary

if the installed system version on the primary is HANA 2.0 SPS 04 or greater
then you have the option to use the --suspendPrimary parameter for a
'takeover with handshake' which ensures that all redo logs are written to
disk. In this case, execute the takeover as <sid>adm with the following
command:


hdbnsutil -sr_takeover --suspendPrimary

https://help.sap.com/docs/SAP_HANA_PLATFORM/2c1988d620e04368aa4103bf26f17727/
ee3fd9a0c2e74733a74e4ad140fde60b.html

https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/
9a4a4cdcda454663ba0c75d180c7ed11.html

Note:

When the primary system isn’t available, the takeover will be a failover. In this case, you need to make
sure that the primary system doesn’t reconnect to the network to claim it’s role. It first needs to be
stopped and registered as secondary. If everything is back online again and working as expected, you
can return to the original situation by repeating the takeover, now called failback.
The Python script getTakeoverRecommendation.py supports the decision-making process. It calls two
other scripts: landscapeHostConfiguration.py and systemReplicationStatus.py.

Depending on the outcome, it returns the following results:

Required: The primary system has errors.

Cannot decide: The system replication status is unknown.

Possible: All flags are green with the primary system up and running and with system replication in sync.

Replication mode Configuration:

Let’s move on to system replication configuration. First, to change the log replication mode, enter the
command:

hdbnsutil -sr_changemode --mode=[sync|syncmem|async] (FRUN is in syncmem)

You might also like