Skip to Content
0

New SQL Monitor: SQLM_UPDATE_DATA job not scheduled automatically

Jan 31, 2017 at 02:06 AM

192

avatar image

Hi Experts,

Regarding the new SQL Monitor I understood that from SAP Netweaver 7.4 and above SP3, the following background jobs will be scheduled automatically once the servers are activated in SQLM

1. RTM_PERIODIC_JOB

2. SQLM_UPDATE_DATA/SCHEDULE

3. SQLM_DEACTIVATE/SCHEDULE

But when when I activate the servers in SQLM, only the RTM_PERIODIC_JOB is scheduled. The remaining jobs were not scheduled automatically.

Did I miss any settings. Please advise

Thanks in advance

Regards

Anand

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Armin Beil
Feb 02, 2017 at 07:36 AM
0

Hello Anand,

you are right, the jobs should be scheduled automatically. Which 7.40 SP do you use?

What is currently shown in the status overview of transaction SQLM for the lines "Scheduled Data Refresh Job" and "Scheduled Deactivation"?

Best regards,
Armin

Share
10 |10000 characters needed characters left characters exceeded
Anand Krishnamurthi Feb 02, 2017 at 07:57 AM
0

Hi,

Thanks for the update.

Currenty we are using SAP Netweaver 7.4 SP15.

In SQLM the status overview is shown for the lines requested

Scheduled Data Refresh - Job Scheduled for Job Event SAP_RTM_COLLECT_ALL_FINISHED

Scheduled Deactivation - 02/09/2017 / 15:49:20 (UTC+8)

I also checked im SM37 for the job based on the event given in Scheduled Data Refresh, there is a job SQLM_UPDATE_DATA/SCHEDULE in released status. when the job will be active...?

Also if i deactivate the servers, the job SQLM_UPDATE_DATA/SCHEDULE is getting deleted.

Regards

Anand

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Hi Anand,

the event SAP_RTM_COLLECT_ALL_FINISHED is fired every time the Job RTM_PERIODIC_JOB finishes. Then SQLM_UPDATE_DATA/SCHEDULE is triggered as a follow-up job of the RTM job. By default this is once per hour. Status released is fine.

The deactivation job is also in place as you can see from the status message. It's easy to miss it in SM37 since SM37 selects for the current day by default while the deactivation job is scheduled for the 9th of February.

Seems that all jobs have been scheduled correctly. If something would be wrong with the jobs you would see yellow or red warning icons in the status overview of SQLM.

Best regards,
Armin

1

Hi Armin,

Thanks for the update and also yes as u have mentioned.

  • There is a deactivation job scheduled on February 9th.
  • But in case of the Job SQLM_UPDATE_DATA/SCHEDULE, I can see it on SM37 in release status only when I activate the server in SQLM.
  • Also the Job RTM_PERIODIC_JOB which was released as per the job frequency got finished. But even after that the job SQLM_UPDATE_DATA/SCHEDULE is still in released state

Just for clear understanding, will there be only one job(SQLM_UPDATE_DATA/SCHEDULE) scheduled when the server is activated. Also I don’t see the job triggered to active and finish state when the RTM_PERIODIC_JOB finished and a new job SQLM_UPDATE_DATA/SCHEDULE scheduled.

Regards

Anand

0
Anand Krishnamurthi

Hi Anand,

SQLM_UPDATE_DATA/SCHEDULE should only be scheduled if SQLM is active. If SQLM is inactive there should be no SQLM_UPDATE_DATA/SCHEDULE job. The behaviour on your system is fine.

Regarding the last point:

Please start transaction SQLM and click "Job Overview" from the toolbar. That should bring you to the SM37 results page. Please verify whether there are entries for SQLM_UPDATE_DATA/SCHEDULE in status finished or not.

If SQLM was continuously active for a couple of hours then there should be some entries with status finished. In that case everything is correct and as expected. If SQLM was active for some hours but there are no entries with status finished please turn off SQLM and create a customer incident for this on component BC-DWB-TOO-RTA.

Best regards,
Armin

1

Hi Armin,

Thanks for the reply.

As you have mentioned, made the SQLM to be continuously active for a few hours and I can see job QLM_UPDATE_DATA/SCHEDULE in finished status.

The SQLM is working as expected.

Once again thanks for your info.

Regards Anand

0