cancel
Showing results for 
Search instead for 
Did you mean: 

MSCS Install problem - ECC 6.0

Former Member
0 Kudos

I am installing ECC 6.0 on Windows 2003 with SQL 2005.

When I install the CI – Central Instance – the install guide requires I that move all processes to Node-A and run the install from Node-A. When doing so, they request that the CI be installed on a local, non-clustered drive. However, when I do this, SAPINST does not present the local drive as an available drive-letter – only the clustered drive.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

if the network share SAPLOC is existing you are not longer able to choose a different installation drive.

The SAPLOC share is normaly created in HA installation through <b>ASCS</b> installation and automatically removed when processing <b>First MSCS Node</b>.

If this fails for any reason or you created the share manually you should delete it,

after that you can change the driveletter.

regards

Peter

Former Member
0 Kudos

Hi,

did you already installed ERS instance (Enqueue Replication Service)?

if you did so, then ERS is installed locally on a local drive, and SAPLOC share is pointing correctly to the local drive - and there is no need to do anything, e.g. everything is OK.

otherwise you have to delete SAPLOC share.

Check where is SAPLOC pointing, if points to a SAP shared drive where ASCS instance is locaed, then it is wrong and you have to delete it.

Best regards

Goran

Former Member
0 Kudos

Well - I'm making some progress but I still have an issue.

I wiped everything out and started again. This time when declaring the SAP Cluster Group I provided a local drive - I had omitted that in the past. Now the ERS installs locally on C: and the CI also gets installed on the local drive C: .

My current setup:

Node-A

C: - local drive - has ERS and CI

E: - cluster drive - has ASCS - fails over successfully

Node-B

C: - local drive - has ERS

E: - cluster drive - only available when failed over

OK - New Question: Now that CI is successfully installed on C: (local) drive on Node-A, what happens if Node-A dies. I have lost the CI and can no longer log onto my system. Surely this defeats the point of having a cluster.

Former Member
0 Kudos

you need to install a addtional dialog instance (and configure it equalt to the CI) on node B.

peter

Former Member
0 Kudos

I have done that.

Question still remains - what if B dies completely?

Former Member
0 Kudos

..and you should not connect directly to one specific App. Server, but you have to use load balancing to connect to available one.

regards

Goran

Former Member
0 Kudos

meant to say - what if >> A << dies completely?

Former Member
0 Kudos

B does the complete job.

Peter

Former Member
0 Kudos

Are you suggesting that I install a CI on node-B as well?

Former Member
0 Kudos

well not an CI but an DI and configure it the same way as the CI (number and types of WPs).

The CI in 700 HA does functionally not differ from the DI (except the Instance name and the initial wp setting).

Peter

Former Member
0 Kudos

you need to have AT LEAST 2 Application servers (e.g. one Central Instance and one Dialog Instance) installed on 2 DIFFERENT machines (in your case MSCS Node A and B).

When you use loadbalancing (which in ABAP goes over message server - ASCS instance) , it would connect you to app. server which is available and has the best performance.

If you install more App.server then 2 (e.g. additional DI) on additional different machines - it is even better, in terms of (high) availability and as well scalabiliy.

But 2 are minimum.

SAP offers you possibility to install CI and DI on MSCS nodes, so that you can reduce TCO. In this case you have to do a proper sizing, as it can happen that on one MSCS you run an appserver and (clusterd) database.

Bu you have also possiblity to install app servers outside of MSCS. Any combination is possible. What is important is - at least 2 app- servers on 2 different machines.

Goran

Former Member
0 Kudos

Hmmm - The CI install gave me work process that the DI did not.

Should I MANUALLY add Enqueue, V1, V2 and Spool processes to the CI?

Former Member
0 Kudos

well it is a bit confusing that Central Instance still has a name DVEBMGSxx , althought it doesn't includes Enqueue(E) and Message(M) server processes.

Enqueue(E) and Message(M) server processes are now part of ASCS instance

and they are UNIQUE , e.g. only one per one SAP system

CI name DVEBMGSxx is kept (unfortunatelly) currently for backward compatibility reasons.

You can add afterward to DI any aditional proceses which are possible to confugure it more than one per one SAP system

Former Member
0 Kudos

because this one is part of ASCS

Former Member
0 Kudos

Great - issue is solved.

Many thanks for all the help.

Answers (1)

Answers (1)

Former Member
0 Kudos

could you please provide the available drive and continue with next and again come back to the previous screen you may get the list of all the drive, it happened with me.

Cheers,

-Sunil