Restart an application server without disturbing the users and BG jobs.

[former_member190251]

Hello Team,

We have CI and 2 Application servers. We have requested customer to restart the 1 application server due to some issue.

But customer wants to do without affecting the job and users.

For users   - we can remove the application server from SMLG.

But i want to know how to suppress the jobs which are running in this application server. however we could not find any jobs are configured in this application server. Jobs will automatically selecting this server.

Please let us know the steps how to avoid the jobs running in the application server.

Regards

Subbu

[Former Member]

Hi,

step-1 remove the affected server from rz12,sm61 and smlg. This will make sure that no new job starts on this server while you are preparing to shutdown the app server.

Step-2- You need to make sure that all business critical jobs should finish if they are running on affected server. If only house keeping jobs are running and if those can be ignored then you can restart the server.

Step-3- Restart the server.

Step-4 Revert the changes done in rz12,sm61 and smlg.

Regards

Krishan

[gabriella_kiss]

Hi,

Before taking any server down you drain it by running the following
commands several hours ahead:

1.
Generally SAP does not recommend to define job with the target server.
Let the system decide on its own for the load balancing on the servers
I would recommed you to follow the below notes for the servers to have
a good load balancing for the job distribution.

24092      Distribution of background jobs on application serv
519059     FAQ: Background processing system

In the above case you can take out the affected appliaction server from the logon groups

2)Remove RFC group for that specific server
  
3.Deactivate the update for that server.
Using transaction SM14 to deactivate update causes all active
transactions to be suspected.  Once you deactivate an update server
then no new update requests are sent to this server. It doesn't
actually stop the processes but ignores them for future update requests.

   In order to deactivate the update we take the following steps:
   A) -Run transaction SM13
   B) -From menu -> Goto -> Server -> highlight the server -> from menu
       select Edit -> Server name -> deactivate

Regards Gabriella Kiss

[Former Member]

Hi Subbu,

To do that you need to have some delta time so that the current job running on the (to be restarted) apps server can finish after you perform the below steps.

1. SMLG - Remove the application server for further Dialog logon

2. RZ12  - Remove the server from further RFC logon and background jobs too

3. SM61 - If server group is configured for batch processing  - Click on Job-Servergruppen - remove the assignment from the groups mentioned there in folders.

4. SM51 - Click on the target server and goto EDIT >> Change state >> Deactivate. This will put the server in passive mode where it will deny any incoming connection except direct logins.

Now once the current sessions are done in that application server... restart it.

Cheers,

TD

[Former Member]

Hi Subbu ,

Please follow beofre the one DI as below

1) suspend the jobs with BTCTRNS1

2) check for the active jobs that are running  on the respective DI server and wait for the jobs completion .if these jobs are not critical you can cancel with proper approval

3) remove this server from SMLG and RZ12  and aslo from default batch group from SM61

if no default batch group has defined ,you can add CI and other DI server in SAP_DEFAULT_BTC group

with the above 3 steps you have isolated the DI server and now you can run BTCTRNS2 so that your jobs will resume on the available servers from group SAP_DEFAULT_BTC>

Regards,

Srini

[Former Member]

I don't think running BTCTRANS1 is a good idea as it will suspend all the jobs but here the requirement is to be able to stop one apps only and let the jobs run in other.

[alwina_enns]

Hello Subbu,

one possibility would be to create a server group in SM61 with the name 'SAP_DEFAULT_BTC', which would contain all server except of the one affected application server. The jobs without a target server will be executed then on the servers from this server group. The note describe this:

786412 - Determining execution server of jobs w/o target server

Regards,
Alwina

[former_member188883]

Hi Subbu,

But i want to know how to suppress the jobs which are running in this application server. however we could not find any jobs are configured in this application server. Jobs will automatically selecting this server.

Running jobs cannot be moved to other application server. you need to wait till the jobs are completed and cancel the running job .

Only the scheduled jobs with defined target server can be moved to other application server.

Regards,

Deepak Kori