Problem in selecting different drives while DB installation in Cluster.

[anilbedi_sapsuperadminist]

Hello,

We are installing ECC 6.0 (AS ABAP), MS SQL 2005, Windows 2003 SR2, MSCS Cluster (One cluster, two nodes, Active/Passive)

Directory Structure

Drive / Cls Group / Used for

-

---

C: Local Disk

😧 Local Disk

E: (SAN) SAPDBGRP MSSQL

F: (SAN) SAP PRD SAP Global files

G: (SAN) SAPDBGRP Datafiles

H: (SAN) SAPDBGRP Transaction log files

Q: (SAN) MSDTC Quorum Resource

-

---

- installed windows and MSCS cluster. Tested successfully.

- installed SQL Server 2005 database server software (installed on both the nodes)

- Server software installed by default in C:\program files\...

- In parameter window "Cluster Group Selection"

provided parameter value as "Data Files = E:\Microsoft SQL Server\"

(for Data file for master, model and msdb)

- installed Central Services Instance for ABAP (ASCS) on First Node

- Configured he First MSCS Node (where it created the SAP cluster group)

- Installing the Database Instance (Resources in SAPDBGRP cluster are E: G: H: drives)

- Parameter Window "MS SQL Server > Database Files"

- Path for Datafiles - Default E: Changed to G:

- Path for Tran log - Default E: Changed to H:

If default E: drive is selected, goes to next step

If changed to G: or H: drive, error message comes <b>"Caught EKdException in Modulecell: no Element found"</b>

Installation Log File (last 8 to 10 statements are displayed hear)

=========================================================

INFO 2007-04-06 17:25:57

Execute step dAskForFilesConfig of component

|NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB

|ind|ind|ind|ind|2|0|MssDbLayout|ind|ind|ind|ind|3|0.

ERROR 2007-04-06 17:26:44

FKD-00037 Query did not return a result.

ERROR 2007-04-06 17:26:44

FKD-00038 Query did not return a result.Select attribute NeededSpace, statement: WHERE Name = 'G'

ERROR 2007-04-06 17:26:55

FKD-00037 Query did not return a result.

ERROR 2007-04-06 17:26:55

FKD-00038 Query did not return a result.Select attribute NeededSpace, statement: WHERE Name = 'G'

ERROR 2007-04-06 18:02:29

FKD-00037 Query did not return a result.

ERROR 2007-04-06 18:02:29

FKD-00038 Query did not return a result.Select attribute NeededSpace, statement: WHERE Name = 'H'

ERROR 2007-04-06 18:02:37

FKD-00037 Query did not return a result.

==========================================================

Please guide.

Ghanshyam

Hello,

Problem solved, G: & H: were added to the SQL Server resources dependency.

Thanks for everybody's help.

Message was edited by:

Basis Team

[Former Member]

I also ran into this problem with my SQL 2005 and SAP ERP 2005 installation with SAN-based storage. I also implemented the "SQL 2005 dependency" solution Basis Team wrote of. Here are the steps:

If you get a “Caught EKdException in Modulecall: no Element found.” Dialog Error box, then add the drives you want to use for the data, logs, and tempdb to your SQL 2005 cluster. They will all be Physical Drive resources.

1) Take the SQL Server cluster offline.

2) Keep the Physical Drive resources offline, and add them as a dependency to the SQL Server resource (Properties --> Dependencies --> Modify).

3) Bring the SQL Server cluster online.

4) Hit the “Back” button on the SAP installer for SAP to recognize the changes.

The size of your data, log, and tempdb files depends on your project objectives.

Make sure that the files are not larger than the underlying virtual disk. It is easy to change the file sizes later in SQL 2005 if needed.

[Former Member]

Thank you Val,

I was able to overcome this error after adding the disk drives as dependencies to the SQL Server resource.

Regards,

Santhi Bushan.

[Former Member]

I had the same thing when I Installed ECC 60 with MsSQL 2005.

Also with SCM 5.0 and MsSQL 2005.

It seems SAPINST does not check the right amount of freespace on a mounted SAN drive.

e.g. 200 Gb on F:\SQL2005\databases\<SID>\SAPDATA1 where the SAPDATA1

is a mounted SAN drive of 200 Gb, and F is just 1 Gb of root space.

Workaround: install the database files on a temp disk where there is enough space, or try to set the data/logfiles to 1 Mb in SAPinst.

(they grow as the database build is in progress)

Regards,

Leo Bakker

[Former Member]

Thank you very much Ghanshyam

i will try the installation again, in case of any douts i will consult u again,

i really appericiate ur help

thanks again

Zeeshan

[Former Member]

hi Basis team '

i need help please tel me in the STEP CREATE SAP CLUSTER GROUP...

what did u put in the following fields as per ur scenerio..

we put follwing while our installation

SAP SID: PSP

Cluster Name: we put virtual name of cluster management group

Global Disk: we put a drive S from shared disks

Local Disk: we left it empty, coz it was showing only shared disks in combo....

Network Name: virtual host name we created in DNS for SAP Cluster Group

IP address: ip....

Subnet : subnet of above ip...

Network to use: PUBLIC

i m asking coz in our cluster group we are unable to see dialog instance...and when we shutdown Node 1 SAP is not workin...

plz plz help

[anilbedi_sapsuperadminist]

Hi,

My problem of Drive selection got solved after I put drives (E,F,G) in db cluster group.

I did not face any problem which you have mentioned. Following are the cluster related parameters required while installation, (other than the normal parameters)

Installation Steps (MSCS Cluster,One Cluster, Active-Passive)

SQL Server S/w Installation

-

---

Automatically installs on Both the Nodes.

Database Instance

-

---

Before starting DB instance, check SQL Server for Disk Recources

Manually add the disk G: & H: to Resources Type to SQL Server if not available Check Dependencies

in SQL Server resource: E:, G:, H:

Profile directory :
SAPCIGRP\sapmnt\prd\sys\profile

Local MSSQL Server : sqlcluster

Path for Datafiles : G:

Path for Logfiles : H:

TempDB drive : E:

Configure the MSCS Node-B

-

---

Move resources to Node-B

Instance Type : AS ABAP

SAPSID : PRD

Instance Number : 00

Virtual Host Name : SAPCIGRP

Support of multiple SAP : No

Enqueue Replication Server Node-A

-

---

SAPSID : PRD

Instance Number : 00

Virtual Host Name : SAPCIGRP

ER Instance Number : 10

ER Drive : 😧

Enqueue Replication Server Node-B

-

---

Move resources to Node-B

SAPSID : PRD

Instance Number : 00

Virtual Host Name : SAPCIGRP

ER Instance Number : 10

ER Drive : D:

Central Instance on Node-A

-

---

Move resources to Node-A

Check the permissions of SAPMNT share

Profile directory :
SAPCIGRP\sapmnt\prd\sys\profile

Central Instance Number : 01

Host Transport Dir : SAPCIGRP

DDIC password different : No

SOLMAN Key : XXXXXXXXXXXX

Dialog Instance on Node-B

-

---

Move resources to Node-B

Profile directory :
SAPCIGRP\sapmnt\prd\sys\profile

Central Instance Number : 01

Other are regular parameters which you provide for standard installation. I could successfully install SAP in MSCS cluster.

<b>IMP: You Must upgrade your kernel to DW105, or your failover / failback will not work.</b>

Ghanshyam