HANA DB Recovery issue - convert topology failed

[Former Member]

May I please request for help on the below issue. I am unable to Recover my DB using a backup without catalog.

RECOVER DATA finished with error:

recovery could not be completed,

Recovery failed in nameserver startup: convert topology failed: found multiple instance numbers in topology

Could not start master name server

Recover Trace File -

hana1 is master

creating file recoverInstance.sql

restart database

restart master nameserver: 2016-01-10 06:11:34

start system: hana1

start system: hana1 failed: start of nameserver failed

recoverSys failed: 2016-01-10 06:11:45

2016-01-10T06:11:44+00:00  P032456      1522a29661c INFO    RECOVERY state of service: nameserver, hana1:35

001, volume: 1, RecoveryExecuteTopologyAndSSFSRecoveryFinished

2016-01-10T06:11:44+00:00  P032456      1522a29661c ERROR   RECOVERY RECOVER DATA finished with error: [448

] recovery could not be completed, [110092] Recovery failed in nameserver startup: convert topology failed:

found multiple instance numbers in topology

2016-01-10T06:11:44+00:00  P032456      1522a29661c ERROR   RECOVERY RECOVER DATA finished with error: [448

] recovery could not be completed, [110092] Recovery failed in nameserver startup: convert topology failed:

found multiple instance numbers in topology

Regards,

Rupali S

[SK-EA]

This message was moderated.

[former_member673803]

Hi,

Please check the below SAP note.

1905462 - HANA scale-out landscape : topology mismatch leads to recovery failure

Regards,

Govind

[Former Member]

@Govind - I have already checked this Note and it did not help.

@Sadanand - Thanks for the information, guess you are right, I did try to recover my Target DB post failure of Source DB restore using XS Advance Runtime deployed Target DB backup, but it caused same error.

However Target DB was able to get restored successfully to its Golden backup (Fresh Install without XS Adv Runtime)

Its did get restored to state before XS Adv Runtime was deployed, BUT still keeping the XS services which is weird.

I still haven't found any official SAP Note, where SAP has stated about such bug and hope they provide us temporary workaround till the bug is fixed.

Regards,

Rupali S

[sadanand_bhat]

Fix is available with Revision 111. Please refer the Note: 2265765

[Former Member]

Rupali,

Do either the source or the target have multi-tenant DB containers enabled?

-Jake

[Former Member]

Hi Jake,

Nope, none are Multi-tenant, but distributed systems (source and target)

Node 1 - Master

Node 2 - Streaming Server

Regards,

Rupali S

[sadanand_bhat]

Please check this with SAP. Its a known issue. There is no B&R possible if you had enabled XS Advanced (as of this date). If this answers your question, please close the thread.

[sadanand_bhat]

Can you tell me which version of HANA are you using?

Also can you confirm that the backup which you are using is correct in terms of topology? i.e., number of services in target system is same as that of services in backup?

[Former Member]

Hi Sadanand,

HANA DB version is SP11 (source & target)

In terms of topology, I reckon its exact match

SOURCE

hana1:/usr/sap/STU/HDB50/hana1 # more daemon.ini

[diserver]

instances = 1

[webdispatcher]

instances = 1

[xscontroller]

instances = 1

[xsengine]

instances = 1

[xsexecagent]

instances = 1

[xsuaaserver]

instances = 1

TARGET

[diserver]

instances = 1

[statisticsserver]

instances = 0

[xsengine]

instances=1

[webdispatcher]

instances=1

[xscontroller]

instances = 1

[xsexecagent]

instances = 1

[xsuaaserver]

instances = 1

Apart from this how can I check the number of instances in theTopology ?

Regards,

Rupali S

[sadanand_bhat]

This is a known issue (because of XS Adanced configured on this). Please refer Note for the info : 2233866

[Former Member]

Hi Sadanand,

This is a release note and isn't talking anything about DB recovery issue.

Regards,

Rupali S