Answer / mohd sohail

In sm66 we can monitor long running jobs

Answer / adel

First check if SAP was restarted during the time the job was running.

if job shows running while system was restarted it is a bug.
check oss note

otherwise, put some traces on the job. very probably the program has inefficient code doing a very long select. in fact doing nothing.

Answer / ramanji

1.Check the over view of the Job-SM37.
2.Check on which workprocess it is running-SM50.
3.Increase the size of TEMP table space.
3.Update the database.

i can also check SAP compliance callibrator in r3p for SOD conflict and simulation tool in addition to id creation , roles assognments , what job i can expect ?

1 Answers  

---

how can u do kernal upgrade in dual stack?

4 Answers   Fujitsu,

---

No sample data in IDES after a successful client copy. When will occur this problem and how to fix it?

2 Answers  

---

What is the importance of early watch client?

5 Answers  

---

In a situation where my sap system is down (users unable to login to sap system), how to analyze the problem?

0 Answers  

---

WHICH IS BEST WEBSITE FOR DOWMLOAD ARTICLE ABOUT BASIS

3 Answers  

---

Hello Guys, If any body looking for "SAP Vendor Invoice Management (VIM) Training", Please Contact Me,We will covers all SAP VIM topics along with end to end ICC, Document pipeline xECM, Enterprise scan etc. Email ID :kakumanusasikanth@gmail.com

0 Answers  

---

what is the purpose of Logon groups? expalin me briefly ?

4 Answers   Infosys,

---

What is SSO? How to configure SSO?

0 Answers  

---

Why we execute SGEN, which Tables it modifies,will it cause DB growth? is it possible to execute SGEN later on after Golive?

0 Answers   IBM,

---

could u explain the transport steps (step by step) procedure?

11 Answers   IBM, TCS,

---

Explain what is the use of reference and service user in sap?

0 Answers  

---