Standalone Gateway installation in Windows 2008 MSCS

[Former Member]

Hi Experts,

We are implementing note 657999 and we are able to create the service in Node A and Node B, and done everyting whatever the note 657999 says. The gateway service is running but the resource we created in the failover cluster management is not coming up and also the gateway server in MMC

The sapstart log file under c:\windows\sapcluster\sapgw\work folder having below error-

(1800) CreateProcess: C:\Windows\sapcluster\sapgw\gwrd.exe

pf=C:\Windows\sapcluster\sapgw\dbsagw33.pfl

(6020) Parent shutdown at 2011/11/16 23:37:39

(6020) Kill(SIGINT 1800) failed

Send Signal SIGKILL to process 1800

Please look into our issue and let us know what is the problem.

Regards,

Nilesh

[Former Member]

Hi,

Please download latest NTCLUST.SAR from market place and apply. This is a known issue for which note(1043592) is also there.

Regards

D.Mukunthan

[sunny_pahuja2]

Hi,

Could you please paste log from gateway work directory ? Have you added the gateway entry in MSCS cluster ?

Thanks

Sunny

[Former Member]

Hi All,

My stand alone gateway server is running in my MMC now. But still I am unable to execute actions in DB13.

Now sometimes my actions (like database check or full online backup) executed successfully but maximum times it gives the same error- Here is the log-

Job started

Step 001 started (program RSDBAJOB, variant &0000000000043, user ID SUDIP)

Execute logical command BRBACKUP On host ORACLEIIP

Parameters:-u / -jid FLL__20111121200427 -c force -t online -m full -p initiip.sap

SXPG_STEP_XPG_START: is_local_host: rc = 403

SXPG_STEP_XPG_START: host = ORACLEIIP

SXPG_STEP_XPG_START: is_local_r3_host: rc = 802

SXPG_STEP_XPG_START: RFC_TCPIP_CONNECTION_OPEN: rc = 1003

SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1.003

SXPG_COMMAND_EXECUTE(LONG)

<timestamp> = 20111121200427

COMMANDNAME = BRBACKUP

ADDITIONAL_PARAMETERS =

-u / -jid FLL__20111121200427 -c force -t online -

m full -p initiip.sap

LONG_PARAMS

OPERATINGSYSTEM = ANYOS

TARGETSYSTEM = ORACLEIIP

DESTINATION

SY-SUBRC = 1003

SXPG_COMMAND_EXECUTE failed for BRBACKUP - Reason: program_start_error: For More Information, See SYS

Job cancelled after system exception ERROR_MESSAGE

Please look into this log and let me know what needs to be done in my system, so that my DB13 works smmothly

Regards,

Nilesh

[Former Member]

Hi Nilesh,

Can you please cross check the configuration steps mentioned in the note 657999? I hope you gave different SID name for standalone gateway instance.

Thanks,

Siva Kumar

[Former Member]

Hi,

Yes....I have choosen different SID (GW1) for gateway and 33 as instance number. So I hope 3333 is the gateway port now and needs to be open between two node2 of clusters.

Regards,

Sudip

[Former Member]

Hi,

Please make sure services file in both nodes has standalone gateway entry.

Thanks,

Siva Kumar

[Former Member]

Hi Siva,

By default the service file contains all gateway entries

In my case the entry should be sapgw33 3333/tcp

Thanks,

Sudip

[Former Member]

Hi Nilesh,

Can you check what is the hostname that you have mentioned in your Gateway profile .pfl file?

1). Is that pointing to Node name or Failover Cluster Management server name like SAP<SID>ORA.

2). check the dependencies for Gateway in Failover cluster management.

3). In C:\Windows\SAPCLuster compare the executables with other working server.

4). Please check C:\windows\SAPCluster\SAPgw folder has sapxpg.exe file.

Thanks,

Arjun