ECC6 ABAP Cluster: Switch Over to other Nodes without Startup Automatically

[Former Member]

Hi All,

I installed the ECC6 ABAP cluster, however when i switched over to all services from node A to node B, the central instance on node B do not startup automatically.

Did anyone have any ideas?

My installation steps are as below:

1. ASCS node A instance 00, with environment sapinst_hostname=<virtual host> -Gobal

2. MSCS node A, with environment sapinst_hostname=<virtual host> - Gobal

3. DB node A, with environment sapinst_hostname=<virtual host> - Gobal

4. Another MSCS node B, - Gobal

5.Enqueue replication node A instance 10, with environment sapinst_hostname=<virtual host> - Local

6. Enqueue replication node B instance 10, with environment sapinst_hostname=<virtual host> - Local

7. Central Instance node A instance 01, with environment sapinst_hostname=<virtual host> - Local

8. Central Instance node B instance 01, with environment sapinst_hostname=<virtual host>- Local

Please let me know if you have any experience regarding with this issues

Thanks

[Former Member]

MSCS installations are already dealing with virutal hostnames.

Therefore no sapinst_hostname has not to be used (for no instance) UNTIL specified in the Windows installations guides.

Next: CI has to be installed once the second ABAP Server has to be a so called DI. Both should use the same system number (for ex. 01).

peter

[Former Member]

Dear friend

Normally what we doing in the case of cluster installation

1.installed server on A node with virtual host name

2.then in second noted we are installing the application server

3.create the same user and group on B node also

4.Mount following file system

sapmnt/SID

oracle/SID/102_64

usr/sap/SID

Sapmnt/SID/grobal

Sapmnt/SID/profile

shailesh tiwari

[former_member433984]

> 1. ASCS node A instance 00, with environment

> sapinst_hostname=<virtual host> -Gobal

> 2. MSCS node A, with environment

> sapinst_hostname=<virtual host> - Gobal

> 3. DB node A, with environment

> sapinst_hostname=<virtual host> - Gobal

> 4. Another MSCS node B, - Gobal

> 5.Enqueue replication node A instance 10, with

> environment sapinst_hostname=<virtual host> - Local

> 6. Enqueue replication node B instance 10, with

> environment sapinst_hostname=<virtual host> - Local

> 7. Central Instance node A instance 01, with

> environment sapinst_hostname=<virtual host> - Local

> 8. Central Instance node B instance 01, with

> environment sapinst_hostname=<virtual host>- Local

in the installation guide <b>sapinst_hostname</b> is not mentioned, so may be you will need to reinstall the cluster solution. Check also this paper

[CONTENT DELETED]

CI and DI are installed on cluster nodes and are not SPOF - so they are not part of MSCS will not start automatically.

best regards

[Former Member]

Thanks for reply

As CI and DI is non-SPOF, I just wonder whether we should install CI on node A instance number 00 and DI on node B instance number 01 with the same virtual hostname (parameter : sapinst_use_hostname) on both nodes; and both nodes have to start it up manually.

Currently, we install CI on node A instance number 00 and install another CI on node B instance number 00 with same virtual hostname.

[former_member433984]

please refer the link I sent you above and installation guide for details, sapinst_use_hostname is not mentioned there and you have to follow installation guide

best regards

[Former Member]

Dear friend

Can you tel me which platform you installing

shailesh Tiwari

[Former Member]

Actually, we are in win 2003 server and sql platform.

We try to reinstall it, but is still no luck

Thanks