Alias parameters - $(DIR_INSTANCE)

[cillian_cahill2]

Hi Guys,

We've a Microsoft Cluster 2003 with two nodes which has a messed up configuration, it's a test system installed by a consultant some time ago and this was never an issue until now.

The nodes have they're binaries installed on the D:\ disk which is local on each node and the sapmnt dir is installed on a shared disk. The issue is with node 1, it's $(DIR_INSTANCE) resolves to the shared disk F:\ instead of D:\ - so when the cluster fails over to node two, it takes ownership of F:\ and node 1 crashes because it can't access F:\. $(DIR_INSTANCE) should resolve to D:\usr\sap\SID.... as it does on our production system.

So basically I've looked at the registry and the environment variables and I can't see anything defining $(DIR_INSTANCE), so I can't manage to edit it to the correct location....?

The system is NW CE 711 AS JAVA - is there somewhere I have forgotten to check? I thought I could impose the correct parameters in the  config tool in the "instance profile" area to use custom values - but on restart these get over written.

Regards,

Cillian

[Sriram2009]

Hi Cillian

Could you check the enter  $(DIR_INSTANCE) by using the transaction code AL11?

Regards

Sriram

[cillian_cahill2]

Hi Deepak,

I know once $(DIR_INSTANCE) is corrected the system will work correctly... but still can't see where this is defined.

@Sriram - It's SAP CE 711 AS JAVA so that option is not available. - Any other ideas?

Regards,

Cillian

[former_member188883]

Hi Cillian,

DIR_INSTANCE should be defined under instance profile of SAP system.

Please check and add the same.

Hope this helps.

Regards,

Deepak Kori

[cillian_cahill2]

Hi Deepak,

I check this in our production system and this alias is only called in other parameters and in not defined in the instance profile, nor is it in the registry or system environment. So there must be somewhere else it takes it from...?

Regards,

Cillian

[Reagan]

As far as I know the DIR_INSTANCE parameter is an internal kernel parameter which points to the /usr/sap/SID/DVEBMGS00 directory.

Regards

RB

[Former Member]

You just have to set DIR_INSTANCE in DEFAULT.PFL, this should fix the problem.If this isn't working, try to set in start profile and check the instance profile that the parameter isn't set there.

[cillian_cahill2]

Hi Daniel,

I can add the entry DIR_INSTANCE = D:\usr\sap\$(SAPSYSTEMNAME)\$(INSTANCE_NAME) to the instance profile and then it points correctly to instance dir. But I can see that the system has been pointing to the wrong directory only with the last 8 months - some how DIR_INSTANCE was switched to the F:\....I was just wondering if there's another location on the server/system that DIR_INSTANCE could have been configured to point to F:\? I have checked all the profiles, the environment variables and the registry and couldn't see it anywhere. Also on our production system I can't see DIR_INSTANCE in any of these location either, but they point to the correct location.

Regards,

Cillian

[Sriram2009]

Hi Cillian

Can you check the Java server nodes setting in cluster environment.

just open the config tool - Instance number (Node 1 & then 2) -  select  Dispatcher_IDxxxx & Server_id xxxx -  Managers -  configuration manager- check the below mention parameters value starting with physical disk (eg: G:\) or virtual name of cluster(\\Virtual Name\SAPMNT\SID) on both cluster node java instance? is it possible can share the screen shot?

Secstorefs.keyfile

Secstorefs.lib

Secstorefs.secfile

Regards

Sriram

[former_member188883]

Hi Cillian,

Can you please compare your setup in accordance to information in blogs below

http://advansit.wordpress.com/2013/06/06/sap-ecc-6-and-mscs-configuration-activestandby-ha/

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90486554-bdc6-2a10-d39b-e143d5b2e...

If everything looks ok, please share logs from the failover.

Hope this helps.

Regards,

Deepak Kori