Problem in selecting different drives while DB installation in Cluster.

Question

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
D: 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

Answer 1

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          : D:
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