cancel
Showing results for 
Search instead for 
Did you mean: 

SAP_REORG_TEMSE_CHECK job is running long time in Node2 and not in Node1

former_member190251
Participant
0 Kudos

Hi,

We observerd that SAP standard job SAP_REORG_TEMSE_CHECK (program RSTS0020) takes real long in node2 and much faster in node1.

Node1 - MSSQL DB

Node2 - SAP central instance.

1. It happens all the time it runs in node2

2. No critical log, error related to the job found in SM21.

3. No critical log found in work process log.

Could you please advise me how to resolve this issue.

Regards

Subbu

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Please check the DB in consistency as per the SAP note 23345 and cosider the notes 48400 and 16083 to resolve the problem.

BR,

Prabhakar

sunny_pahuja2
Active Contributor
0 Kudos

Hello,

It might be because of communication with the database as both are on separate nodes and communication happening over network. Have you observed this problem with some other job?

Thanks,

Sunny

former_member190251
Participant
0 Kudos

Hi,

Thanks for the prompt reply.

Is there any command to check the connectivty issue between Node1 and Node2(other than Niping).

Moreover we observerd that the issue is not with all the job are running in Node2. only some jobs like SAP_REORG_SPOOL_NEW is taking more time to complete in Node2 compared to Node1.

Regards

Subbu

Former Member
0 Kudos

Hi,

Try and check this note if it helps.

805934 - FAQ: Database time

1100926 - FAQ: Network performance

  • To exclude problems in the network area between SAP and Oracle, check the network (Note 1100926).

Thanks

Rishi Abrol