Skip to Content
0

Hana indexserver initializing state after creation of new tenant

Dec 10, 2017 at 02:04 PM

100

avatar image
Former Member

Hi,

We have an MDC system with 2 tenants. We created a new tenant using the cockpit and chose the option to not start the tenant database automatically. The creation was successful. We then tried to restore a backup of another tenant to this newly created tenant. During the recovery, there is a prompt to shutdown the new tenant and the process hung there. The cockpit shows the database as starting and its been in this state for more than 2 hours. The 'select * from M_DATABASES' shows the tenant is in 'Starting' state. The alert file of the nameserver shows the following message:

commlib commlibImpl.cpp(00992) : ERROR: commlib::connect to Host: 127.0.0.1, port: 35055, Err or: Connection failed: $msg$ - , rc=$sysrc$: $sysmsg$ [2952]{-1}[-1/-1] 2017-12-10 21:11:45.848902 e TrexNet EndPoint.cpp(00337) : ERROR: failed to open channel 127.0.0.1:35055! reason: (stream: connect failed)

is there a way to force shutdown the tenant other than killing the indexserver process, so that we could perhaps delete this and create a new tenant with the automatic startup option. This, i guess might have issues as the cockpit would not recognize the termination.

Regards,

Jerry

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Jimmy Yang
Dec 19, 2017 at 04:54 PM
0

Hi Jerry,

You tried to stop HANA from Cockpit as well?

If you have access to the SYSTEMDB, you can execute "ALTER SYSTEM STOP DATABASE <SID>".

I am not certain this will work but you can try it and update this thread with the results.

Share
10 |10000 characters needed characters left characters exceeded