MC SG & SAP

[Ludovic Derlyn]

Hi,

This is my config, I run with MCSG A11.17 and SAP (SG-Ext-SAP-R3, toolkit etc...)

I have two nodes in my cluster, first node DBCI second node AS for SAP
When I stop my package, AS is stopped also
In my sap.conf , I have set ASTREAT=11:

ASSID[0]=PRE; ASHOST[0]=hostsas; ASNAME[0]=D; ASNR[0]=01; ASTREAT[0]=11; ASPLAT
FORM[0]="HP-UX"

My problem is when I execute an TOC , package is stopped on nominal node, DBCI has stopped and switch to second node, therefore on second node AS is not stopped
AS will be stopped , because some transactions will be lost....

Have you an idea ?

Regards
L-DERLYN

[David Dilly]

Hello Ludo
It depends of the ASTREAT....

[David Dilly]

This is my last sap.config :


ASSID[16]=PRD; ASHOST[16]=sd1prdpu; ASNAME[16]=D; ASNR[16]=01; ASTREAT[16]=14; ASPLATFORM[16]="HP-UX"

Regards.
David

[David Dilly · Accepted solution]

Look at the sap.config example :

ASTREAT[*]: defines the way the instance is treated if the status of the
# package changes.
# ASTREAT[*]=0 means, that the Application Server is not affected by
# any changes that happen to the package status.
# This value makes sense to (temporarily) unconfigure the instance.
# ${START_WITH_PKG}:
# Add 1 to ASTREAT[*] if the Application Server should automatically
# be started during startup of the package.
# ${STOP_WITH_PKG}:
# Add 2 to ASTREAT[*] if the Application Server should automatically
# be stopped during halt of the package.
# ${RESTART_DURING_FAILOVER}:
# Add 4 to ASTREAT[*] if the Application Server should automatically
# be restarted if a failover of the package occurs.
# If you don't use the restart option you have to configure your
# SAP ABAP Engine to use DB-RECONNECT.
# ${STOP_IF_LOCAL_AFTER_FAILOVER}:
# Add 8 to ASTREAT[*] if the Application Server should automatically
# be shut down if the package fails over to its node.
# This treatment policy will overrule the ${RESTART_DURING_FAILOVER}
# if applicable.
# ${STOP_DEPENDENT_INSTANCES}:
# Add 16 to ASTREAT[*] if the instance is a Central Instance and
# all specified Dialog Instances with the same ASSID[] should
# be stopped prior to it.
# This treatment policy overrules the treatment policies
# specified for Dialog Instances.

14 mean : AS shutdown when dbci start on same node + AS restarted if a failover of the package occurs + AS should automatically be stopped during halt of the package.

Regards

[David Dilly]

This is the version of the Toolkit : SGeSAP - B.03.12.00

[Alessandro Bocchino]

If DBCI TOCs the database is gone, so it is of no use trying a regular stop of the application server - transactions are lost anyway.

Before the DBCI startup script tries to start the Central Instance on the failover host, it tries to stop the application server then tries to cleanup any memory segment left, so the DBCI should startup in a clean way.

You can eventuallly try a strict cleanup which forces the removal of residual memory segments.

Best regards,
Alessandro Bocchino
http://www.risolve.com

[Ludovic Derlyn]

I will test the value 14 next week

Thanks a lot