DB13 Not Running on an MSCS installation

[Former Member]

Hi

We've a MSCS installation - DB running on Node A, Central instance running on Node B. 4.7 extension set 2, windows 2003_x64 and Oracle 10.2.0.2

Installed a local gateway as part of the Oracle Cluster group called GAW. as per OSS 657999

When we attempt to run any DB13 job we get the error:

Can't exec external program (No such file or directory) WaitforSingleObject failedwith %d (No such deviceor address)

I believe that all env. variables and params are as per recommendations - SAPEXE point to c:\windows\sapcluster

- Any ideas

Appreciate you assistance

Conor

[antonio_voce · Accepted solution]

I , check profile parameter in init<DBSID>.sap .

Antonio.

[Former Member]

Hi

- In response to Yaroslav -

- SM59 connections work fine

- There is no entry in HKEY_LOCAL_MACHINE/SOFTWARE/SAP/GW SID

- GW service runs under the SIDADM account

- Service starts and stops fine - also part of the cluster group and starts and stops here fine also.

Conor

[former_member433984]

> - In response to Yaroslav -

> - SM59 connections work fine

> - There is no entry in HKEY_LOCAL_MACHINE/SOFTWARE/SAP/GW SID

> - GW service runs under the SIDADM account

> - Service starts and stops fine - also part of the cluster group and starts and stops here fine also.

Hello Conor,

that is it. Please see item

8. Create the service SAP<SID>_<system number> on node A.

in the note. It is important to have the correct service registration, as later its environment will be inherited by sapxpg, brconnect etc.

br,

Yaroslav

[Former Member]

Hi,

please make sure that in instance profile of standalone gateway:

SAPSYSTEMNAME = <SID>

match with your SAP system <SID>

In other words, don't give to your gateway instance different <SID>, though in related SAP note (657999) they say something completely different:

1. Choose the <SID> and <system number> for the gateway (*). Make sure that they are different from those used by the SAP system.

With kind regards,

Soudruh Ladislav Sedlacek z Brna

[Former Member]

Hi,

Conor, This is a known problem in SAP on MSCS cluster. The error is because SAP requires a remote shell daemon (rsh) for the DB13 functionality to work.

Anyways there are certain steps to be carried out on both the nodes. So please follow the SAPNote 657999 - Installing a Standalone Gateway in an MSCS Environment very carefully as you are working in a cluster environment.

So if this information to you is helpful then please reward plenty of points

Regards,

Suhas

[Former Member]

Hi,

Did you read the first message ? Connor said he has intalled the standalone gateway in the Oracle Cluster Group.

Regards,

Olivier

[former_member433984]

1. does the RFC connection check in SM59 deliver OK?

2. which user account is used to run the GW service?

3. what is the value for AdmUser under HKEY_LOCAL_MACHINE\SOFTWARE\SAP\<GW SID>?

[Former Member]

Hi

Thanks for your assistance

Which Parameter in init<SID>.sap should I be looking at?

Thanks

Conor

[antonio_voce]

I connor, could you drag and drop the file here ?

[Former Member]

Hi,

I suspect you can't run db 13 in a clustered environment because app is one node and db is in another node. When you run db13 it will be looking for the resource in CI and not the DB instance. SAP note is also available for the same.

Regards

D.Mukundan

[Former Member]

Hi,

If the cluster is well configured, DB13 jobs run perfectly on a MSCS cluster.

Regards,

Olivier

[Former Member]

Hi,

You need to find more error logs.

I just can tell you that I've got nearly the same config (only difference Oracle 9 instead of 10) and that DB13 jobs run just fine.

Did you create the SAPOSCOL destination for the Database : SAPOSCOL_DBclusteralias ?

If yes, dose Transaction OS07 works for this SAPOSCOL destination ?

I think OS07 also uses the standalone gateway to run saposcol on the database node.

Regards,

Olivier